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-121435 · Issue 563875

Handling added for null requiredskillcount on assignment

Resolved in Pega Version 8.2.7

If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.

INC-122149 · Issue 562783

Corrected approval step task message

Resolved in Pega Version 8.2.7

When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.

INC-127077 · Issue 564107

Busy indicator appears when uploading via Select

Resolved in Pega Version 8.2.7

After update, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.

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