INC-143376 · Issue 604529
Adding handling for property without parent page
Resolved in Pega Version 8.5.2
Filtering was not working for a DateTime control in an optimized grid with embedded property which was a function alias defined in a report definition referenced by a Data Page. This was traced to the system assuming that every property has a parent page, which this use case did not. To resolve this, an update has been made that will return null for the parentGroupOrListProp if one does not exist.
INC-143531 · Issue 598644
Dirty Flag reset updated
Resolved in Pega Version 8.5.2
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
INC-143599 · Issue 598771
Non-template RDL time value handling updated
Resolved in Pega Version 8.5.2
The Time value displayed on clipboard and data designer differed from the value shown on user work form when using a categorized repeating dynamic layer rendered in non-template mode with the Datetime control configured inside the RDL. This was traced to the Time string being considered as a date when using this configuration and calling the engine API, and has been resolved by ensuring this configuration will call the correct Time API instead so that the timeofday property value will be formatted correctly.
INC-144102 · Issue 605882
Values with accent characters are sorted properly
Resolved in Pega Version 8.5.2
Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.
INC-144301 · Issue 604406
Revised character escaping for Tooltip
Resolved in Pega Version 8.5.2
Hover text/Tooltip on the Collapsible layout was showing the content in ASCII format if the input string contained special characters like "&" (which was getting printed as "&"). This has been resolved by unescaping the title string and letting handlebars do the work of escaping it.
INC-144515 · Issue 608598
Corrected multiple harness error messages being displayed
Resolved in Pega Version 8.5.2
Same validation error messages are being displayed multiple times for the harness. This was traced to the way the system checks for an existing error table based on the data-harness-id attribute in the current harness context; sometimes existing errors tables are missed and new ones were created which stacked up on screen. This has been corrected by adding a condition to check for existing errors.
INC-144543 · Issue 600085
Keyboard accessibility added to Cosmos buttons
Resolved in Pega Version 8.5.2
Focus states were missing on the standard and icon buttons in Cosmos. These have been added to facilitate keyboard navigation.
INC-144851 · Issue 604479
Date Time picker works with locale es_US
Resolved in Pega Version 8.5.2
When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).
INC-144888 · Issue 603616
Custom rich-text editor plugin support updated
Resolved in Pega Version 8.5.2
At runtime, two rich-text editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for rich-text editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden rich-text editor. Investigation showed that if plugins were added to pega.ctx.customrich-text editorPlugins, then the plugin manager discarded plugins from pega.u.d.customrich-text editorPlugins. To resolve this, the rich-text editor plugin manager has been modified to merge the plugins from pega.ctx.customrich-text editorPlugins and pega.u.d.customrich-text editorPlugins.
INC-145119 · Issue 601710
Client side validation works with Reference page property
Resolved in Pega Version 8.5.2
A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.