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-A7679 · Issue 217201

Wrap text working with accessibility

Resolved in Pega Version 7.2

When accessibility was turned on, the wrap text was not functioning properly due to the handling of white-space:nowrap in iconRequired class. This has been corrected.

SR-A4720 · Issue 212449

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.

SR-A8526 · Issue 218436

Added missing property call for correspondence rule

Resolved in Pega Version 7.2

Opening a rule using "Prompt HTML" and "Validation" from any correspondence rule generated the error "Unable to open the rule as Base Class Value is empty". This was caused by a hidden field that was missing the pzCorrTypeClass property needed to open the rule, which has now been added.

SR-A9044 · Issue 218037

Ampersand encoding added to "Create Work" flow handling

Resolved in Pega Version 7.2

In order to ensure the "Create Work" action correctly handles a flow with a parameter containing an ampersand "&" character, the system has been updated to encode the parameter's value when replacing the Change tracker token with the actual value.

SR-A4927 · Issue 214148

Subsequent HTTP requests now properly access ReloadHarness

Resolved in Pega Version 7.2

In some scenarios, ReloadHarness was generating the error "This action is not allowed as it is outside the current transaction." on subsequent HTTP requests. This was caused by improper population of the URL on the work page at that point in the reloading of the function, and has been corrected.

SR-A7746 · Issue 217225

Updated harness unload for RTE

Resolved in Pega Version 7.2

The Section ID stamped on RTE's TextArea element and the ID on the section div were different, causing stale RTEs to not be nullified or removed from harness elements after a refresh section. The harness unload has been updated to use the correct section ID.

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.

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