Downloads
Product availability Matrix (PAM)Downloads of this patch are available from the
Rocket Customer Support Portal.
Further explanation can be found
here.
New Feature(s)
- The ux-PlainText widget, implemented by widget JS class uxPlainText, no longer applies CSS text formatting styles from the Fluent design-system.
This will allow Uniface UX developers to seamlessly integrate database-stored values into HTML text without any visual styling differences. Furthermore, the ux-PlainText widget will now conform to the text formatting styles of its parent container if any styles are specified for the parent.
|
Fixes
| UNI-35906 |
The options-dropdown of the uxSelect widget is not positioned correctly when it has 'fluent-card' as it's ancestor. |
| UNI-35713 |
Performance degradation in the PostgreSQL driver when using segmented fields. |
| UNI-35690 |
UX widgets, such as ux-TextField, ux-NumberField and ux-TextArea, when stretched in height, break the focus/active state visualization. |
| UNI-34846 |
Not all property updates are send to the dataUpdate() function of the custom widget when set using $fieldproperties in the exec operation |
UNI-35906 - The options-dropdown of the uxSelect widget is not positioned correctly when it has 'fluent-card' as it's ancestor.
Solution available in patch(es): 10.4.02-040
Description:
When a uxSelect widget has fluent-card as its ancestor, it's options dropdown is not placed correctly.
To fix this, the "contain" and "content-visibility" style properties of "fluent-card" can be set to "visible" and "initial"
This is done in the dataInit function of the uxSelect widget at runtime (and only when a uxSelect widget is loaded inside a fluent-card widget).
A better approach to this is to set these properties using css selectors at page load time.
Environment:
+Uniface Version : 10.4.02.037
+Operating System : OS independent
+Database : Database independent
+Browser Information: All browsers
Workaround:
Changing style attribute of the fluent-card at page load time using javascript or css from the DSP.
Notes:
This problem has been solved.
UNI-35713 - Performance degradation in the PostgreSQL driver when using segmented fields.
Solution available in patch(es): 10.4.02-040
Description:
The insert and update statements were not cached in case the database table definition contained a segmented field.
Environment:
+Uniface: Version: 10.*
+Operating System: Independent
+Database: PostgreSQL
Workaround:
None
Notes:
This problem has been solved
UNI-35690 - UX widgets, such as ux-TextField, ux-NumberField and ux-TextArea, when stretched in height, break the focus/active state visualization.
Solution available in patch(es): 10.4.02-040
Description:
When a UX widget, such as ux-TextField, ux-NumberField, or ux-TextArea, is stretched in height, it breaks the focus/active state visualization, leading to an inconsistent UX experience.
Environment:
+ Uniface Version : 10.4.02.037 and higher
+ Browser : Browser independent
+ Operating System : OS independent
+ Database : Database independent
Workaround:
Use these widgets with their default heights.
Notes:
This problem has been resolved.
UNI-34846 - Not all property updates are send to the dataUpdate() function of the custom widget when set using $fieldproperties in the exec operation
Solution available in patch(es): 10.4.02-040
Description:
For a UX widget, when you use $fieldproperties in operation Exec to set a widget property, some properties do not reach the widget.
For example, putitem/id $fieldproperties(fieldName), "html:appearance", "filled"
Environment:
+Uniface Version : 10.4.02
+Operating System : ALL
+Database : ALL
Workaround:
A workaround is to use $properties(), like:
putitem/id $properties(fieldname), "PropId", "PropValue"
Notes:
This problem has been resolved.