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.
SR-A24246 · Issue 248666
Event size difference on calendar corrected
Resolved in Pega Version 7.2.2
When using the out-of-the-box calendar gadget to display some events apart from the worklist goals and deadlines, an event shown on the calendar was correct in the monthly view but had the wrong time and duration in the daily view. This was traced to the way the height of the div tag was calculated in different functions, and has been corrected.
SR-A38578 · Issue 253239
Population handling added for null value flowType property
Resolved in Pega Version 7.2.2
While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.