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-169186 · Issue 655537

Disconnect button availability extended

Resolved in Pega Version 8.7

A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.

SR-D70310 · Issue 537140

Window type check added for icon display logic

Resolved in Pega Version 8.5

When a Role had privileges to use Live UI, Agile WorkBench and Scenario Testing, the Scenario Testing tool icon intermittently did not show. This was traced to an incorrect condition used to check whether current window was of type desktop (portal) window, and has been resolved by adding a check that will also ensure consistency with Agile Studio icon display logic.

SR-D89672 · Issue 550526

Custom error label styles work for 'required'

Resolved in Pega Version 8.5

When using the default 'required' error message, the class "labelError" is added when the required field is empty. However, when the default 'required' is replaced by a custom error message, a UI error was seen because the class "labelError" was not added when the field was empty. This was traced to an error in the non-template to template code transform, and has been resolved by updating webwb_pzpega_ui_dlcelltemplate_js to add the labelError class based on the presence of an error message.

INC-190380 · Issue 678643

CreateVersion rule updated for REST Integration Wizard

Resolved in Pega Version 8.7

When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.

INC-190380 · Issue 678644

CreateVersion rule updated for REST Integration Wizard

Resolved in Pega Version 8.6.3

When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.

SR-D83476 · Issue 550786

Layout Group (Tab) keyboard navigation behavior made consistent

Resolved in Pega Version 8.5

When using keyboard navigation for Layout Groups (tab), arrow keys (up/down/left/right) are used to navigate the tabs once focus is set on the first tab, and the tab contents of each tab is opened automatically. It was noted that pressing tab a few more times caused the second tab to gain focus, but the contents of the tab did not open automatically or when enter was pressed, which was unexpected behavior. For accessibility best practices, tab focus should not be allowed on tab groups. To resolve this issue, this has been removed and the system will continue to follow auto activation of tabs on arrow keys.

INC-185255 · Issue 669441

More responsive attachment loading for interaction portal

Resolved in Pega Version 8.7

Attempting to view a large email attachment in the interaction portal was resulting in slow loading and page responsiveness issues. Investigation showed there were numerous unnecessary height calculations happening when checking the dom elements, and this has been resolved with an update which will use the property mapping js file to make the screen more responsive when highlighting.

INC-164429 · Issue 633222

Map address control works in read only view

Resolved in Pega Version 8.7

The pyTrackingMap control was not showing position when used in read-only mode. This was traced to a missed use case, and was caused by the property handle being considered in order to get the value of the current address, but in the case of read-only the property handle was empty and the address field was considered. To resolve this, in case of a read-only track map, the addressproperty value will be considered instead of the property handle.

INC-178834 · Issue 660425

RDA support added for Citrix XenApp

Resolved in Pega Version 8.7

Robot Runtime was not working in a Citrix XenApp environment when using the JWT token generated by the D_pxRoboticJWTToken data page to identify the user. This has been resolved by updating the scope of the datapage D_pxRoboticJWTToken from node level to requestor, which will allow the user information in the JWT token to be passed to the routing service and support the use of RDA in Citrix environments.

INC-169545 · Issue 649519

Localization updated for decimal slider

Resolved in Pega Version 8.7

When using the Indonesian locale, selecting the range on a slider which allowed selection of a decimal / double value that was then displayed in another textbox caused the value to increase incrementally and the slider always showed the end max. Investigation showed that this was caused by the handling of the comma decimal separator used in Indonesia, and has been resolved by updating the handling to ensure the slider value is converted to the respective locale.

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