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.
SR-A19119 · Issue 241157
Improved error handling for XML-executed BIX extract failures
Resolved in Pega Version 7.2.2
When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.
SR-A76706 · Issue 252781
Modified pyLoadDataTypes data transform to match expected type
Resolved in Pega Version 7.2.2
Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.
SR-A77495 · Issue 254777
Corrected delete error with first row of Decision Table
Resolved in Pega Version 7.2.2
After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.
SR-A67932 · Issue 251208
Blank query field in Bulk Actions defaults to none instead of all
Resolved in Pega Version 7.2.2
Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.