Skip to main content

Miscellaneous Notes and Bug Fixes for USoft 11.0.1C

Patch installation

When installing this patch in the production environment:

  • Web publications must be updated in order to get the fixes made in this patch.
  • Flat files must be updated.
  • Service Framework servers must be updated.

Bug fixes

The identification number in front of each item is a Jira Issue ID. This is a number that USoft uses internally.

An identification number(s) in parentheses at the end of an item (if any) is a Jira Support ID. This is a number that USoft Support uses to communicate with external reporters.


BINDER

USD-6625 

USoft Binder now has an option to copy the arguments of a binder item by right-clicking them.


DEFINER

USD-6884 (US-1701) (US-1573)

In USoft Definer, if multiple windows were opened and all windows were closed using "Windows -> Close All", a crash could later occur at an undetermined time.

This has been fixed.

USD-6983 (US-1779)

The template domain 'DECIMALS' did not have a '-' sign in the io-format. As a result, negative values were not displayed correctly in the client server application.

This has been fixed in the default data used when creating Definer tables for the first time or when upgrading from 10.1.

For existing repositories, this must be changed manually in the DECIMALS template domain by changing the IO Format from "Z(8).99" to "-Z(8).99".

USD-6998 (US-1788)

The USoft Benchmark data action 'Drop Undefined' also suggested to delete all tables of USoft applications (such as T_TABLE, T_CONSTRAINT, etc.).

This has been fixed.

USD-6775 (US-1569) (US-1644)

In the Service Definer, if version control was enabled, the columns 'JAVA_LOCATION' and 'PUBLICATION_LOCATION' of the T_SVC_SERVER table were not placed under version control.

This has been changed. Both columns are now brought under version control.

To update the version control files of an existing connected Service Definer repository, either re-create the version control files by disconnecting the populated Service Definer from the version control system and then re-create the version control files, or manually update the server records, commit them, and change them back again.


LINUX PORT

USD-6848 (US-1678)

On Linux, when UBlendIt was used to run creapp, UBlendIt could not correctly detect if the result of creapp was successful or not. This resulted in UBlendIt always reporting this operation as failed. Also, UBlendIt did not report any output (or errors) from the creapp call.

This has been fixed.


RULES ENGINE

USD-6671

XML.SQL2XML now supports the various forms of JOIN syntax.


RULES SERVICE

USD-4353 (US-701)

When configuring a Rules Service, it is possible to specify one or more controlling hosts (in addition to the localhost). This functionality was not working anymore: all hosts able to reach the Rules Service port were able to configure it. This has been fixed.

Specifying controlling hosts for a Rules Service running in a Docker container is not possible due to limitations in the network bridge from the container. Every host that is allowed to reach the Rules Service in the container can also configure this service. If you do not want this, take additional security measures, for example by adding firewall rules.

If the Rules Service runs as a Windows service, the list of controlling hosts now also works after the service is restarted.


SERVICE FRAMEWORK

USD-6923 (US-1313) (US-1742)

In Service Definer, no informative message was shown if a SQL statement was checked without a properly configured default connection.

This problem has been solved.

USD-6945

In Service Definer, the use of JavaAssist is deprecated since USoft version 11.0. A warning message is issued when a service is published or a class is checked.

It is recommended to provide a path to the JDK installation in "Compiler settings". For more information, see "Compiling Java in Service Definer" at docs.usoft.com.

USD-7012 (US-1799)

In Service Definer, a compilation error was thrown during publish if USoft had been installed in a folder containing a space character, e.g. in the folder "c:\program files".

This problem has been solved.

USD-7024 (US-1781) (US-1806)

In Service Definer, the table containing the re-route mappings was not under version control.

This has been fixed.

To write existing re-route mappings in an instance of Service Definer that is already connected to version control, make a small change and commit. This should trigger writing the re-route mappings to version control.


DOCS.USOFT.COM

USD-6158

The knowledge base or product documentation for the USoft platform (excluding USoft Studio) has been moved from community.usoft.com to: docs.usoft.com.

The new location offers these advantages:

The table-of-contents structure in which the articles are organised, is easier to view and navigate because an expandable tree view display is offered on the left-hand side. The location in this structure of the article currently selected is now highlighted.

The internal structure of an article is easier to view and navigate because it is displayed as a collection of clickable links on the right-hand side that does not scroll out of view.

Search behaviour is improved. The search result pane has richer navigation functionality, the table-of-contents tree view auto-reduces to show only articles that contain the text most recently searched, and occurrences of the text searched are highlighted in the article contents.


WEB APPLICATION

USD-6951

On a page with an embedded data source that uses a host variable in an output expression column, an error was thrown about the hostvar when a newly created record was committed.

This has been fixed.


WEB DESIGNER

USD-6971 (US-1764)

Web Designer would crash when the repository was running under version control and a subclass of an action control was created. This has been fixed.


WINDOWS APPLICATION

USD-6753 (US-1553)

The read-only colour of dropdowns in the Blue skin was hard to see. This has been fixed.


WINDOWS DESIGNER

USD-6750 (US-1552)

The About Dialog did not resize correctly when dealing with a large company name. This has been fixed.