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-B13020 · Issue 283559

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

SR-B13020 · Issue 283078

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

SR-B13040 · Issue 293380

Improved reliability for GetReference API

Resolved in Pega Version 7.3

A sporadic issue with the OOB getReference API caused a failure in obtaining the absolute reference for a parameterized data page. This was caused by a race condition in the page handler, and synchronization has been improved to ensure the proper name will be set into the data page.

SR-B13040 · Issue 293526

Null DPI check added for async page load

Resolved in Pega Version 7.3

A null pointer exception was being generated when a data page was being loaded from the asynchronous cache and some exception occurred while switching the access group or getting a definition. To avoid this, a check has been added for a null DPI.

SR-B13088 · Issue 287632

SLA correctly reset after reassignment

Resolved in Pega Version 7.3

When the SLA values were updated on routing the task, the newAssignPage and assign table were updated with the new SLA details but the pxFlow page was still holding the old SLA values. This caused the updated SLA details to not be displayed in the out-of-the-box pyAssignmentListGadget section. This was an issue with the pxAdjustSLA and Reassign activities not completely updating the embedded page pxFlow in the WorkPage completely, and has been fixed.

SR-B13315 · Issue 284499

Accessibility updated for flow action label

Resolved in Pega Version 7.3

Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.

SR-B13315 · Issue 284499

Accessibility updated for flow action label

Resolved in Pega Version 7.3

Accessibility tools such as JAWS were not reading out the flow action label. This has been fixed.

SR-B13418 · Issue 283237

Attachments removed when work object withdrawn

Resolved in Pega Version 7.3

After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.

SR-B13431 · Issue 283632

Mobile App description localized in PegaExpress

Resolved in Pega Version 7.3

The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.

SR-B13431 · Issue 283681

Mobile App description localized in PegaExpress

Resolved in Pega Version 7.3

The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.

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