INC-174435 · Issue 659479
Survey Complex Question Definition properly displayed
Resolved in Pega Version 8.4.6
Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".
INC-175533 · Issue 678911
Improved Page compare for page groups
Resolved in Pega Version 8.4.6
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-180603 · Issue 661739
Added protections for GetSiblings
Resolved in Pega Version 8.4.6
Cross-site scripting protections have been updated for the GetSibling activity.
INC-182248 · Issue 665782
Added logic to handle manual validate rule creation
Resolved in Pega Version 8.4.6
Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case.
INC-191567 · Issue 676158
New application wizard security updated
Resolved in Pega Version 8.4.6
Security around displaying and running the new application wizard has been enhanced.
SR-D91834 · Issue 554425
Related cases of different types properly linked in Case Worker Portal
Resolved in Pega Version 8.5
After creating a case of type1 in the Case Worker portal, creating a case of type2 from the first case showed the case ID of the second case in the Related Work section as expected. However, after clicking on the link of the case ID of the second case from the related work section, the second case opened but the case ID of the first case was not shown in the Related work. The cases were correctly associated when the Case Manager portal was used instead. This was traced to the Case Worker clipboard continuing to hold the previous case ID thread, and has been resolved.
SR-D71475 · Issue 538721
Check added to apply values of newAssignPage.pxFormName
Resolved in Pega Version 8.5
After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.
SR-D63307 · Issue 542770
Unneeded class name filter removed from GetRelevantPropertiesForDataType
Resolved in Pega Version 8.5
Given one class with a set of properties and another class inherited from the first class containing a relevant records set for class 2, then a new harness did not show the base class fields. Investigation showed that the fields present in the parent class and marked relevant in the case were not being fetched due to pzGetRelevantPropertiesForDataType having a class name filter along with filter by rule resolution. To resolve this, the class name filter has been removed as it is not required due to the report already filtering by rule resolution and relevant class through a join.
SR-D61681 · Issue 532561
Handling added for different access groups updating a case
Resolved in Pega Version 8.5
When a parent flow was configured with a Wait shape to wait until any AccessChild case reached Pending-Authentication and then the “Update a case” shape was used to update the case status of child cases using a Data Transform, the Wait shape was being processed successfully but the child cases were not always updated as expected. This issue occurred when the cases were processed by users with different access groups, so the ProcessFlowDependencies agent processed the dependency. In this scenario, findPageByHandle returned an incorrect WorkPage because of the different access groups. To resolve this, pyLoadMyCasesNested Step-5 and pzProcessIndividualDepAssignment Step -13 now make additional checks to verify whether the page found by findPageByHandle API is a valid WorkPage or not.
SR-D90544 · Issue 550807
Corrected row focus for deleting in App Studio case model
Resolved in Pega Version 8.5
When attempting to delete a row of properties from the 2nd page of the data model of a case type while using App Studio, clicking on the delete icon brought up a dialog box asking for confirmation for deletion but at the same time the screen went back to the first page of the data model instead of remaining on the second page. Because of this, clicking on the OK button to confirm the deletion caused a random property from the first page to be deleted instead of the targeted row of the second page as expected. This was due to the refresh being triggered immediately within overlay UI actions, and has been resolved by updating the first trash icon action set for the section pzExpressFieldActions to be a modal instead of an overlay when launching local action.