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-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-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-A85804 · Issue 255413

Support added for Word2016 with macro templates

Resolved in Pega Version 7.2.2

After creating a document in Word 2016 based on a Pega macro as the template, saving the document and closing it would lead Word to crash the next time the document was reopened. This was traced to a file conflict between in Word2016 and the macro file, and has been resolved by updating the Office2010 version WordMerge macro file to enable the support of Word2016.

SR-A89074 · Issue 258503

Resolved upgrade issues with ConnectSOAP using MTOM

Resolved in Pega Version 7.2.2

After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element" . Analysis showed the base64binary was not being substituted correctly with the expected "XOP Include" element. Axis uses Axiom to write Multipart messages and multiple XOP writers are involved in writing and encoding the message. When the writer stream is flushed , it depends on SimpleNsStreamWriter to write the bytes. SimpleNsStreamWriter is currently packaged as part of WStx-2.3-asl.jar and webservices-rt.jar, but this was not true in previous versions. As a result after upgrade, Webservices-rt classes is taking precedence over wstx-asl classes, which was generating the XOP:include elements with inline content. For better backwards compatibility, the WS-TX jar references have been removed from the webservices-rt.jar so that now it will rely on wstx-asl-3.2.3.jar which is already shipped with the product.

SR-A20058 · Issue 257774

PEGA0020 alert updated for full interaction time

Resolved in Pega Version 7.2.2

An error with PAL timer statements caused an Null Pointer Error during connect SOAP execution due to socket read time not being accounted for in the PEGA0020 alert. This has been fixed.

SR-A22183 · Issue 249190

Elements given correct default value in XML

Resolved in Pega Version 7.2.2

An issue was found where blank tags were being created for node elements given a default value in the XML Stream rule. Analysis showed that when the optional element in the XML Stream rule was set with "" and had a default value, the "StreamXML/DetectEmptyProperties" empty string was getting displayed in the output XML instead of default value. This 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