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-B42218 · Issue 300079

Updated logic check for property panel invalid actions

Resolved in Pega Version 7.3

Configuring invalid actions on the events & actions property panel was not triggering the validation messages when submitted, saved, and checked-in. When the action was re-opened, no changes were saved. This was due to a segment of code called on load of the property panel that remained for backwards compatibility but should not have been called in this scenario. This has been fixed by adding a check at the top of this activity for messages/errors which will route the logic appropriately.

SR-B42262 · Issue 303693

Field Values displayed correctly in mobile dynamic layouts

Resolved in Pega Version 7.3

Dynamic layout headers that reference Field Values were not displayed correctly in the mobile application. This was caused by the getLocalizedValueFromList function not passing activeContext to the resolveParams function, and has been fixed.

SR-B43160 · Issue 299701

Fixed up/down arrows for Firefox modal dialogs

Resolved in Pega Version 7.3

Up and Down arrows actions were not working in modal dialog text boxes when using Firefox. This was a defect in the framework, and has been addressed in modaldialog js.

SR-B43621 · Issue 300812

Back/Previous years calculation fixed to use current year

Resolved in Pega Version 7.3

In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.

SR-B43665 · Issue 301542

Accordion layout resizes correctly with IAC

Resolved in Pega Version 7.3

The "Accordion" layout was behaving incorrectly when the browser window was resized, preventing scrolling to the bottom of the page. This was an issue with layout groups configured with accordion not triggering a harness resize when clicked, and has been fixed.

SR-B4391 · Issue 275319

GenerateGridHTML updated for JAWS version compatibility

Resolved in Pega Version 7.3

An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".

SR-B44426 · Issue 300990

New JS APIs added to get section streams

Resolved in Pega Version 7.3

In order to support getting section stream(s) using JS API's, the following new JS APIs have been added to the pzpega_api_ui_actions actions JS file: pega.api.ui.actions.getSection(sectionName, contextPage, callback) pega.api.ui.actions.getSections(sectionName, contextList, callback)

SR-B44591 · Issue 301046

Color issue fixed for last value ranges

Resolved in Pega Version 7.3

An "Invalid XML" error was generated when trying to apply different colors for different ranges of values in the advance UI control "Charts" > "Gauge Half Arch". This has been fixed.

SR-B45435 · Issue 301778

GenerateGridHTML updated for JAWS version compatibility

Resolved in Pega Version 7.3

An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".

SR-B45917 · Issue 302415

DisplayReport date made consistent between report and exported PDF

Resolved in Pega Version 7.3

When exporting a report to PDF, the "Generated on" date did not match the format on the report. This was caused by the system using different controls for date in pzDisplayReportSectionForPDF and displayReportSection, and has been resolved by changing the date format specified in pzDisplayReportSectionForPDF to match that in displayReportSection.

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