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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B17037 · Issue 289405

Handling added for SP initiated logins

Resolved in Pega Version 7.3

Attempting a Service Provider (SP) initiated login request caused the error "The Response did not contain any Authentication Statement that matched the Subject Confirmation criteria" to appear. This was due to the code used to identify whether the flow is IDP initiated or SP initiated SSO not having the handling for encrypted assertions. The system has now been updated to look for the relay state in the DB: if an entry is present then the SSO flow will be SP initiated, otherwise it will be IDP initiated.

SR-B17080 · Issue 289244

saveAllOrNone API more robust for multi-tenant shared BIX

Resolved in Pega Version 7.3

Intermittent errors appeared when two BIX command line extraction scripts were running in parallel when both used BixUser_Tenant as the operator. This was traced to the saveAllOrNone API, which was not equipped to prevent other nodes from writing data into the DB while the current thread was also trying to write that same data to the DB. Further diagnostics are required to formulate a solution to this intermittent error, but the API has been made more robust: the system will not throw an IllegalStateException when the DB exception is DuplicateKeyException.

SR-B17100 · Issue 290607

Optimistic locking fixed for GetNextWork

Resolved in Pega Version 7.3

The optimistic locking feature was is not working as expected when GetNextWork was invoked. This was caused by missing parameter passing, and has been fixed.

SR-B17270 · Issue 288020

XSS filtering added to Autocomplete highlighting

Resolved in Pega Version 7.3

XSS filtering has been added to Autocomplete highlighting for better security.

SR-B17338 · Issue 294731

Corrected and improved calculations for multiple page Business Calendars

Resolved in Pega Version 7.3

The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.

SR-B1734 · Issue 272443

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B1734 · Issue 272039

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B17355 · Issue 289241

Accessibility improved for properties in accordion layout

Resolved in Pega Version 7.3

The screen reader was reading the property name for Properties configured on Accordion Layout titles instead of the content of the property. This has been fixed.

SR-B17403 · Issue 297717

Resolved concurrent mod exceptions when using getValueInType API

Resolved in Pega Version 7.3

Concurrent modification exceptions were observed in the logs when the getValueInType API was called to fetch property values from multiple threads. To resolve this, the getValueInType API has been made thread safe by synchronizing its access.

SR-B1753 · Issue 274602

Null dr handling added for VDB startup

Resolved in Pega Version 7.3

VBD was unable to start due to unexpected null values in the 'dr' column of the partition summary table in Cassandra. To handle this, handling has been added for the possibility of a null value when loading data from the partition table.

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