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

Obj-Open-By-Handle fails with Exception Alert (EXCP0001)



User makes a change in one of the property types from Text to Value List such that Obj-Open-By-Handle fails for the existing work objects. The property holds the older value of the property type with StepStatus to enable the users to identify the old work objects. However, Obj-Open-By-Handle fails with an exception and the user is unable to log the erroneous work objects.

Error Messages

Exception Alert (EXCP0001)

Steps to Reproduce

  1. Create a case type and a related property 
  2. Set Type to Text
  3. Create two work objects for the newly created case type
  4. Create a ruleset version
  5. Withdraw the property created
  6. Create another ruleset version
  7. Change the type of the property to Value List
  8. Create an activity to Obj-Open-By-Handle the old work objects
  9. Verify if the StepStatusGood is True to record the IDs of the work objects

Root Cause

An issue in the custom application code or rules. The exception occurs when the Tracer is on and the user runs the activity. The Tracer expands the property during the activity execution. The exception occurs as there is a difference in the property type.


Perform the following local-change:
  1. Do not trace the activity while running it
  2. Use the property to get the desired StepStatus after Obj-Open-By-Handle
Suggest Edit

Published December 2, 2021

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