SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).
SR-A63731 · Issue 251489
FilterHistory WRITE_NONE correctly stops all audits
Resolved in Pega Version 7.2.2
Changing the system settings rule "FilterHistory" from WRITE_SOME to WRITE_NONE was still running an audit when the stage changed instead of completely stopping all auditing. This was due to an RUF call to ADDHISTORY without checking the DSS, and a check has been added to fix this.
SR-A77379 · Issue 254823
FilterHistory WRITE_NONE correctly stops all audits
Resolved in Pega Version 7.2.2
Changing the system settings rule "FilterHistory" from WRITE_SOME to WRITE_NONE was still running an audit when the stage changed instead of completely stopping all auditing. This was due to an RUF call to ADDHISTORY without checking the DSS, and a check has been added to fix this.
SR-A76390 · Issue 253683
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-A24732 · Issue 248383
Better character escape handling for "&" in case notes
Resolved in Pega Version 7.2.2
If any notes were added that contained at least one "&" symbol, the subject could unexpectedly be seen in the detailed view modal window of the case notes. This was caused by the escape handling for the symbol, and has been corrected.
SR-A76381 · Issue 252860
Customizable when added for PegaPULSE delete button
Resolved in Pega Version 7.2.2
In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.
SR-A76381 · Issue 252811
Customizable when added for PegaPULSE delete button
Resolved in Pega Version 7.2.2
In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.
SR-A24719 · Issue 252331
Correct Bulk processing status when no transfer occurs
Resolved in Pega Version 7.2.2
Searching by Work bulk processing was not transferring items when there were multiple assignments yet was showing a Transferred status and not displaying an error. This was traced to a missing 'when' condition check in the handling, and has been fixed.
SR-A67005 · Issue 251958
Work-.Close function updated to resolve "Flow not at task" error
Resolved in Pega Version 7.2.2
The Work-.Close function has been updated to improve synchronization between operators in cases where having a combined standard flow and screen flow as a sub flow could cause a "Flow not at task" error as one operator moved forward and the other subsequently tried to save an already open work object.
SR-A76914 · Issue 252778
Short Description parameter cleared every loop to ensure data integrity
Resolved in Pega Version 7.2.2
When adding the coverable work types in a case, the description which comes in the Actions menu was not correct due to the Short Description parameter not being cleared. This caused the same description to be used for the next flows. To fix this, the system will now clear the parameter Short Description in the activity LookupCoverableProcessList at the end of every loop, ensuring every flow takes its own short description.