Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A22750 · Issue 244061

Case Stages status updated by automated process

Resolved in Pega Version 7.2.1

Case stages that were completed by an automated process and not a person maintained their default "Future" status in the Case Stages data page instead of being marked "Past". The stage completion status is determined by value in "pxCompletedBy", but this field was empty due to the automation. A check has been added to resolve this.

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-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.

SR-A24114 · Issue 246936

Removed hardcoding from pyWorkPage

Resolved in Pega Version 7.2.1

The function pzIsAFollower contains "pyWorkPage", which is hard-coded to get the handle of the Primary Page. However, if the primary page was a different named page and not pyWorkPage, an exception was generated. This has been resolved by removing the hardcoding in pzIsAFollower().An overloaded function has been created for pzIsAFollower() which takes reference page name as parameter, and the when rule which calls this utility function to pass the parameter has been updated.

SR-A24421 · Issue 247092

Case Audit section localized

Resolved in Pega Version 7.2.1

The ChangeStageAutomatic field value was not showing the localized value in audit due to the ChangeStageAutomatic field value not being properly picked when encountering a blank field. To fix this, Embed-ListParams.getHistoryList will set the localized pyMemo instead of the direct pyMemo in pyMessageKey when it is blank.

SR-A24444 · Issue 247096

Page name in pxCreateTopCase dynamically generated

Resolved in Pega Version 7.2.1

The page name of the Top case being created was hard-coded in pxCreateTopCase, causing corrupted data in FW. This has been fixed by dynamically generating the page name and removing it as well at the end of pxCreateTopCase.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us