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.

INC-204256 · Issue 701949

Helper Text displays for radio buttons with 'when' condition

Resolved in Pega Version 8.8

The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).

INC-204349 · Issue 704561

Updated check for portal name with search

Resolved in Pega Version 8.8

After update, using search from a Cosmos portal landing page launched the results in a new tab, and the logoff menu did not show which portal was being used. This has been resolved by updating the 'when' rule to check if pxThread.pxPortal contains the portal name rather that testing for equality.

INC-205394 · Issue 706789

Hidden subprocess steps highlighted in screen flow navigation

Resolved in Pega Version 8.8

When a subflow was used as a last step within a screenflow and the subflow steps navigation links were hidden, the subprocess step was not highlighted as current. To correct this an update has been added that will highlight the circle on the navigation for a subprocess set as last step with substeps hidden, and the lines on the navigation step will be highlighted on the left side for a subprocess set as a step other than the last step and which has substeps hidden.

INC-205517 · Issue 705990

Corrected clearing filters in mashup

Resolved in Pega Version 8.8

After clearing filter on a table, the screen did not reload and is hidden in Iframe in Mashup. This has been resolved by adding code to trigger the resizeHarness action for clear filters in a mashup configuration.

INC-206058 · Issue 709519

Property label correctly highlighted after validation failure

Resolved in Pega Version 8.8

The property label was not changing to red after validation failed. This has been resolved.

INC-206220 · Issue 717873

Listener timeout added for fetching external content

Resolved in Pega Version 8.8

Email listeners became stuck and did not recover if there was an issue retrieving external content for a message. To resolve this, a timeout setting has been added when fetching external content.

INC-206401 · Issue 699717

DIrty dialog supported for multiselect and anypicker

Resolved in Pega Version 8.8

The dirty check confirm popup was not displayed after adding items in multiselect or anypicker and then clicking on cancel. This has been resolved by adding special handling with a value property that will store the selected values necessary for this operation.

INC-206483 · Issue 707090

Delegated rules page displays proper warning in Vietnamese

Resolved in Pega Version 8.8

Opening the "Configuration" left navigation item for delegated rules and clicking on edit to modify the rule did not display the guardrail warning message properly in Vietnamese. This has been resolved by ensuring the Vietnamese date time is properly formatted as "Ngày dd tháng M năm yyyy".

INC-206577 · Issue 704421

ParentKey handling updated for for CS portal

Resolved in Pega Version 8.8

After creating an interaction in the CPM portal and refreshing the CPMPerformIncludes section (top-level section in the Perform harness) on button click, the focus was set to the first property and a large number of "Uncaught harness context does not exist" error appeared on the console and the screen became frozen. Analysis showed that after the refresh the parentKey property was empty, causing the flow to be executed in the wrong context. This has been resolved by adding a condition to set the parentKey for CS portal 'Add document' scenarios.

INC-206773 · Issue 708376

ScreenFlow called from Dataclass section completes as expected

Resolved in Pega Version 8.8

When calling a screen flow from a section of another screen flow, the flow did not work properly in the modal dialog screen flow but did work in the process flow. Investigation showed that when the second screenflow was opened from the Data class section, the assignment of the first screenflow was not deleted post submission. This has been resolved by adding a conditional block for screenFlow Dataclass section.

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