Miscellaneous Notes and Bug Fixes for USoft 11.0.1B
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-6796 (US-1626)
In an Oracle database account for which the user name was declared (in the CREATE USER statement) as an unquoted name in mixed case, causing Oracle to silently perform a conversion to all-uppercase, even if Create Tables (creapp.exe) was successfully applied to USoft Authorizer, Create Tables (creapp.exe) applied to USoft Definer could fail and complain about missing Authorizer tables.
This has been fixed.
DEFINER
USD-6815 (US-1648)
A crash could occur if an incorrect statement was typed in SQL Command that looked like insert into<some_table>(.
This has been fixed.
DELIVERY MANAGER
USD-5710 (US-1709)
In Delivery Manager, support for SQL Server connections via ODBC has been added.
DOCUMENTATION
USD-6819
The Knowledge Base article on RulesEngine.MessageLanguage() wrongly claimed that this component method could be used to pass certain types of message to web pages. In reality, the Page Engine is not able to do this.
This claim has been removed. Note that all constraint messages, including those containing variable elements, are correctly passed by the Page Engine.
INSTALLER
USD-6789 (US-1614)
Released binaries and installer are now signed by USoft.
LINUX PORT
USD-6728 (US-1531)
When using SAML for authentication, a user might be authorized correctly at first, but denied access during a second attempt.
This has been fixed.
RULES ENGINE
USD-5632
Domains now correctly show what module they belong to in USMeta.Domains and USMeta.Columns output.
USD-6680 (US-1487)
USoft now also supports the 'except' operator in a union clause.
WEB APPLICATION
USD-6783 (US-1598)
When a dsc.refresh() was performed on a data source whilst no record was selected (e.g. with 'Set First Record as Default Selected Record’ set to 'No'), an error would be thrown.
This has been fixed.
USD-6797 (US-1628)
The File Upload Control did not work correctly if only an upload button was displayed. Nothing happened in this situation.
This has been fixed. The file selection dialog now displays correctly.
USD-6805 (US-1564)
Using a SQLDataSource to execute component functions or batch jobs resulted in java errors.
This has been fixed.
USD-6825 (US-1660)
Using an INVOKE query that contained a "WITH SELECT" in a SQLDataSource resulted in an error message.
This has been fixed.
USD-6830 (US-1662)
In a page with many data sets, navigating beyond the (initially) visible data sets resulted in reverting back to one of these initially visible sets.
This has been fixed.
USD-6843
In USoft 11, JQuery is no longer enabled by default.
For this reason, developers upgrading from 10 to 11 who used custom JQuery code in CustScript.js or further manually added files would be confronted with various errors on starting the application after upgrade. These errors made upgrading difficult unless JQuery was re-enabled first. This, in turn, made it attractive to continue using JQuery in the upgraded application.
A custom JQuery compatibility class existed already: UdbJQuery. So far, it covered only basic functions. Now, many more common functions have been added, so that these will work when calling JQuery without having the library present. This will significantly help to achieve an upgraded application free of Jquery calls, since every JQuery call throws a warning message, making it easy to find and address these calls.
WEB DESIGNER
USD-6850 (US-1677)
Host variables were not passed to the 'Automatically query next datasets'.
This has been fixed.
USD-6866
In Windows Designer and Web Designer, an unnecessary message would appear if a class was opened after the name was changed.
This has been fixed.
WINDOWS APPLICATION
USD-6812 (US-1642)
An RDBMS user was handled as a funnel user when an attempt was made to re-login to a different database account using ApplicationLogin()
This has been fixed.
WINDOWS DESIGNER
USD-6717 (US-1516)
After upgrading from 10.1, the positioning of Window GUI elements would sometimes differ from the position they had in 10.1. This could only happen for GUI elements of which the Position property was set to 'inherit from System'.
This has been fixed. If Position is set to 'inherit from System', the position calculation of GUI elements will be done the same way as in 10.1.
However, from the time when you start using version control on 11, the positioning can result in unwanted diffs that keep occurring. To avoid this, set the Position property to a literal value manually, instead of using 'inherit from System'. Also note that in 11, any newly inserted control will be given a literal Position value, as opposed to the 'inherit from System' value.