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-A19119 · Issue 241157

Improved error handling for XML-executed BIX extract failures

Resolved in Pega Version 7.2.2

When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.

SR-A76706 · Issue 252781

Modified pyLoadDataTypes data transform to match expected type

Resolved in Pega Version 7.2.2

Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.

SR-A77495 · Issue 254777

Corrected delete error with first row of Decision Table

Resolved in Pega Version 7.2.2

After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.

SR-A67932 · Issue 251208

Blank query field in Bulk Actions defaults to none instead of all

Resolved in Pega Version 7.2.2

Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.

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