Downloads
Product availability Matrix (PAM)
Downloads of this patch are available from the
Rocket Customer Support Portal.
Further explanation can be found
here.
Currencies
- Add support for PostgreSQL 15 (PGS U1.7) on Docker image.
|
Fixes
| UNI-35691 | A runtime exception is generated when html:size property is set for ux-TextField widget using the Properties Explorer |
| UNI-35689 | A UX widget that is in error state sometimes fails to be updated correctly after execution of a trigger that has only output scope. |
| UNI-35681 | The auto-indent feature of the code editors in the IDE sometimes fails to indent properly around function declarations and scope declarations. |
| UNI-35651 | The ux-Switch widget shows incorrect animation when being toggled interactively. |
| UNI-35416 | Starting the SCP service on Linux may give an error. |
| UNI-35415 | "systemctl stop rms.target" or "rms.sh stop" does not stop the RMS server on the latest Oracle Linux |
| UNI-33520 | When the idle_in_transaction_session_timeout is set in the PostgreSQL database and the connection to the server is lost, the DBMS connection cannot be restored. |
UNI-35691 - A runtime exception is generated when html:size property is set for ux-TextField widget using the Properties Explorer
Solution available in patch(es): 10.4.02-039
Description:
When html:size property is set to a value for ux-TextField widget using the DSP Widget Properties dialog, and on edit of the textField, if a button causing interaction is clicked, an exception is caused at runtime on the browser. This prevents the button's default trigger from completing execution. If the browser debugger is not open, the process fails silently leading users to think that the button could not be clicked.
Environment:
+ Uniface Version 10.4.02.037 and higher
+ Operating System: OS independent
+ Database: Database independent
Workaround:
No html:size property is defined
Notes:
This problem has been resolved.
UNI-35689 - A UX widget that is in error state sometimes fails to be updated correctly after execution of a trigger that has only output scope.
Solution available in patch(es): 10.4.02-039
Description:
When a UX widget's validate() trigger rejects the widget value, or when a client-side syntax check fails, the UX widget gets into an error state. When a trigger that has only output scope is executed, UX widgets in such an error state are sometimes not updated correctly with the response from the trigger execution.
Environment:
+ Uniface Version 10.4.02.037 and higher
+ Operating System: OS independent
+ Database: Database independent
Workaround:
Define the trigger to also have input scope. With that, trigger execution will be prevented when a widget is in error state.
Notes:
This problem has been resolved.
UNI-35681 - The auto-indent feature of the code editors in the IDE sometimes fails to indent properly around function declarations and scope declarations.
Solution available in patch(es): 10.4.02-039
Description:
When hitting Enter after the 'end' keyword, the 'end' keyword might be misplaced under certain circumstances. The 'endscope' keyword faces similar issues.
Environment:
+Uniface Version : 10.4.02
+Operating System : Windows
+Database : Database independent
Workaround:
When 'end' or 'endscope' get misplaced, they can be manually re-indented.
Notes:
This problem is solved.
UNI-35651 - The ux-Switch widget shows incorrect animation when being toggled interactively.
Solution available in patch(es): 10.4.02-039
Description:
When the ux-Switch widget is being toggled on or off, code being executed as a part of the onchange (web)trigger slows down or even interrupts the animation of the switch-toggle. During this time, the switch-toggle might get stuck outside of the widget's boundaries, creating a bad and confusing user experience.
Environment:
+Uniface Version : 10.4.02.037
+Browser : Browser independent
+Operating System : OS independent
+Database : Database independent
Workaround:
Avoid long running or halting code and/or a server round trip in the onchange (web)trigger.
Notes:
This problem is solved.
UNI-35416 - Starting the SCP service on Linux may give an error.
Solution available in patch(es): 10.4.02-039
Description:
The scp.sh script checks whether the SCP service is already running and if so it will first stop it. However, the outcome of this check is interpreted reversely, so it will try to stop the service when it is not running, and will not try to stop it when it is in fact running. This causes an error message to be issued when the service is not running, saying that it can't be stopped because it is not running.
Environment:
+Uniface: Version: Version independent
+RMS version: Version independent
+Operating System: Any Linux distribution
+Database: DBMS independent
Workaround:
As a workaround you can edit scp.sh. Find this line:
if [ -z "$STS" ]; then
and insert a ! and a space before the -z, like this:
if [ ! -z "$STS" ]; then
Notes:
This problem is solved after installing or upgrading your RMS server.
UNI-35415 - "systemctl stop rms.target" or "rms.sh stop" does not stop the RMS server on the latest Oracle Linux
Solution available in patch(es): 10.4.02-039
Description:
On the latest version of Oracle Linux the RMS server can't be stopped in the normal way.
Environment:
+Uniface: Version independent
+RMS version: Version independent
+Operating System: Oracle Linux
+Database: DBMS independent
Workaround:
After trying to stop the RMS server using systemctl or rms.sh, find the PID of the still running RMS server and issue a "kill <PID>" command.
A more permanent workaround is to edit the rms.sh script and replace the line that assigns a value to the variable PID with this:
PID=`pidof /lserv64`
if pidof is installed on your system.
Notes:
This problem is solved after installing or upgrading your RMS server.
UNI-33520 - When the idle_in_transaction_session_timeout is set in the PostgreSQL database and the connection to the server is lost, the DBMS connection cannot be restored.
Solution available in patch(es): 10.4.02-039
Description:
If the connection to the PostgreSQL database is lost, restoring the connection is only feasible by closing and restarting the application.
Environment:
+Uniface Version : 10.x
+Operating System : OS independent
+Database : PostgreSQL
Workaround:
None
Notes:
This problem has been solved