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-B89155 · Issue 337930

Case stages correctly displayed in Microsoft Internet Explorer

Resolved in Pega Version 7.4

Case stages were not being properly displayed when using Microsoft Internet Explorer. This was due to the UI kit version of the "pxDisplayStages" rule using the Dynamic Layout with inline format, causing the parent div to not be used for width in Microsoft Internet Explorer. This has been fixed.

SR-B89321 · Issue 337392

Display cases in each stage properly refreshing

Resolved in Pega Version 7.4

The report from GetWorkInStage which displays cases in the stage was not refreshed/reloaded when a different stage was clicked. This was due to the report parameters not being considered while opening the report, resulting the system displaying the existing opened report even though it had different filter parameters. The dynamic container (pzpega_ui_dynamiccontainer) - reportDefinition API has now been modified to consider report parameters and reload the report with new parameters as expected.

SR-B92095 · Issue 342336

Resolved exception on added nested case

Resolved in Pega Version 7.4

An exception was being generated when attempting to add a case which had a child case. This was due to a missing check for an empty coveredInskey, and has been fixed.

SR-B92186 · Issue 342002

Removed max for case dependency updating children

Resolved in Pega Version 7.4

If more than 50 child cases existed for a Parent Case, case dependency was only being updated for a maximum of 50 cases. The others remained parked at the same state as before the parent case was updated. This limit has been removed by eliminating pagination from the pzGetChildCases report definition.

SR-B94242 · Issue 341369

Case creation works in Interaction API

Resolved in Pega Version 7.4

It was not possible to create cases in the pyInvokeInteraction Interaction API due to a missing property. This has been corrected.

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.

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