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-B94242 · Issue 348085

Case creation

Resolved in Pega Version 7.4

The Interaction API was not able to create cases due to a 'when' rule modification that was missing. This has been fixed.

SR-B95152 · Issue 341223

Leading spaces preserved in Pega Pulse

Resolved in Pega Version 7.4

Multiple white spaces in div will be shown as single space by browser at run time, leading to Pega Pulse appearing to trim leading spaces from lines using the pxFeed section and User-submitted formatting not being preserved. To resolve this, the white-space CSS property of .pulse-display-post CSS class has been modified to use pre-wrap.

SR-B95830 · Issue 344260

Better handling for case updating when switching applications

Resolved in Pega Version 7.4

When using two applications, the application 1 case lifecycle view was shown at login. After switching to application 2, the case life cycle was not updated until the refresh icon was clicked. This was an issue with the pyCurrentCase value not being updated while switching apps, and an additional condition has been added to the pzSetCurrentCase Data transform to better handle application switching.

SR-B95971 · Issue 348613

Fixed switching back to previous chat interaction after close

Resolved in Pega Version 7.4

When using CPM to handle multiple Chat Interactions that involve switching between them, clicking on the 'x' (close) icon of a case was not resulting in a proper switch to the previous case: the work area was switched, but the case tab was not switched. This was traced to the browser cancelling all of the async requests triggered from the document upon unload, causing the pzUpdateClipboardModel request to not execute. The asyncrequest API has now been updated to properly support the sync requests.

SR-C1747 · Issue 345146

Parameter CoverPage passed to Close from CreateWorkPage

Resolved in Pega Version 7.4

After configuring a parent case and a child case where the child case calls the "CreateWorkPage" activity, the pyWorkCover page of the child was not appearing in the clipboard. This was due to a missed use case for the Parameter CoverPage being passed to Close activity from CreateWorkPage activity, and has been fixed.

SR-C57 · Issue 344928

Check added for Manage Participant work parties

Resolved in Pega Version 7.4

Expected work parties were not displayed in Manage Participant due to a missed use case. A check for the prefix "|" has been added before removing the repeatable work party in step 4 of pyGetWorkPartyOptions & getWorkPartyOptions activities.

SR-C9329 · Issue 350197

Duplicate cases issue fixed

Resolved in Pega Version 7.4

Duplicate cases were shown in worker case compensation due to a case-sensitive values check. The 'when' condition has been modified to correct this.

SR-C9808 · Issue 351050

Resolved duplicate assignments in app

Resolved in Pega Version 7.4

Assignments were being duplicated in the app due to the system using a stale cover page. This has been corrected.

SR-B81527 · Issue 331290

Silverlight error fixed for LaunchWordMerge

Resolved in Pega Version 7.4

The WordMerge functionality was not working for a Mash-up on a website, displaying a Silverlight error. This occurred when using AppDynamics software for the user environment, and was traced to the pyheadercookiesset including an ADRUM cookie. Because there was an unescaped character added in the cookie, it failed on XML reader parsing in Silverlight. Handling has now been added for the special character.

SR-B82808 · Issue 331981

Correspondence Message in the audit history no longer truncated

Resolved in Pega Version 7.4

Because SendSimpleEmail sets pyLabel to the first 64 characters of pySubject and pyLabel is limited to 64 characters, messages in the audit history were often truncated. In order to allow the full correspondence subject to be included in the audit history message, pySubject has been modified to use Param.MemoForEmail in SendSimpleEmail and pass it to CorrAttach activity to add the complete subject in the history.

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