Support Article

Activity status error while running an activity but processing

SA-36777

Summary



When the activity pxTransferAssignment is run manually (by clicking on the run option in the activity rule form), with valid parameters, the assignment is getting transferred as expected. However, it throws an error.

The same works fine when the activity is invoked through a flow. The error is not seen.

Functionality is not impacted in both the cases.


Error Messages



Info: Database-General trying to calculate the handle of a class whose instances may not be written to the database: Assign-


Steps to Reproduce



Run the activity pxTransferAssignment is run manually (by clicking on the run option in the activity rule form), with valid parameters.

Root Cause



A defect in Pegasystems’ code or rules.

pxMethodStatus is being set to exception incorrectly, when the activity is run manually.


Resolution



Here’s the explanation for the reported behavior:

The error is because of pxMethodStatus being set to some exception which is seen in acquireWorkObject, when run manually.
This can be ignored as this does not impact the functionality.

Published May 9, 2017 - Updated October 8, 2020


100% found this useful

Have a question? Get answers now.

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