SR-A25429 · Issue 252126
Count corrected for @getMessagesCount
Resolved in Pega Version 7.2.2
Flawed logic in the out-of-the-box activity restoreAssignment exposed a flaw in @getMessagesCount where the API used to copy error messages returned a string which is concatenation of all messages with \n delimiter, resulting in the count always being one. This has been corrected.
SR-A92563 · Issue 261301
removeDuplicatesFromList modified to remove duplicate rules based on resolution
Resolved in Pega Version 7.2.2
In DB2 zOS, the flow actions are retrieved in random order. Because of this, FixCorr was sometimes picked from Pega-ProcessEngine and sometimes picked from other rulesets such as Pega-IntegrationEngine. Since removeDuplicateFromList returns the flowaction which was last in the result set, inconsistent results were seen. There was a workaround to check the 'Disqualify this action from bulk processing' checkbox in Work-FixCorr in Pega-IntegrationEngine and Pega-Procom ruleset, but this has been resolved with an enhancement that modified removeDuplicatesFromList to remove duplicate rules based on rule resolution.
SR-A23564 · Issue 251378
pzGetAllCoveredAttachments activity tuned for better system performance
Resolved in Pega Version 7.2.2
In order to improve system performance, the pzGetAllCoveredAttachments activity has been modified to limit the scope of its SQL query to only open the cover and fetch the covered items instead of calling the generalized pzGetChildKeys function.
SR-A94678 · Issue 262223
pzGetAllCoveredAttachments activity tuned for better system performance
Resolved in Pega Version 7.2.2
In order to improve system performance, the pzGetAllCoveredAttachments activity has been modified to limit the scope of its SQL query to only open the cover and fetch the covered items instead of calling the generalized pzGetChildKeys function.
SR-A88489 · Issue 257325
Additional localization for Case Management
Resolved in Pega Version 7.2.2
Localization has been added to the text 'Simple Case' under case narrative and to values displayed under the column 'Performed by' sections in Caser Management.
SR-A92126 · Issue 261816
Bulk Action transfers all selected records
Resolved in Pega Version 7.2.2
Not all of the selected cases were being transferred when using the Bulk Actions functionality to transfer. This was due to the pySelected values to not being updated in the clipboard. To resolve this, a Refresh other section has been added to Select Action in pzBulkProcessingActionSection to update the value when clicked.
SR-A87755 · Issue 256079
Fixed Dynamic Class Reference use for the workbasket name in Wait shape
Resolved in Pega Version 7.2.2
The error "Unable to open assigned's Data-Admin-WorkBasket record" was thrown when using a Dynamic Class Reference to refer the workbasket name in Wait shape. This was traced to the Workbasket in the Wait shape being quoted, leading to the property reference not being honored. The quoting of the workbasket has been removed in the pzAfterWait.
SR-A92706 · Issue 260877
out-of-the-box Approval step section checking improved
Resolved in Pega Version 7.2.2
The out-of-the-box Approval step which takes custom section name as parameter did not work if the section was in the Framework/At work group level because the pzApprovalPreProcessing activity checked section existence using Obj-Browse, which checked only in the existing class and not in the work pool. The system has been updated to use Obj-Open in the pzApprovalPreProcessing activity to check if the section exists. This also checks if the section exists in its parent hierarchy.
SR-A76776 · Issue 254774
Pega Pulse Link Description text box handled dynamically
Resolved in Pega Version 7.2.2
To correct an issue where the Pega Pulse Link Description text box was not visible due to screen size (i.e., the Pega Pulse fields were not getting wrapped on the screen, the container for the pzLinkDescription section has been changed to use dynamic layout so it correctly adjusts according to the width.
SR-A91228 · Issue 258648
ConsiderLockingMode passed to GetNextWork
Resolved in Pega Version 7.2.2
When calling the OpenAndLockWork activity in the MoveToWorkList activity, the ConsiderLockingMode parameter was not being passed. This parameter value is checked to determine whether it is optimistic locking or not. To enhance the system, the First step of Assign-WorkList now sets the parameter ConsiderLockingMode to true/false based on based on the GetNextWork_MoveAssignmentToWorklist system setting so that optimistic locking is considered.