INC-138877 · Issue 589533
Filter range decimals persist for German locale
Resolved in Pega Version 8.5.2
When using German localization, filtering values in Dashboard caused the entered decimal value range (13.00 - 50.55) to lose the separator and become a whole number (1300 - 5055). This has been corrected.
INC-138968 · Issue 594167
ARIA landmarks added to put dynamic layout in tab order
Resolved in Pega Version 8.5.2
As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.
INC-139023 · Issue 591163
Tab will exit portal side menu
Resolved in Pega Version 8.5.2
It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.
INC-139054 · Issue 598153
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF, lines were broken up for the content boxes. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-139095 · Issue 596507
Portal loads for Simplified Chinese locale in IE
Resolved in Pega Version 8.5.2
When using IE, the portal would not load when using the Simplified Chinese locale. This was caused by Microsoft Internet Explorer rendering the locale as 'zh-CN-#Hans' instead of the expected 'zh-cn'. This has been resolved by adding a check to remove the "#" in the locale string to avoid a malformed URL.
INC-139156 · Issue 592148
Pasting image lands in correct location
Resolved in Pega Version 8.5.2
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich-text editor, and has been resolved.
INC-139260 · Issue 592218
Handling added for third party form library
Resolved in Pega Version 8.5.2
When using a third party library which created a form tag, the wrong form was used on submit in the Ajax container. This has been resolved by updating the pzpega_ui_doc_submit file submitInner method to handle this use case.
INC-139327 · Issue 595699
GetImmutablePropertyInfo updated to return pyType for page group properties
Resolved in Pega Version 8.5.2
Dates were are not matching in the UI and Apply filter section in the date column of Table layout filters. The system calculates pyType properties on save and passes the complete reference of the property to the getImmutablePropertyInfo API, but this resulted in the API ignoring the subscript if a nested page group property was passed. To resolve this, updates have been added to invoke the API getImmutablePropertyInfo so the property name and class name are passed during runtime in order to return pyType for page group properties.
INC-139328 · Issue 588584
Corrected Excel table picture being included with the rich-text editor paste
Resolved in Pega Version 8.5.2
Corrected Excel table picture being included with the rich-text editor pasteAs an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using the rich-text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
INC-139624 · Issue 595988
Validation error messages persist appropriately
Resolved in Pega Version 8.5.2
Whenever there was a Validation check on a flow action Validation Tab and Post Processing Activity, the error message appeared on the screen momentarily and disappeared. Intermittently, the validation error would stay on the screen after appearing a second time. This was traced to the refresh action happening in the wrong context due to the refresh action of the Ajax container being called twice, once in postacrenderac and another time in the harness unload function.The case error DOM was present in the markup, but because of the refresh in the harness unload, the error message was removed from the DOM. This has been resolved by changing the refresh call from onHarnessUnload callback to postAcRender callback. Logic has also been added to prevent refresh when error messages are present.