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.

INC-135349 · Issue 583004

Unit Test Ruleset rules do not count against Guardrails

Resolved in Pega Version 8.3.5

Although the documentation indicates that rules in a Unit Testing ruleset should not count against the guardrail score or unit test coverage, when branching a unit test ruleset, the branch did not carry the same unit test flag value as the source ruleset and the rulesets were counted as a result. This has been resolved with an update to ignore testrulesets in guardrail and pegaunit calculations.

INC-193289 · Issue 679210

Security updated for @baseclass

Resolved in Pega Version 8.7

After update, searching for a baseclass 'when' rule returned no results. Listing the rules under baseclass in App Explorer resulted in the error "Applies To: The Class with key value(s) %40baseclass does not exist". This was an unintended side effect of security updates, and has been resolved by creating an exception path for "@baseclass".

SR-133538 · Issue 205317

Smart Prompt fixed for DT column headers

Resolved in Pega Version 7.1.9

Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.

SR-133538 · Issue 204972

Smart Prompt fixed for DT column headers

Resolved in Pega Version 7.1.9

Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.

INC-187103 · Issue 671737

Guided Tour working from Actions menu

Resolved in Pega Version 8.7

After updating from Pega 8.4 to Pega 8.5, "Manage a Guided Tour" was no longer working under a local action when called from the Actions menu on a work object. An unspecified error message appeared in the tracer. Investigation showed there was a null pointer error caused by the menu being invoked on an invalid page, and this was traced to updated authentication requirements: registration at the portal is not reliable as it is thread-scoped and run only once. The thread name is not guaranteed to stay the same so subsequent invocations of the tour activities failed. This has been resolved by modifying the call registration function to handle the security issues related to the generation of the menu path.

SR-D42402 · Issue 508895

Added differentiated handling for special symbols based on location in the label string

Resolved in Pega Version 8.2.4

While importing an Excel file into a decision table that used custom functions like@string:notequal or equal, label names like 'AlphaPrefix !=AAA' resulted in the error "invalid expression or reference: line 1:28 extraneous input '"True"' expecting {<EOF>, '-', '+', '=', '*', '/'," " . Investigation found that the problem was with the label of the column not handling the the special characters like (‘!=’, ‘<’ , ‘<=’, ‘>’, ‘>=’ ) present in the middle of the label string: the label and default operator were being updated irrespective of the location of the symbols within the string. To resolve this, DecisionTableWorkBookConverter.java has been modified to set the operator only if the special strings (‘!=’, ‘<’ , ‘<=’, ‘>’, ‘>=’ ) are present at the end of the label.

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