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-D92158 · Issue 555085

App Studio performance improvements

Resolved in Pega Version 8.4.2

In order to improve performance for opening data models, submitting changes, and opening views in App Studio, pzShowDataTypeInExpress has been modified to remove a readonly condition that caused a database query for every row.

SR-D93112 · Issue 554909

Added backwards compatibility for migrated when rules

Resolved in Pega Version 8.4.2

After upgrading from v6 to v8, the 'when' rules were replaced with "" in a custom decision tree. In 7.2 and earlier releases, the Rule-Obj-When function alias had its param name as "strName"; this was changed to "blockName" in later versions of Pega. To handle backwards compatibility, the pzEmbedUpgradeToHarnessBased activity has been modified to read the strWhen param value from pyCallParams and set it to blockName params correctly under pyFunctionData.pyParameters data model, conditionally only for Rule-Obj-When function alias.

SR-D93787 · Issue 558842

Tooltip added to LHS anypicker control

Resolved in Pega Version 8.4.2

A Tooltip has been added to the LHS anypicker control, allowing the display of longer when and strategy rule names on hover of the anypicker control.

INC-125281 · Issue 562797

Rulesets removed from direct invocation ability

Resolved in Pega Version 8.4.2

Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.

INC-125706 · Issue 565518

Expression Builder test functionality updated to improve context resolution

Resolved in Pega Version 8.4.2

After upgrade, running a test in Expression Builder to evaluate an expression resulted in a 'Property undefined' error. Although the test functionality failed, the data transform rule was properly saved and no issues were observed at runtime. This was traced to a change made in the way the IDs on input elements were made unique. This caused an issue with Expression Builder resolving the correct context when the Source property page was not the primary page class, such as in these cases:1) For Each Page with the "Also use each page as source context" checkbox checked 2) Update page using the "with values from" 3) Append and Map to with "an existing page" 4) Append and Map to with "each page in" To resolve this, the pzEBHiddenElement function has been updated.

INC-125803 · Issue 568663

Cross-site scripting updated for pzTransformAndRun

Resolved in Pega Version 8.4.2

Additional Cross-site scripting work has been done on the pzTransformAndRun activity.

INC-126813 · Issue 565864

Handling added for Decision Table test case with "call"

Resolved in Pega Version 8.4.2

Clicking on the Convert to test button to launch a Test Case rule form did not load all of the options to create the UTCs, and the screen seemed stuck on the message “Loading..”. This was a corner case that happened when the decision table's return value had "Call" in it: the table believed there was the need to call another decision table, which was traced to "Call" being present on the RUT's label values. To resolve this as avoid regressions, quotes have been added to the returned value so that the value is picked instead of trying to call another decision table.

INC-127291 · Issue 562778

Rulesets removed from direct invocation ability

Resolved in Pega Version 8.4.2

Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.

INC-127981 · Issue 563001

Rulesets removed from direct invocation ability

Resolved in Pega Version 8.4.2

Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.

INC-131175 · Issue 571610

Branch rule deletion updated

Resolved in Pega Version 8.4.2

When two branches, for example Test1 and Test_1, were created and the rules were saved, deleting the Test1 branch also deleted the rules in Test_1, resulting in the remaining branch Test_1 not having any rules. This was traced to the Obj-List method in activity DeleteRuleset fetching the incorrect results, and has been resolved by replacing it with a report definition created in Data-Rule-Summary.

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