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-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.

SR-B46050 · Issue 302190

Corrected DateTime corruption

Resolved in Pega Version 7.3

If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.

SR-B462 · Issue 271962

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-B4620 · Issue 277531

Fixed dirty prompt save UI error

Resolved in Pega Version 7.3

The dirty prompt save action was causing corruption in the UI if there were validation errors present. This was traced to the On save of a work object with errors replacing the harness with section. As a result, styles and scripts in harness were lost and only plain/raw html was shown. This has been fixed by removing the Show-Stream step so Show-Harness takes care of refreshing the screen.

SR-B46365 · Issue 303375

Error check added for ID/label mismatch on field labels

Resolved in Pega Version 7.3

When an UploadFileFlow was created, tabbing through fields with blank values updated most of the field labels with the revised style when an error was present, but Date kept its original style. This was due to an issue setting error styles on a property if the label and identifier of a property were different. To handle this, the code has been modified to such that if the identifier of a control and shown text are different, a check in "findLabelFor()" will fail.

SR-B46718 · Issue 304110

pyFLowSLA property added to support pxObjClass change

Resolved in Pega Version 7.3

Validation errors occurred when using a data transform which changes the pxObjClass of primaryPage. Pega Platform tries to validate internally for all the properties during the page change class; in order to support the DT, the new property pyFlowSLA has been introduced. The previous pxFlowSLA property has been deprecated.

SR-B47060 · Issue 303231

Fixed BulkActions filter reset

Resolved in Pega Version 7.3

In the Bulk Actions page, adding a new filter property caused the other conditions to be reset incorrectly. To resolve this, checks have been added to see if there is already a filter condition configured in the Embed-FCondition.pzDefaultOperators.

SR-B47227 · Issue 304654

Requirements template sets Excel input cells as text for security

Resolved in Pega Version 7.3

For increased security in Pega Platform Excel files, the Requirements template has been changed to set all the input cell types as text instead of general.

SR-B47384 · Issue 303522

Fixed focus reset for page number click in grid layout

Resolved in Pega Version 7.3

An anchor element generated for the active page in a repeat grid had "#" as href but did not have an onclick handler defined, causing a click of the Page number in a Grid layout to move focus to the top of the page. This has been corrected with the addition of an onclick handler in pzGridActivePage custom control for inactiveLink in 123 pagination.

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