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

INC-168914 · Issue 659660

Updates added against Cross-site Scripting

Resolved in Pega Version 8.6.1

Cross-site Scripting (XSS) protections have been updated for the UI.

INC-171257 · Issue 651733

Expanded results for Proposition Filter Relevant Record Properties

Resolved in Pega Version 8.6.1

Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.

INC-174468 · Issue 650943

Delegated rules search considers localized text

Resolved in Pega Version 8.6.1

The search / filter box used to look for particular delegated rules on the configuration tab did not consider localization via field values, where the on screen name and description of the delegated rule was localized. This resulted in the search text being compared against the original text (.pyAdviceText and .pyDescription) used for the name and description at the time the rule was delegated, but not with the localized text that actually appeared on the screen. This has been resolved by updating the pzPopulateDelegations activity to filter by localized values of pyAdviceText and pyDescription.

INC-178070 · Issue 658679

Browser invocation allowed for UnlockOperator

Resolved in Pega Version 8.6.1

Attempting to unlock an operator who was locked out due to security policies was failing. This was an unintended side effect of security work performed earlier, and has been resolved by reenabling 'Allow invocation from browser ' for pzUnlockOperator. This activity requires an authentication check with privilege protection.

INC-180603 · Issue 661738

Added protections for GetSiblings

Resolved in Pega Version 8.6.1

Cross-site scripting protections have been updated for the GetSibling activity.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us