Downloads
Product availability Matrix (PAM)
Downloads of this patch are available from the Rocket Customer Support Portal
New Feature(s)
- We have enhanced the Uniface Documentation to include a visual preview of all DSP widgets, including UX widgets. This allows users to quickly compare and select the most suitable widget at a glance.
Currencies
- OpenSSL has been upgraded to version 3.0.18 for improved security.
- CEF has been upgraded to version 141.0.5 with the corresponding Chromium version 141.0.7390.55, for improved security.
Notes:
- This upgrade solved inconsistent scrollbar rendering in the IDE on Windows 11.
- MSAA changes in the UHTML widget may affect your Windows GUI automation tests.
- As a result, the minimum system requirements have been revised:
CEF now requires Windows 10 or newer or Windows Server 2016 or newer, running on an Intel Pentium 4 processor with SSE3 support.
8GB RAM: A good experience for typical users who use one instance of the IDE.
16GB RAM or more: Recommended for power users who want to run many IDE instances simultaneously.
Fixes
- UNI-42691: In uxRadioGroup, if valrep is empty, users can still interact with the radio group and select a placeholder option, which fires the onChange trigger.
- UNI-36970: Errors generated by stored procedures are not relayed back to the caller.
- UNI-32628: WRD returns HTTP 200 instead of 5xx for server errors, causing incorrect success indication.
UNI-42691 - In uxRadioGroup, if valrep is empty, users can still interact with the radio group and select a placeholder option, which fires the onChange trigger.
Solution available in patch(es): 10.4.03-028
Description:
If valrep is empty, users can still interact with the radio group and select a placeholder option, which fires the onChange trigger.
Environment:
+ Uniface Version: 10.4.03+ Browser: Browser independent
+ Operating System: OS independent
+ Database: Database independent
Workaround:
None.
Notes:
This issue has been resolved.
Back to top
UNI-36970 - Errors generated by stored procedures are not relayed back to the caller.
Solution available in patch(es): 10.4.03-028
Description:
Errors generated by stored procedures are not relayed back to the caller. You do see the actual error in the message frame or log file (except when Sybase / SAP Adaptive Server is used), in addition to $status being -150. However, $procerrorcontext does not contain the message, so it is difficult to programmatically deal with such errors.
Environment:
+Uniface: All versions+Operating System: OS independent
+Database: DBMS independent
Workaround:
You can find the error in $putmess after the activation of a stored procedure that failed with $status = -150, except when Sybase / SAP Adaptive Server is used.
Notes:
This problem is solved. In $procerrorcontext, in the item ADDITIONAL, which is a list in itself, the items MESSAGE, DRV and STATUS are added, where MESSAGE will contain the error message the stored procedure issued, DRV the connector in question, and STATUS will include the database error code for that error. In addition, when Sybase / SAP Adaptive Server is used, the complete error message will appear in the message frame as well, just like with all other connectors.
Back to top
UNI-32628 - WRD returns HTTP 200 instead of 5xx for server errors, causing incorrect success indication
Solution available in patch(es): 10.4.03-028
Description:
Current Behavior:- The WRD currently returns HTTP status 200 (OK) even when a server error occurs and a red error page is shown.
- This is incorrect. Server errors should return a 5xx HTTP status, which indicates a server-side issue.
Updated WRD Behavior:
- In the new WRD version (6.5 or 7.2), red error pages now correctly return HTTP 5xx status code.
Impact on RESTful Applications:
- If your RESTful API error handler only checks the response body, your application will still work with the updated WRD.
- If your error handler checks the HTTP status code, you may need to update your application to handle the new 5xx error responses properly.
Environment:
+ Uniface Version : 10.4.03.000+ Operating System : OS independent
+ Database : DBMS independent
+ Browsers : Browser independent
Workaround:
No
Notes:
This problem has been fixed.
