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

INC-164944 · Issue 636292

Logic updated to handle decision trees over 64k

Resolved in Pega Version 8.5.4

Logic updated to handle decision trees over 64kAn exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.

INC-168094 · Issue 642627

Security updated for help URL infrastructure

Resolved in Pega Version 8.5.4

Cross site scripting protections have been added to the help URL infrastructure.

SR-A8387 · Issue 217780

Added prevention for inappropriate Google Chrome autofill

Resolved in Pega Version 7.2

When login userid and password were stored in the Google Chrome browse and autofill was enabled, Google Chrome was using those values to populate the RuleSet rule form's input field (hidden on UI on Versions tab) and password field (on the Security tab). Those invalid values caused a save failure. To fix the issue, the system will pre-populate the hidden input field so that Google Chrome does not auto fill this field on the client side.

SR-A3950 · Issue 209476

Corrected order of tabbing focus in Activity rules

Resolved in Pega Version 7.2

After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.

SR-A5453 · Issue 215368

Fixed Edit in Excel with load balancing enabled

Resolved in Pega Version 7.2

Edit in Excel was not working for decision tables if a load balancing was enabled. This was traced to the load balancer port number being added to the RequestHomeURL, causing a malformed strURL for opening the decision table in Excel. A check has been added to evaluate whether the strURL starts with a proper protocol and host instead of checking for RequestHomeURL.

SR-133163 · Issue 203273

Refined property-set expansion to support complex activities

Resolved in Pega Version 7.2

Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.

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