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

INC-157095 · Issue 638807

Enhancement added for tenant-level authentication

Resolved in Pega Version 8.5.4

In a multi-tenant PDC with a few tenants that utilize their own custom SSO, a pre-authentication activity inside a tenant that should block community access was also affecting tenants that did not have that pre-auth activity set. This was a missed use case and has been resolved by adding a tenantId hash in SchemePRAuth.makeUniqueSchemeName() to create the authServiceName.

INC-161260 · Issue 634051

Enhanced logging for CBAC policies

Resolved in Pega Version 8.5.4

Additional logs have been added to assist in easier debugging of any configuration issues with CBAC policies.

INC-161660 · Issue 633030

Authorization token handling and cleanup improved

Resolved in Pega Version 8.5.4

When using a mobile app configured with default authentication, clicking on the "Trouble logging in?" link opened a new window and displayed the message "please contact your system administrator" along with the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY CODE-SECURITY PZGETAUTHORIZATIONCODE". This has been resolved. In addition, the OAuth token generation and handling has been improved, and the purge agent has been updated to accept a DSS setting for the max number of expired records to purge each time it is run. The default value is 5000.

INC-162434 · Issue 640052

LookUpList correctly executes during SSO login with model operator

Resolved in Pega Version 8.5.4

After configuring SSO to create operators on fly using a model operator, a new user logging in for the very first time had their operator ID created using the model operator, but after upgrade new users logging in to the system received the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST". This was due to the methods used for additional security on the activity @baseclass LookUpList which allows it to only be run by authenticated users, and 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