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

SR-D33359 · Issue 505773

SelectAll properly applied to only the page selected

Resolved in Pega Version 8.2.4

In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.

SR-D37444 · Issue 507038

WorkBasketGadget control updated for improved backwards compatibility

Resolved in Pega Version 8.2.4

After upgrade, the WorkBasketGadget Control was not retrieving the work queues. This was traced to a backwards compatibility issue introduced when greater security was put in place. The control WorkBasketGadget contains a call to pzEncryptURLActionString that was introduced in 8.x versions of the platform to encrypt URLs to avoid hijacking. The content of the URL relies on the pxRequestor.pxWorkGroup property, which is resolved using pega:reference tags. This approach was working in versions below 8.x, but these tags were not resolved at runtime. To correct this, requestorWorkGroup will be resolved as string and passed as a parameter instead of using pega:reference tags.

SR-D26785 · Issue 495892

Corrected error when persisting temporary work object

Resolved in Pega Version 8.2.4

When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.

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