INC-154824 · Issue 620922
Check added for hidden field during validation
Resolved in Pega Version 8.5.3
When using custom validation for a future date, after certain steps the message "value cannot be blank" was displayed even though there was a value in the date control. This was traced to the validation also being performed on a hidden field, and has been resolved by adding a condition in pega_validators to check for hidden fields when running the validation.
INC-154855 · Issue 616003
Updated expression handling when not using client side validation
Resolved in Pega Version 8.5.3
After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.
INC-154860 · Issue 626100
Corrected extra space from harness child elements
Resolved in Pega Version 8.5.3
After upgrade from v7 to v8, extra space was seen at the bottom of harness content. This was caused by the header and footer heights being included two times while calculating mashup height, and has been resolved by updating the postMashupHeight method to skip including the header and footer height while iterating child elements for harness-content-workarea-view.
INC-154977 · Issue 622803
Added hidden field validation for offline app
Resolved in Pega Version 8.5.3
An enhancement has been added to handle the usecase of offline apps needing to validate hidden fields. This will be handled through the new flag "pega.u.d.validateHiddenFieldsInOffline".
INC-155319 · Issue 616476
Action Set Dialog features displayed correctly in App Studio Design with Firefox
Resolved in Pega Version 8.5.3
When using the App Studio Design mode to edit controls and elements within section at runtime (Open Case Type in App Studio -> Save and run) and selecting a control in Design mode that has any action set configured on it, upon opening the action set clicking the �Add an action� link element the dialog box which appeared cut off. This was traced to an issue where Overlay was not flipped in Firefox v83.0 when the client.right value exceeded the main container width, and has been resolved by adding a condition for Firefox to use the correct client.right value as per the main container.
INC-155855 · Issue 620576
Safe check added to modal window pop-up cancel
Resolved in Pega Version 8.5.3
On click of a link to add items to the rows by selecting the page list from pop-up window, clicking on the cancel button generated a node name undefined error after which clicking the link would not open the pop-up window at all. This was traced to the pre-processing activity in the flow action used to copy page list from one page to other, and has been resolved with the addition of a safe check.
INC-156094 · Issue 621064
Access control updated for non-auto-generated finishAssignment
Resolved in Pega Version 8.5.3
After upgrade, a flow containing a flow action that called an out of the box HTML rule was triggering a SECU0019 alert and blocking functionality. This was a missed use case for BAC where all non-auto generated rule actions should be registered, and has been resolved by registering finishAssignment.
INC-156625 · Issue 620655
Cross-Site Scripting protection update
Resolved in Pega Version 8.5.3
Cross-Site Scripting protections have been updated for labels.
INC-156802 · Issue 620674
Handling added for special characters for track changes
Resolved in Pega Version 8.5.3
After entering inverted commas ["] inside a text box configured with post value and 'refresh this section' actions, focusing out of it caused the UI to freeze. A JSON parse issue was seen in the browser console, which was traced to the domelement API not having handling for special characters in the HTML code. This has been resolved.
INC-156826 · Issue 625439
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.5.3
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.