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.

INC-139300 · Issue 590273

Additional security for encrypted passwords

Resolved in Pega Version 8.3.5

Handling and cleanup has been updated for encrypted values to enhance security.

INC-141296 · Issue 592474

Log-access security updated

Resolved in Pega Version 8.3.5

Access control has been updated for Log-Usage class.

INC-139337 · Issue 595222

RefreshRequestors security update

Resolved in Pega Version 8.3.5

Security improvements have been added for RefreshRequestors.

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-128923 · Issue 594162

Cross-site scripting security update

Resolved in Pega Version 8.3.5

Cross-site scripting protections have been added to OpenNoteDetails.

INC-143136 · Issue 604016

Cross-site scripting update

Resolved in Pega Version 8.3.5

Cross-site scripting protections have been updated in Designer Studio.

INC-162881 · Issue 636993

Decision Table check-in warnings supported for large tables

Resolved in Pega Version 8.5.4

After adding an empty row in the middle of Decision Table rows and checking in, the Decision table rule's CheckIn form shows a functionality warning about a conflict in decision table ("This rule contains 1 logic conflict(s). Click the 'Show Conflicts' button for more details."). However, this behavior did not occur as expected if the decision table had more than 500 cells in it, and has now been resolved.

INC-163970 · Issue 636137

Expression Builder updated for special character handling

Resolved in Pega Version 8.5.4

If a modulo operator (%) was used in expression builder, the expression showed the correct value when it was submitted (closed) but on reopen the expression was changed and not calculated correctly. If the expression was not reopened then it calculated the value properly. This issue was traced to a server call to pzEvaluatePegaExpression which treated certain values as containing special characters, and has been resolved by updating the handling for this scenario.

INC-164002 · Issue 639913

Decision table null input handling updated for backward compatibility

Resolved in Pega Version 8.5.4

After upgrade, any null values as inputs in the decision tables were skipped if "Allow Missing properties" was not checked. This behavior was different from previous versions. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.

INC-164171 · Issue 635868

Support added for connect-SOAP run in parallel mode

Resolved in Pega Version 8.5.4

When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.

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