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

Setting added to customize using blank Map values

Resolved in Pega Version 8.5.5

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 657036

Improvements for Offer Eligibility rules loading time

Resolved in Pega Version 8.5.5

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 659661

Updates added against Cross-site Scripting

Resolved in Pega Version 8.5.5

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

INC-171257 · Issue 651732

Expanded results for Proposition Filter Relevant Record Properties

Resolved in Pega Version 8.5.5

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-174435 · Issue 659481

Survey Complex Question Definition properly displayed

Resolved in Pega Version 8.5.5

Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".

INC-174468 · Issue 650944

Delegated rules search considers localized text

Resolved in Pega Version 8.5.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 658677

Browser invocation allowed for UnlockOperator

Resolved in Pega Version 8.5.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-179111 · Issue 659476

Toolbar delete handling modified

Resolved in Pega Version 8.5.5

After upgrade from Pega 7.4 to 8.5, the toolbar delete button behavior was different. Previously, the pzRuleFormToolbarDeleteRule section rule invoked RuleFormMain on refresh, but the updated version was calling RuleFormHeader, preventing the deletion of the assignment from the class instance. This was an unanticipated edge case and has been resolved by updating the action in the button to refresh the section RuleformMain instead of header.

INC-180468 · Issue 659924

JAWS correctly reads work group header

Resolved in Pega Version 8.5.5

While creating the groups within the organizational unit, JAWS was reading the name of the frame as "Process Work Area" instead of "Create Work Group" and "enter data" instead of the name of the edit field with edit instructions. This has been resolved by adding a property to the short description label so it contains the instance type that is being created.

INC-180603 · Issue 661741

Added protections for GetSiblings

Resolved in Pega Version 8.5.5

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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