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-139843 · Issue 594083

WSDL for Connect SOAP documentation updated

Resolved in Pega Version 8.6

SOAP integration documentation has been updated to include information regarding handling a WSDL that contains references to external XSD documents.

INC-143033 · Issue 607836

Access Control Policy documentation updated

Resolved in Pega Version 8.6

The documentation for the ACP rule (https://community.pega.com/knowledgebase/articles/security/85/creating-access-control-policy) has been updated to clarify that these rules must be checked in for the policy change to take effect. Access control policies only work when a rule is checked in. Therefore, any changes in a checked out rule will be ignored. When changing or modifying any ABAC policy rules, the rule must be checked out, updated, saved, and checked in for the changes to take effect.

INC-145944 · Issue 612847

Product Rules help updated for Report Definition filters

Resolved in Pega Version 8.6

The Product Rules help documentation has been updated to remove references to the deprecated use of When filters and List View filters as these have been replaced by Report Definition filters.

INC-158784 · Issue 625592

Throttling during email processing help documentation updated

Resolved in Pega Version 8.6

The IMAP section of the support article for throttling email has been updated to include more detailed information about the dynamic system setting used for throttling, Pega-IntegrationEngine Email_throttling_pattern_regex, and how to configure it.

SR-SR-D89339 · Issue 550312

Ping service documentation updated

Resolved in Pega Version 8.6

The documentation for ping service architecture and output has been updated to reflect that the response now includes more parameters.The response contains JSON text in the following format: {"node_type": [""],"health": [{"last_reported_time": "","test_name": "","status": ""},{"last_reported_time": "","test_name": "","status": ""}],"state": "","node_id": ""}

INC-162881 · Issue 636992

Decision Table check-in warnings supported for large tables

Resolved in Pega Version 8.6.1

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-164002 · Issue 639912

Decision table null input handling updated for backward compatibility

Resolved in Pega Version 8.6.1

After update, 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 644705

Support added for connect-SOAP run in parallel mode

Resolved in Pega Version 8.6.1

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-164439 · Issue 657997

Setting added to customize using blank Map values

Resolved in Pega Version 8.6.1

After update to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".

INC-165256 · Issue 657038

Improvements for Offer Eligibility rules loading time

Resolved in Pega Version 8.6.1

After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.

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