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

SR-B13450 · Issue 284622

Null check added to joins of UserWorkList columns

Resolved in Pega Version 7.3

When attempting to join a pyUserWorkList Report definition with work class properties, blank values in the pyUserWorkList columns caused a Null Pointer exception on click of the filter icon for joined class properties/columns. This has been resolved by adding a null check.

SR-B13517 · Issue 293343

Icon alignment fixed in grids with skin inheritance

Resolved in Pega Version 7.3

The Header Title and the Collapsible Icon of a grid were misaligned due to an error in skin inheritance. The pzTemplateNewSkin1 legacy standard format has been changed to correct this.

SR-B13785 · Issue 284733

Added tenant ID check for batch thread in MT environment

Resolved in Pega Version 7.3

When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.

SR-B13785 · Issue 284743

Added tenant ID check for batch thread in MT environment

Resolved in Pega Version 7.3

When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.

SR-B13785 · Issue 278965

Added tenant ID check for batch thread in MT environment

Resolved in Pega Version 7.3

When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.

SR-B14210 · Issue 284725

Autocomplete updated to handle null resultcount from data page

Resolved in Pega Version 7.3

The autocomplete control was not rendering a list supplied by data page results due to the pxResultCount being null in the results of the datapage. The count size calculation in the autocomplete function has been reworked to resolve this.

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