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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

SR-A24797 · Issue 247605

Localization added to reassign statement in Audit -> History

Resolved in Pega Version 7.2.1

The Audit->History reassign statement "This assignment has been reassigned to Operator ?, as ? is unavailable" was not localized due to the string being hardcoded without using field values. Localization has been added through the newly created field value ROUTINGREASSIGNEDTOSUBSTITUE to be used in the checkForSubstitute function.

SR-A27978 · Issue 248681

"Grand Total" localized

Resolved in Pega Version 7.2.1

Localization has been added for the pyFieldCaption property "Grand Total" .

SR-A62507 · Issue 249049

"Grand Total" localized

Resolved in Pega Version 7.2.1

Localization has been added for the pyFieldCaption property "Grand Total" .

SR-A8117 · Issue 227498

Assign-pzResetAssignmentSLA retains SLA on drag and drop

Resolved in Pega Version 7.2.1

The out-of-the-box Assign-pzResetAssignmentSLA activity passed "Workpage" as parameter instead of "param.WorkPage", causing assignments that were dragged and dropped in the Case Manager portal to lose their SLAs. To resolve this, the Assign-pzResetAssignmentSLA activity has been updated to pass param.WorkPage instead of WorkPage

INC-128571 · Issue 584752

Auto-process assignments cleanup improved

Resolved in Pega Version 8.6

After configuring auto process with an assignment at the flow end, the perform harness was being presented at the end of the assignment during runtime. This was the result of the newAssign page not being removed as part of the cleanup after auto-processing was done, causing the performB2BAssignmentCheck activity to believe the next assignment existed. This has been resolved by ensuring that auto-process assignments have the newAssignPage removed after the assignment is deleted.

INC-134113 · Issue 591542

Child case locking error message has correct parameter

Resolved in Pega Version 8.6

A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value.

INC-135335 · Issue 588511

Parent flow next step will take precedence over sub-process

Resolved in Pega Version 8.6

ABreadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.

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