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-A7485 · Issue 216800

Visible When Conditions working for buttons in Harness

Resolved in Pega Version 7.2

Due to changes in the condition expression formatting, Visible When Conditions were not working as expected for buttons in the harness after upgrade. A check has been added to evaluate the structure and apply the correct visibility expression.

SR-A7679 · Issue 217201

Wrap text working with accessibility

Resolved in Pega Version 7.2

When accessibility was turned on, the wrap text was not functioning properly due to the handling of white-space:nowrap in iconRequired class. This has been corrected.

SR-A4005 · Issue 211179

Check added to pass value instead of parameter name from icon control

Resolved in Pega Version 7.2

After upgrade, an issue was found with passing a property to an activity from the deprecated icon control: instead of the value of the property, the property name itself was passed to the parameter of the DoAction activity. A check has been added to the generateButton RUF to catch property references and populate the property value at run time instead of the property name as a literal value.

SR-A6169 · Issue 204154

Corrected compilation error when using param.value in Repeat Layout label

Resolved in Pega Version 7.2

A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.

SR-A4720 · Issue 212449

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.

SR-A733 · Issue 207631

Edited Propositions retain format

Resolved in Pega Version 7.2

When updating a Proposition using the "Edit" button, the format was lost, however updating the proposition using the "Bulk Edit"-> 'Edit in Excel' button preserved the formatting. This has been addressed by making the default UI control for the text values a Text Area, which maintains the multi-line format.

SR-A8526 · Issue 218436

Added missing property call for correspondence rule

Resolved in Pega Version 7.2

Opening a rule using "Prompt HTML" and "Validation" from any correspondence rule generated the error "Unable to open the rule as Base Class Value is empty". This was caused by a hidden field that was missing the pzCorrTypeClass property needed to open the rule, which has now been added.

SR-A9044 · Issue 218037

Ampersand encoding added to "Create Work" flow handling

Resolved in Pega Version 7.2

In order to ensure the "Create Work" action correctly handles a flow with a parameter containing an ampersand "&" character, the system has been updated to encode the parameter's value when replacing the Change tracker token with the actual value.

SR-A4927 · Issue 214148

Subsequent HTTP requests now properly access ReloadHarness

Resolved in Pega Version 7.2

In some scenarios, ReloadHarness was generating the error "This action is not allowed as it is outside the current transaction." on subsequent HTTP requests. This was caused by improper population of the URL on the work page at that point in the reloading of the function, and has been corrected.

SR-A7746 · Issue 217225

Updated harness unload for RTE

Resolved in Pega Version 7.2

The Section ID stamped on RTE's TextArea element and the ID on the section div were different, causing stale RTEs to not be nullified or removed from harness elements after a refresh section. The harness unload has been updated to use the correct section ID.

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