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-A27796 · Issue 250774

Click of phone link preserves chart display

Resolved in Pega Version 7.2.2

A click on a "Telephone" link that generated a prompt for the user to allow access for launching an external application caused the charts used on the screen to disappear. To fix this, the pxFormatTelephone rule has been modified to add an onclick handler.

SR-A33704 · Issue 250630

Repeating grid refresh handling improved for mouse click location

Resolved in Pega Version 7.2.2

A numeric field in a repeating grid referenced by a Declare Expression with a "refresh on change" did not always persist the changed value on the clipboard. This was traced to a handling difference in the code where if the mouse was clicked somewhere outside the row being edited the section refreshed and the value reverted back to the previous value, but if the mouse was clicked within the row the value updated correctly. This has been fixed by updating the logic in isElementDirty to better consider number and decimal type controls.

SR-A22996 · Issue 250572

Logic updated for 'when' controlled edit modes in embedded sections

Resolved in Pega Version 7.2.2

Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.

SR-A22996 · Issue 252883

Logic updated for 'when' controlled edit modes in embedded sections

Resolved in Pega Version 7.2.2

Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.

SR-A22996 · Issue 248338

Logic updated for 'when' controlled edit modes in embedded sections

Resolved in Pega Version 7.2.2

Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.

SR-A62629 · Issue 250580

Improved format conversion handling added for Work Objects with custom date format

Resolved in Pega Version 7.2.2

Custom Date format was throwing an invalid date format error when trying to add an attachment to the Work Object if the read-only date format for one of the properties was given as DD-MMM-YYYY and it was displayed on the UI in the same format. In this issue, the entire form was submitted while uploading the file and the error occurred because the format was different from what the server was expecting. To resolve this issue, handling has been added to convert the date/time value to/from the expected format when interacting with the server.

SR-A23683 · Issue 247601

Error highlights fixed in tabbed navigation

Resolved in Pega Version 7.2.2

Due to a missing style call, the highlight on tabbed navigation was removed when errors occurred on that screen. This has been fixed.

SR-A17941 · Issue 249577

Resolved maximized RTE tab blanking

Resolved in Pega Version 7.2.2

If the Rich Text Editor was opened and maximized in a modal window tab using a dynamic container, navigating away and returning to the tab resulted in the RTE tab being blank. This was an issue with the resize function relating to Quirks mode, and a check has been added to resolve the problem.

SR-A17941 · Issue 249820

Resolved maximized RTE tab blanking

Resolved in Pega Version 7.2.2

If the Rich Text Editor was opened and maximized in a modal window tab using a dynamic container, navigating away and returning to the tab resulted in the RTE tab being blank. This was an issue with the resize function relating to Quirks mode, and a check has been added to resolve the problem.

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