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.

SR-D41114 · Issue 508945

Localization added for 'NoResultys Found"

Resolved in Pega Version 8.2.5

It was not possible to translate/localize the message 'No Results Found' (autocomplete) to Spanish due to auto complete not containing any property or field value corresponding to this message. This has been corrected by adding the field value and corresponding code handling needed.

SR-D41130 · Issue 510079

Handling added for precision decimals in cascading dropdown on mobile

Resolved in Pega Version 8.2.5

A cascading dropdown with a parameterized datapage configuration containing decimal values with precision (such as 22.3,20.000) showed the values as expected on desktop, but the values were empty on mobile. The values did show on mobile as well if precision was not used. This has been resolved by updating templateengine_context so that decimal values will not be treated as a property reference.

SR-D41882 · Issue 510092

Resolved Ajax container blank tab

Resolved in Pega Version 8.2.5

When using an Ajax container in tabbed mode, opening a work item from the dashboard and clicking on the Begin button resulted in the Workitem closing automatically and the main tab becoming blank. This was rtaced to the system attempting to set the last tab header before it was created, and has been resolved by removing an instantiateTabs call in the success callback of the close MDC tab functionality in the pzpega_ui_redux_impl file.

SR-D41984 · Issue 510012

Added handling to correct '&' displayed as '&amp,' in custom tab name

Resolved in Pega Version 8.2.5

When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&amp," instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.

SR-D42583 · Issue 514486

Label of a field is correctly rendered when a section is re-used with a visiblity condition

Resolved in Pega Version 8.2.5

The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.

SR-D42701 · Issue 510922

Cross-site scripting security added for Case Manager

Resolved in Pega Version 8.2.5

Cross-site scripting security has been added to the Document features in the Case Manager portal.

SR-D43141 · Issue 512434

Support added for iFrame Mashup resize when using SPA

Resolved in Pega Version 8.2.5

After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.

SR-D43468 · Issue 511643

Includes() function changed for Microsoft Internet Explorer compatiblity

Resolved in Pega Version 8.2.5

The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer, resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.

SR-D43627 · Issue 509800

Keyboard tab support added added for Focus on Date control

Resolved in Pega Version 8.2.5

It was not possible to use the Tab key to move to a section with date control to launch it, and hitting enter when on a calendar did not open it. To resolve these, tabindex has been added for date/time focus and the calendar will open on enter.

SR-D44546 · Issue 512599

Corrected opening collapsible rows with modal action inside a nested pane grid

Resolved in Pega Version 8.2.5

After expanding the second level of a collapsible row in a table and then collapsing the row back down again, trying to expand other rows in the table did not work and the error "Unable to get property 'target' of undefined or null reference" appeared on the console. This was an issue with a modal action configured inside a nested pane grid that was attempting to call a target key on an undefined object, and has been resolved by explicitly checking for the existence of the 'event' object before calling the 'target' key on it.

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