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

SR-A6547 · Issue 217014

Updated handling for empty keys in DataSet-Execute

Resolved in Pega Version 7.2

When executing a 'delete by keys' operation in a DataSet-Execute method, passing empty keys would intermittently cause the whole dataset to be truncated or deleted. To create a more robust execution environment, when a Dataset-Execute is called and no key is passed it will trigger a delete statement matching the key value to null.

SR-A6629 · Issue 216162

Updated group authentication for populating Batch Processing landing page

Resolved in Pega Version 7.2

pyApplication and pyApplicationVersion were not getting populated when running a data flow from the Batch Processing landing page that used information from system pages. This was an issue with the system pages not being included in the proper authentication group, and has been resolved.

SR-A8103 · Issue 216452

DSM thread CPU consumption resolved

Resolved in Pega Version 7.2

In certain installations, a DSM thread that was not properly sleeping after the system was upgraded caused degraded performance. This has been corrected.

SR-A8236 · Issue 217418

Removed default overriding threads per node setting of Topology page

Resolved in Pega Version 7.2

The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not being taken into account by the data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was traced to a default value overriding the setting from this page, and the code has been updated to correctly reflect the setting being used.

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