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-B7355 · Issue 277915

Actions visible in Perform harness for cases without active assignments

Resolved in Pega Version 7.3

When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.

SR-B7620 · Issue 290018

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7621 · Issue 278634

Activity created cases open correctly

Resolved in Pega Version 7.3

When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.

SR-B8696 · Issue 279855

Support added for FCM GetNextWork

Resolved in Pega Version 7.3

When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.

SR-B9998 · Issue 279141

Improved handling for apostrophe in email addresses

Resolved in Pega Version 7.3

In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.

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