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-169203 · Issue 646099

Robotics Desktop Automation correctly runs on subsequent tabs

Resolved in Pega Version 8.4.5

When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.

INC-174468 · Issue 650945

Delegated rules search considers localized text

Resolved in Pega Version 8.4.5

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 658424

Browser invocation allowed for UnlockOperator

Resolved in Pega Version 8.4.5

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

Decision table null input handling updated for backward compatibility

Resolved in Pega Version 8.7

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 644707

Support added for connect-SOAP run in parallel mode

Resolved in Pega Version 8.7

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 657995

Setting added to customize using blank Map values

Resolved in Pega Version 8.7

After upgrade 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 657037

Improvements for Offer Eligibility rules loading time

Resolved in Pega Version 8.7

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-167037 · Issue 650991

SmartpromptType classes shown in Rule-Admin-Skill

Resolved in Pega Version 8.7

Some class instances were not showing in SmartpromptType list. This was traced to the activity LookUpList, which is called from Rule- class in Rule-Admin-Skill, using pyClassName as one of the filter criteria in Java Step1. Therefore Rule-Admin-Skills did not show in SmartpromptType list. This has been resolved by overriding LookUpList for Rule-Admin-Skill class so it will not consider pyClassName as a filter criteria.

INC-168692 · Issue 642009

Regex corrected for USZipCodeExtended validation

Resolved in Pega Version 8.7

Edit Validate - USZipCodeExtended was not working as expected. Instead of validating 5 numbers followed by 4 numbers, it was validating for 5 numbers followed by 5 numbers. This has been corrected.

INC-168885 · Issue 663668

Corrected restoring lockable data class

Resolved in Pega Version 8.7

After opening an instance of a lockable data class and deleting it and then restoring it, the system reported an error that a lock can't be held on the instance. This only happened for lockable data instances that were deleted and restored immediately, and as a work around the item could be restored successfully from from the History- instance. To resolve this, the pzRMActionRecoverDeleted activity has been updated to copy to a temporary page and take action instead of acting on the primary page.

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