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-122025 · Issue 181153

Dropped rule added to DSM rules for SR properties

Resolved in Pega Version 7.1.8

A set of rules was inserted into the UI of Proposition LP and Strategy rules in DSM (Designer Studio) for use in retrieving a list of SR properties. This set was inadvertently missing the rule 'Activity Embed-Decision-SPContainer . pyRefreshSPList', and this has been added.

SR-122118 · Issue 180259

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-122118 · Issue 183909

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-122176 · Issue 184992

Older button visibility conditions retained after upgrade

Resolved in Pega Version 7.1.8

After migration, older button controls set to visibility "ALWAYS" and when condition "canPerform" became visibility "WHEN" and when condition "canPerform". To resolve this, the logic for the activity Embed-Harness-Section!UpgradeOnOpen has been updated to check for "VISIBILITY" first before "visible when" to retain the proper settings.

SR-122264 · Issue 182315

Preview Included Section corrected for Case Manager portal

Resolved in Pega Version 7.1.8

The Section Include preview feature was implemented with support in the Developer Studio, but was found to not be working as expected in the Case Manager Portal. This was due to a wrong 'if' condition for span identification, and the system has been updated.

SR-122305 · Issue 181630

Resolved addition of extra lines added upon RTE save

Resolved in Pega Version 7.1.8

After pasting some text (paragraph) content into the out-of-the-box RTE control and saving, new lines were inserted between paragraphs and again every time the save button was clicked, adding more lines. This was caused by a missing redundancy check within the RTE control code that is used to replace '/n' (new lines) with
in order to incorporate proper indentation when the text area is upgraded to RTE. Changes have been made to handle the carriage return case properly.

SR-122305 · Issue 183086

Resolved addition of extra lines added upon RTE save

Resolved in Pega Version 7.1.8

After pasting some text (paragraph) content into the out-of-the-box RTE control and saving, new lines were inserted between paragraphs and again every time the save button was clicked, adding more lines. This was caused by a missing redundancy check within the RTE control code that is used to replace '/n' (new lines) with
in order to incorporate proper indentation when the text area is upgraded to RTE. Changes have been made to handle the carriage return case properly.

SR-122393 · Issue 183981

Fixed error with importing a complex column layout

Resolved in Pega Version 7.1.8

After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.

SR-122393 · Issue 182288

Fixed error with importing a complex column layout

Resolved in Pega Version 7.1.8

After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.

SR-122393 · Issue 183524

Fixed error with importing a complex column layout

Resolved in Pega Version 7.1.8

After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.

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