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-160288 · Issue 626068

Kerberos handling updated for database remap

Resolved in Pega Version 8.5.3

After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.

INC-133951 · Issue 584149

Try catch added for templated refresh when

Resolved in Pega Version 8.5.3

After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to+F386 DynamicLayoutGenerator.java.

INC-137875 · Issue 608102

Update for special characters in operator name

Resolved in Pega Version 8.5.3

Handling has been added for encoding an operator full name field which contains special characters.

INC-139086 · Issue 597146

"Show next error" correctly displayed on user portal

Resolved in Pega Version 8.5.3

In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.

INC-139739 · Issue 598902

Cross-Site Scripting protection update

Resolved in Pega Version 8.5.3

Cross-Site Scripting protections have been updated for labels.

INC-141302 · Issue 614994

UI automation script documentation update

Resolved in Pega Version 8.5.3

To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.

INC-143363 · Issue 604363

Added handling for maintaining on-change event descriptor

Resolved in Pega Version 8.5.3

The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.

INC-144522 · Issue 612323

Portal primarythread copied to workprocessing thread to establish proper class

Resolved in Pega Version 8.5.3

Attempting to add a new item/row in a table configured in a modal dialog in the home page of the Cosmos portal was not working, and the error "Section 'TestSection' execution error on page 'pyWorkPage' of class 'CosmosApp-Work-TestCaseType'. : For input string: "" appeared. This was a missed use case for pyPortalHarness, and was caused by the primarypage not getting copied to the workprocessing thread which led to some actions failing as classless. This has been resolved.

INC-144572 · Issue 600757

Corrected mobile tab layout highlighting

Resolved in Pega Version 8.5.3

When switching between three tabs in a layout group (Other � Mobile Tabs) in a section, the highlight was appearing on the active tab and the inactive tabs. This has been resolved by updating the CSS generation to not consider hover styles for touchable devices.

INC-144709 · Issue 608798

Removed unnecessary decoding from GetDropdownOptions

Resolved in Pega Version 8.5.3

When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.

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