SR-A22841 · Issue 245073
All Data Flow keys considered for filtering
Resolved in Pega Version 7.2.1
When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.
SR-A23035 · Issue 245109
Enabled bulk delete of ADM models
Resolved in Pega Version 7.2.1
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."
SR-A23222 · Issue 244490
"Deadline date" corrected for German locale
Resolved in Pega Version 7.2.1
When a case was opened, the deadline shown in the top was in the wrong format for a German locale. This was caused by the standard translation method being used, and has been corrected by replacing the non-auto-generated pyCaseDeadline control with pxDateTime control to fix the issue.
SR-A23378 · Issue 248193
Max limit removed from OperatorsInWorkGroup
Resolved in Pega Version 7.2.1
The Report Definition pzOperatorsInWorkGroup previously returned a max of 50 records per work group. This created difficulty when using pyTransferAssignment with groups larger than that. In order to facilitate large installations, this limit has been removed.
SR-A23395 · Issue 245032
Optimized decision data components
Resolved in Pega Version 7.2.1
Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.
SR-A23395 · Issue 243235
Optimized decision data components
Resolved in Pega Version 7.2.1
Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.
SR-A23668 · Issue 245756
Corrected syntax for pyAdjustAssignmentSLA
Resolved in Pega Version 7.2.1
An extra space present in the label prepended for pxTaskLabel caused severe warnings to be generated by pyAdjustAssignmentSLA that were lowering the application compliance score. This syntax error has been corrected.
SR-A23689 · Issue 245765
Unnecessary diagnostic message removed from logging
Resolved in Pega Version 7.2.1
The Server log of PegaRULES was displaying the confusing message "Here Thru the Branch Code": this was an unnecessary diagnostic trace and has been removed.
SR-A23817 · Issue 246191
Enabled SLA calculations for drag and drop reassignments
Resolved in Pega Version 7.2.1
SLA was not firing when an assignment was dragged and dropped from a workbasket to a work list and vice versa. This was due to a missing update to the assignment handle for the queue item, and has been fixed.
SR-A23997 · Issue 248204
ResumeFlow copied to @baseclass to support Split For Each Advance flow
Resolved in Pega Version 7.2.1
Split For Each Advance Flow Fails on Data Instances with error: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'RESUMEFLOW'. This was traced to the context of the assignment being on a Data- instance while ResumeFlow is defined at Work-, causing all processing to fail for the resume. This has been fixed by creating a version of ResumeFlow in @baseclass which in turn calls Work- ResumeFlow.