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.

SR-D28965 · Issue 501857

Repository document deletion modified for better cleanup

Resolved in Pega Version 8.2.4

When using documents functionality, creating and uploading a document properly stored it, but deleting the document did not remove the associated files from storage. Whenever a document is created that has a file, instances Of Link-Attachment and Data-WorkAttach-File are also created. Previously, when the document was deleted, the associated instances and actual file were not deleted from the repositories but rather marked as Resolved-Withdrawn and hidden at the UI level. The system has now been updated so that when a document is deleted, the document attachment will also be deleted from all places like list, Tile, and document View, and reference instances like Link-Attachment and Data-WorkAttach-File instance will also be removed along with the actual file from the repository.

SR-A92680 · Issue 263151

Removed duplicate repeat grid header

Resolved in Pega Version 7.3

An extra Grid Header Title was created when allow refresh on update was checked in a repeat grid configured for row editing via modal dialog. This was due to a place holder div error, and has been corrected.

SR-B385 · Issue 270797

ASCII characters properly displayed in dynamic layout headers

Resolved in Pega Version 7.3

When using a field value that contains special characters like + and = to display the header value of a dynamic layout the characters were being converted to their encoded ASCII characters on screen (ex [&] instead of [&]). This was traced to the Field Value text being encoded twice, and the GridHeaderElements function has been updated to correct this.

SR-A100782 · Issue 272266

Siteminder block resolved for DPParams containing double quotes

Resolved in Pega Version 7.3

Due to the DPParams being transmitted in JSON format, using the Siteminder CSSChecking parameter set to yes with BadCSSChars containing "%22" caused the " (double quotes) that surround the name value pairs to trigger a Siteminder block. To resolve this, the system will pass the DPParams in the post body instead of sending it in the query string.

SR-A101144 · Issue 272239

Error message clear after bad row deleted

Resolved in Pega Version 7.3

Error messages were not clearing even after deleting the row which caused the error. This has been corrected.

SR-A101500 · Issue 279633

Menubar Object memory leak repaired

Resolved in Pega Version 7.3

A memory leak has been resolved by eliminating unnecessary DesktopMouseClick events when creating a new old-Menubar object.

SR-A101500 · Issue 278178

Menubar Object memory leak repaired

Resolved in Pega Version 7.3

A memory leak has been resolved by eliminating unnecessary DesktopMouseClick events when creating a new old-Menubar object.

SR-A101675 · Issue 270578

Size to Content refresh updated

Resolved in Pega Version 7.3

A expandable grid with a text area and button as columns in it was not correctly calculating the size after refreshing. An explicit call to the resizeHarnessActual has been added to ensure expected behavior.

SR-A103192 · Issue 271775

ReadOnly radiobutton display fixed for null value

Resolved in Pega Version 7.3

When a radiobutton control was set ReadOnly, "--" was not displaying as expected when the property did not contain any value. Instead, the radio button values were displayed as empty. This was caused by a missing span tag element for read only mode, and has been fixed.

SR-A87830 · Issue 258083

PD4ML JAR updated

Resolved in Pega Version 7.3

Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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