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-B16331 · Issue 303039

Check added to WorkUnlock to ensure cover page exists

Resolved in Pega Version 7.3

An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.

SR-B16331 · Issue 294717

Cover page check added to Work-Close

Resolved in Pega Version 7.3

An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.

SR-B16337 · Issue 287224

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-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-B16784 · Issue 287160

Attachments removed when work object withdrawn

Resolved in Pega Version 7.3

After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.

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

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