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-A97665 · Issue 265978

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

SR-A94083 · Issue 266677

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A97281 · Issue 263948

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A99477 · Issue 266058

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A86001 · Issue 259595

Extraneous row removed from field level auditing

Resolved in Pega Version 7.2.2

When tracking a Page list property, an extra row was being appended in the repeat layout. A null check has been added to correct this.

SR-A76763 · Issue 252485

Ensured Dirty pop up appears for mobile log off

Resolved in Pega Version 7.2.2

While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return 'if dirty' to resolve this.

SR-A96203 · Issue 270094

CreateCase rollback corrected

Resolved in Pega Version 7.2.2

While creating a sub-case and getting an error on any end-step of flow, Pega starts the rollback of the process, but was saving pxCoveredInsKeys in the Clipboard page of Case. This was a missing use case in AddCoveredWork to call RemoveFromCover if an error was thrown while creating a child case along with copying page pages from cover to primary, and has been corrected.

SR-A96203 · Issue 266909

CreateCase rollback corrected

Resolved in Pega Version 7.2.2

While creating a sub-case and getting an error on any end-step of flow, Pega starts the rollback of the process, but was saving pxCoveredInsKeys in the Clipboard page of Case. This was a missing use case in AddCoveredWork to call RemoveFromCover if an error was thrown while creating a child case along with copying page pages from cover to primary, and has been corrected.

SR-A91680 · Issue 259008

Resolved Null Pointer Error for resubmit of a corrected case with optimistic locking

Resolved in Pega Version 7.2.2

Work order case creation was throwing a null pointer exception in logs if optimistic locking was enabled on the case type and the case was resubmitted after correcting a validation error. This has been fixed with the addition of a null check for a clipboard page in use.

SR-A103064 · Issue 270247

Schema Change Tracking query performance improvements

Resolved in Pega Version 7.2.2

A query which was used in Schema Change Tracking (Designer Studio -> System -> Database -> Schema Change Tracking) was causing high CPU usage. This was due to the query having a full table scan which was using Information_schema, and the query has been rewritten for better efficiency.

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