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-A8824 · Issue 217931

Operator information localized

Resolved in Pega Version 7.2

Localization has been enabled for the pzOperatorInformation section.

SR-A3713 · Issue 214995

Added 'Enter key' configuration for CaseAttachments delete icon

Resolved in Pega Version 7.2

It was not possible to trigger the delete icon in the Attachments pane using the Enter key when using pyCaseAttachments from UI-Kit. This was due to DOM automatically mapping the click event to Enter / Space for trigger elements like buttons while the Enter event needed to be configured explicitly for icons. To simplify this, an extra event ?Enter key? configuration has been added for the existing Click action for the Delete icon in pyWorkAttachmentsFeedElement section.

SR-A3008 · Issue 219945

Check added to handle Next button disable for repeat grid

Resolved in Pega Version 7.2

The 'Next' button on a modal dialog was not disabled correctly when launched from a repeat grid due to the wrong "currentPageSize" being passed to the server when using an expand pane grid. A check has been added that will handle the expand pane grid and return the right "currentPageSize".

SR-A9773 · Issue 221357

Fixed repeating row focus when using Accessibility

Resolved in Pega Version 7.2

When Accessibility was enabled and the add icon was clicked to add a section to a row repeat, it was not possible to access the first item in first row with the keyboard. Additional added rows had the correct focus. This was traced to an issue where getFocusOnNewRow was not being called correctly, and as been resolved.

SR-A9513 · Issue 220450

Handling corrected for undefined model parameters

Resolved in Pega Version 7.2

If model parameters were set to undefined, refreshing the harness using F5 / Browser refresh. encodeURIComponent method returned "undefined (String) value". This was an issue with the deferred loading of the dynamic container, and has been corrected.

SR-A9554 · Issue 220841

Resolved NPE in UpdateElementModel

Resolved in Pega Version 7.2

An index check has been added to to handle a NullPointerException in UpdateElementModel activity and ensure the index is greater than zero before accessing the page list.

SR-A10762 · Issue 221765

Expressions allowed in trend report config

Resolved in Pega Version 7.2

Configuring a trend report using an expression for the summary view caused the execution error "Failed to find a 'RULE-EDIT-INPUT' with the name; no rules with this name were found in the rulebase". This has been resolved by reworking the 'if' condition in the JS method editInput.

SR-A8509 · Issue 220449

Corrected indexing with Composite/User portal

Resolved in Pega Version 7.2

After upgrade, the PRXML was not being updated and Data and Rules were not being indexed properly if the "Rule-Portal.pzDesktopSubtypeChange" data transform had the pyDesktopTypes set to Composite and the desktop type was set to user. This was due to an issue with the value domain for the pyDesktopType property, and has been corrected.

SR-A11303 · Issue 222793

Set proper Field Value to localize section headers with "&"

Resolved in Pega Version 7.2

The localization value was not getting picked up for a section header containing '&'. This was due to the section being configured as Text, and it has now been properly configured as a Field Value.

SR-A9913 · Issue 220331

Corrected accessibility on harness confirm message

Resolved in Pega Version 7.2

On moving out from Perform to Confirm Harness after completing a process, JAWS was not reading the confirm message first as expected. This was due to the confirm message not being updated in any of the live regions which would allow it to be read by Assistive Technology products, and has been resolved by creating a live region and updating the confirm message in the live region.

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