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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D39577 · Issue 507203

Dynamic Layout Group renders properly when nested sections use PageGroup as source

Resolved in Pega Version 8.2.5

After upgrade, an included Section rule was not rendered in Dynamic Layout Group (repeat) layout at run time. This issue was only seen when PageGroup was used as the source for the dynamic layout group, and investigation showed that under these conditions the pagegroup state for nested sections was not propagating a needed editable property. This has been corrected.

SR-D40762 · Issue 510369

ReloadSection passes event object explicitly

Resolved in Pega Version 8.2.5

After upgrade, 'replace current-model' was not working when used in a section with a link control that had an onClick event that was intended to launch a local action. Investigation showed that the link control was not working in the latest Google Chrome version, and this has been corrected by passing the event object explicitly to the reloadSection function in PZPEGA_UI_DOC_SUBMIT.js

SR-D40778 · Issue 512975

Asterisk symbol displayed for radio button set to required always

Resolved in Pega Version 8.2.5

When marked as required, the "Asterisk" symbol did not show up on the radio button label. This was traced to an XML cleanup issue with the pyReqRunOnClient property when required was configured as 'always' and has been corrected.

SR-D40941 · Issue 512592

Identifier property added for worklist with filter by format

Resolved in Pega Version 8.2.5

After configuring a Grid layout which displayed a users worklist, one of the properties representing the column in Grid had the property type as boolean. The property was derived from another report definition in the main report and a join was performed to display the property. Investigation showed that the filter for Boolean column did not show any filter values like ( [No Value, Y,N ) when run through a case Manager Portal, however the Boolean Column filter worked when run through Report Definition. Other properties from the same class that were not boolean worked with the filter. This was traced to the WorkListWidgetGridsAuto being set to Optimize code, causing filter by format to not be visible in the column properties of pxPages. To resolve this, code has been added for the identifier property

SR-D41035 · Issue 513205

Handlign added for OpenAssignment triggered from confirm harness

Resolved in Pega Version 8.2.5

Triggering openAssignment from the confirm harness was replacing the whole Ajax container DIV, leading to 'submit' no longer working. This has been corrected by adding additional handling for this usage.

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.

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