INC-147658 · Issue 604684
Handling added for Top and Primary page references in flow action
Resolved in Pega Version 8.5.2
Handling added for Top and Primary page references in flow actionAfter upgrade, if a flow action had a class of the section which was different from the class of the flow action, the DXAPI code retrieved the section as the same class of the flow action and not the class defined in the flow action. In flow action, the section was configured be rendered in the context of page reference as Top, however, this was not handled so the section was resolved in the context of primary page. This has been resolved by adding the missing handling for Top and Primary page references in flow action.
INC-148817 · Issue 604969
Added check for ABAC policy to getassignmentdetailsinternal
Resolved in Pega Version 8.5.2
When an attribute based access control (ABAC) policy was defined on a particular class, the policy was properly applied when browsing instances of the class and directly opening the work object. However when an associated assignment was processed via the DXAPI (using the assignments service) the security was not applied and users who should not have access were able to progress the case. This has been resolved by adding a check in the pzgetassignmentdetailsinternal activity to check for work object opening security.
INC-149823 · Issue 608352
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.5.2
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField Rule-Utility-Function.
INC-
196961 · Issue 693473
Iteration method updated for SetRequiredSkillsCountColumn
Resolved in Pega Version 8.7.1
After update, database utilization spiked and did not drop. Investigation traced this to the use of Local.totalCount in pzSetRequiredSkillsCountColumn, which caused the iteration loop to run more times than necessary. This has been resolved by replacing Local.totalCount with Local.iterationsCount in the iteration.
INC-184040 · Issue 688256
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.7.1
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.
INC-186036 · Issue 685370
Field Level Audit updated to handle hierarchical properties
Resolved in Pega Version 8.7.1
Field Audit was not working for the first change of the data selected/provided for a field. The audit was only reflected after the second change was made. When the property involved a series of hierarchies, for example pageprop.pagelist(1).pageprop, the FLA objects will initially use deferred saves and the generated pzinskeys will be added to a savedFLAMap object. However, when the last pageprop was not eligible to save, all the deferred saves of earlier records were cancelled but the inskeys were not removed from the savedFLAMap object. Because of this, the parent FLA records were assumed to have been saved already when those saves were actually deferred. This was a missed use case for hierarchical properties, and has been resolved by adding an update to remove the inskeys from the savedFLAMap object so that in the subsequent property change the audit's FLA records for the parent properties (pageprop.pagelist(1)) will be saved again.
INC-194180 · Issue 701664
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.7.1
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.
INC-198765 · Issue 696686
Public URL will be appended with "/" if it is not present
Resolved in Pega Version 8.7.1
When using the Worklink Correspondence Fragment rule with authentication service type "prweb/PRAuth/sso", the returned URL did not contain the needed "/" at the end of public link. The "/" was present when using the legacy authentication service "prweb/sso". This has been resolved by updating the system to include a "/" at the end of a public URL if one is not present.
INC-198807 · Issue 689769
Bulk Transfer Audit displays correct label
Resolved in Pega Version 8.7.1
After Bulk Transferring an assignment, the audit showed the flow action rule name instead of the label. This has been addressed by creating a field value for the name 'pyTransferAssignment' and updating the param.actionLabel to refer to the localized value.
INC-200247 · Issue 701955
WorkAttachmentIcon activity correctly registered
Resolved in Pega Version 8.7.1
The pyWorkAttachmentIcon control used to download attachments was generating a SECU0019 warning. This was traced to pzAppStorageOkToAttachFile not being correctly registered, and has been resolved.