Miscellaneous Notes and Bug Fixes for USoft 11.0.1E
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 do not have to 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.
AUTHORIZER
USD-7141 (US-1906)
The username in RulesEngine.SetUser() was case-sensitive.
This has been changed, it is now case-insensitive again.
USD-7165
The catalog in the Authorizer was not visible anymore.
This has been fixed.
BATCH
USD-7207 (US-1981)
sql-scripts() calls called from a decision in an action task of a job were not executed.
This has been fixed.
BENCHMARK
USD-6754 (US-1557)
The Benchmark Tracer showed generic text in the bottom list view.
This has been fixed.
USD-7140 (US-1902)
The order of the buttons in the Benchmark dialog Operations on Appliction Database' was different in 11.0 as compared to 10.1.
This has ben changed.
USD-7174 (US-1928)
When exporting application data with Benchmark the status bar showed 'Exporting data for application <user>'. This has been fixed to 'Exporting data for application <application>'
DATABASE CONNECTIVITY
USD-6911 (US-1733)
When using separate RDBMS types for Repository and Application, constraints would sometimes get parsed for the wrong RDBMS resulting in database errors.
This has been fixed.
DEFINER
USD-5716 (US-1186)
When trying to use an interface component in a domain constraint, an error was given when checking the constraints.
This has been fixed.
USD-7136 (US-1897)
When USAUTH was used as a module, an error could occur when upgrading the repository to version 11.
This has been fixed.
USD-7138 (US-1905)
When you consume USD as a module and try to parse a constraint the application no longer crashes
USD-7155 (US-1908)
When a table was defined in the EAR diagrammer, an error about GUK values could occur during saving.
This has been fixed.
USD-7182 (US-1938)
The definer would crash when a job was trying to execute a task which does not exist.
This has been fixed: now a clear error is given.
USD-7203 (US-1943)
In the Definer, the dialog with which you can import data from Studio into the Definer has an analyse button to preview what will happen when importing a certain file. Pressing this button resulted in an error.
This has been fixed.
LINUX PORT
USD-7137 (US-1899)
When trying to build the Rules Service base image on Linux, executing an "apt-get update" would result in the error: "Could not connect to nlux75.usoft.com:3142 (45.82.188.225)"
This has been fixed.
SERVICE FRAMEWORK
USD-7085 (US-1827)
The Service Definer uses 2 java logging frameworks: log4j2 (the 2nd version of log4j) and Java Util Logging.
The logging framework log4j2 was already supported and is configured by the generated configuration file log4j2.xml in the publication folder of the server.
Java Util Logging is newly supported and is configured by the configuration file "logging.properties" in the "JAVA\SUN\JRE64\conf" folder where USoft has been installed. If you add e.g. the lines below to the "logging.properties" file and in the Service Definer ensure the Log Level of the Server is e.g. "Trace", the file "UService.log" in the "logs" folder of the server publication contains detailed technical log records. For details how to configure the Java Util Logging check e.g. https://docs.oracle.com/javase/8/docs/api/java/util/logging/package-summary.html
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level = FINEST
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
.level = FINEST
Silence verbose classes:
org.glassfish.grizzly.filterchain.DefaultFilterChain.level = INFO
org.glassfish.grizzly.ProcessorExecutor.level = INFO
org.glassfish.grizzly.nio.AbstractNIOAsyncQueueWriter.level = INFO
org.glassfish.grizzly.http.server.io.ServerInputBuffer.level = INFO
org.glassfish.grizzly.http.io.InputBuffer.level = INFO
WEB APPLICATION
USD-6896 (US-1711)
The health check of the page engine service failed when rerouting had been configured for the server.
This problem has been solved.
USD-7176 (US-1931)
In a SQLDataSource, having a semicolon at the end of the SQL expression may result in SQL Parser Error messages. Although removing the semicolon also fixes the problem, this error should not happen. If an unnecessary semicolon is placed at the end of the query, it is now ignored.
USD-7179 (US-1934)
When a lookup data source is finished loading data long before its main data source finishes querying, it may end up being disabled if the first selected record of its main data source has no key value for the lookup data source filled in. This has been fixed: it now performs an extra check in this specific situation, and then decides if the lookup data source must remain disabled or not.
USD-7233
A relate control without any columns did not query anymore.
This has been fixed.
WEB DESIGNER
USD-6230
In the Web/Windows Designer, in the property inspector, it is now possible to copy the value of a property to the clipboard by pressing Ctrl+C. This is also supported for disabled/read-only properties.
WINDOWS APPLICATION
USD-7134 (US-1892) (US-1898)
When USD.con was used as a module in another application, an error would occur when starting that application about a difference in the definitions of template domain DECIMALS.
This has been fixed.
USD-7135 (US-1898)
When USAUTH was used as a module, errors could occur about different definitions of the domains DATE and DATETIME.
This has been fixed.