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

SR-B2093 · Issue 277296

Corrected page passivation for parameterized data pages

Resolved in Pega Version 7.3

A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.

SR-B2191 · Issue 275647

Fixed Chrome position resetting with proposition change

Resolved in Pega Version 7.3

When duplicating a proposition in Chrome, any change in an attribute refreshed the screen and reset the scrollbar all the way to the top. This has been fixed.

SR-B2228 · Issue 273457

WordTextArea control updated for IE

Resolved in Pega Version 7.3

Erratic behavior was seen in saving and displaying a Word document when launched from the WordTextArea control. This was a compatibility issue with IE, and the DoLaunchExtWord function has been modified to fix 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