INC-139861 · Issue 594006
Cross-site scripting protections added to Case Email
Resolved in Pega Version 8.5.4
Cross-site scripting updates have been added to rules handling linked email correspondence.
INC-161463 · Issue 638002
Case Dependency corrected for different access groups
Resolved in Pega Version 8.5.4
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
INC-161948 · Issue 638962
Locking settings enabled for circumstanced case types
Resolved in Pega Version 8.5.4
Optimistic locking options were not present for a circumstanced case type, and the option to select the "Lock parent case when an action is performed on this case" check box was not available. However, when the parent case type was enabled with optimistic locking, a circumstanced child case could inherit a lock from its parent. Because "Lock parent case when an action is performed on this case" was not enabled on the circumstanced child case type, trying to update the parent case from the child case and save the parent case resulted in a "Lock not held on parent" error. This was a missed use case, and has been resolved by enabling locking settings in Case Designer for circumstanced case types.
INC-162168 · Issue 634934
Refresh works for nested lists
Resolved in Pega Version 8.5.4
After creating Pagelist A with another Pagelist within (B), a section was created with a repeating dynamic layout to display Pagelist A and a button was added with action set to refresh this section. In the embedded section of the repeating dynamic layout, a nested repeating dynamic layout was created for Pagelist B and a button was set to refresh this section. When using this configuration, the refresh was returning the actionID for Pagelist A regardless of which button was used. To resolve this, an update has been made which will iterate over the stack and append the individual indexes to the encoded value in the pzAPICreateJsonForField function.
INC-162550 · Issue 630273
Read-only text controls properly localized
Resolved in Pega Version 8.5.4
An issue with localization of property references used in read-only text controls when calling dx api v1 /assignments/{ID}/actions/{ID} in context of DataGather application in attachment JSON response has been corrected.
INC-162763 · Issue 646110
Case creation and Save As performance improvements
Resolved in Pega Version 8.5.4
Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.
INC-162894 · Issue 644181
Deleting attachment with icon button works in Attachment section
Resolved in Pega Version 8.5.4
After upgrade, a delete icon in the attachment section was not working as expected. This was traced to BAC work done earlier, and has been resolved by updating the Delete Attachment function of the AttachmentListViewSelectorScript.
INC-163154 · Issue 638099
Code updated for bulk actions buttons
Resolved in Pega Version 8.5.4
After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.
INC-165445 · Issue 649150
Corrected case for Location output parameter name
Resolved in Pega Version 8.5.4
The activity pzCreateCaseV2Impl which is used for the create case API was not returning the "location" output parameter due to the parameter being set as "Location", with capital L inside activity pzCreateCaseInternal at step 10. This has been corrected by renaming the parameter 'location' to 'Location'.
INC-166820 · Issue 649968
Blank parameter handling added to assignments function
Resolved in Pega Version 8.5.4
When calling the Pega v1 API /assignments/{ID}/actions/{actionID} a 500 Internal Server Error status was returned if the configuration included an Autocomplete configured with two fields where the second had the "Use in Search" setting enabled. An error was also logged. Once the error occurred, editing the Autocomplete to disable the second "Use in Search" did not stop the error; the entire Autocomplete had to be deleted and recreated. This was traced to the system trying to set a blank parameter due to the autocomplete being configured with a data page with no parameters, and has been resolved by modifying the pzAPIDetermineOptionsFromPage Rule-Utility-Function to not set parameters when the parameter key is blank.