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-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.

SR-A12587 · Issue 224456

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

SR-A8396 · Issue 218579

Corrected duplicate work object IDs

Resolved in Pega Version 7.2

The out-of-the-box section pyAssignmentListGadget was generating duplicate work object ids when pyAssignmentsLabel was used to display the case/Assignments label & ID in Case contents. This was caused by changes made in a previous version intending to enhance the displaying of labels, and has been modified to avoid duplicate workobjectIDs.

SR-A8848 · Issue 219083

Correct class being passed in SubProccessTab flow

Resolved in Pega Version 7.2

n the pzSubProcessTab section. the value for the "RuleClassProperty" was not being passed as blank to the pzRuleCallParamsWrapper section when the flow was defined on the current page and was instead defaulting to Work Pool Class. The system has been modified to pass the proper class.

SR-A9211 · Issue 220239

Corrected highlighting in calendar gadget

Resolved in Pega Version 7.2

When using the calendar gadget, selecting the weekly view generated a blue box around the monthly tab instead of the expected weekly tab. An error in the section reload was causing the focus to move to the next action element, and this has been corrected.

SR-A10178 · Issue 219880

"ExportToExcel" activity updated to match Java API upgrade

Resolved in Pega Version 7.2

After upgrade, the "ExportToExcel" out-of-the-box activity was returning an error when clicking 'save as' on the rule in application ruleset. This was caused by the code in the activity not being upgraded after the Java API version was upgraded, and has been corrected by updating the "ExportToExcel" activity.

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