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-B16337 · Issue 288963

BIX TotalInserts and TotalInstance counts made consistent for nested pages

Resolved in Pega Version 7.3

The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.

SR-B16825 · Issue 292599

WordMacroManagerDot updated for 64-bit compatibility

Resolved in Pega Version 7.3

The WordMacroManagerDot macro has been updated for Word-64-Bit environment compatibility.

SR-B16921 · Issue 287323

BIX documentation for Obj-Save help updated

Resolved in Pega Version 7.3

The BIX Extracts help file has been updated to clarify which properties are or are not updated when using Obj-save, explicitly noting that pxUpdateDateTime is not updated in the database when the Obj-save method is invoked and that a data transform should be applied to cause an update. Obj-save does update pxCommitDateTime.

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

SR-B2362 · Issue 274142

Corrected newline comparisons for pega.comparePages

Resolved in Pega Version 7.3

When mapping an external table partially to PRPC class, updating the table with Obj-Save caused the un-mapped columns to be updated to null. This was due to the comparePages API not doing an appropriate comparison whenever a property in one of the pages had a new line as a CR ("\r\n") and in the other page had new line("\n"). This has been corrected.

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