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.

INC-182530 · Issue 695760

SAML datapages cleared before new authentication

Resolved in Pega Version 8.7.1

If a previous user had not logged out or timed out when using SAML authentication, a second person using the same device/browser would end up in the first user's session after performing their own authentication. Investigation showed the second login D_SAMLAssertionDataPage was not getting refreshed with the current user login details; this has been resolved by explicitly deleting the SAML Datapages before processing a new login if the session has not timed out.

SR-D71105 · Issue 532189

Corrected error when using CharCounter in non-template mode

Resolved in Pega Version 8.2.6

An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.

SR-D82298 · Issue 544631

Corrected error when using CharCounter in non-template mode

Resolved in Pega Version 8.2.6

An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.

INC-195519 · Issue 698497

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.7.1

Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.

INC-195511 · Issue 693219

Check added for child join class when using ABAC

Resolved in Pega Version 8.7.1

When a join was applied on a report definition and the same join class had a child class to which ABAC was applied (for some property eg., isABC), an "invalidreference" exception (isABC) was generated. This was traced to the system taking into account the child class of the join class while running the report, and has been resolved by adding a check to handle this scenario.

SR-D74247 · Issue 542916

Resolved errors when using Build Model from the Preview Console

Resolved in Pega Version 8.2.6

Using the Web Chatbot interface and trying to perform Build Model action from Preview Console failed with multiple errors, either "This action is not allowed as it is outside the current transaction" or "class <blank> doesn't exist". This was traced to issues with the transaction during model update, and has been resolved by conditionally disabling the show page step of pzGetModelProcessStatus. This step creates a difference in the context of the current transaction and is disabled when called from Update API.

SR-D38492 · Issue 505491

Batching now enabled when using IH Summary shape in substrategies

Resolved in Pega Version 8.1.7

Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.

SR-D48881 · Issue 514602

Corrected alignment of column header and content when fixed header is used

Resolved in Pega Version 8.1.7

The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.

SR-D26133 · Issue 500723

Corrected alignment of column header and content when fixed header is used

Resolved in Pega Version 8.1.7

The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.

SR-D28898 · Issue 501653

Corrected alignment of column header and content when fixed header is used

Resolved in Pega Version 8.1.7

The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.

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