Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with Resolve activity and findPageByHandle



When resolving a child case by using the out of the box UpdateStatus activity and passing the status as "Resolved-Rejected", the assignments in the parent case are also getting deleted even though the parent case is not resolved.

Error Messages

Not Applicable

Steps to Reproduce

Resolve a child case.

Root Cause

A defect in Pegasystems’ code or rules where scenarios in which a page other than pyWorkCover was used to house the parent case are not properly handled.


Perform the following local-change: Utilize pyWorkCover to house the parent case.

A side effect of this local change was found. When the child object is resolved, the parent/cover object is incorrectly considered stale and is subsequently reopened. This results in the current locking strategy being lost.

The root cause of this side effect was found to be a problem with how Pegasystems' Resolve activity determined if the parent/cover object was stale, which allowed false positives to be returned when the activity was executed on a platform stack utilizing a SQL Server database. As SQL Server's datetime columns are accurate to the 1/300th of a second, exposed columns occasionally contain a datetime value different than the corresponding datetime value in the blob. Pegasystems' Resolve activity did not properly take this into account when determining if the parent/cover object was stale. HFix-36067 was created to address this side effect.

Suggest Edit

Published August 26, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us