Question
CGI
SE
Last activity: 16 Nov 2018 17:09 EST
Issue with pxDeleAssignment activity
There are two assignments in system and trying to delete one assignment (assume stale) on submission of other assignment. The stale assignment is getting deleted but current assignment is not moving to next stage or to next assignment.By default It's showing confirm harness and need to open the case again to proceed with case in advance .
I see, below flow message Info in tracer .
trying to calculate the handle of a class whose instances may not be written to the database: Work-: code: SQLState: Message
Pega Version is 7.3
Pegasystems Inc.
FR
Hello,
Did you set the "param.Commit" to false on pxDeleteAssignment?
Because I think if pxDeleteAssignment is doing a Commit the remaining work on current assignment might be failing due to lock been lost maybe.
CGI
SE
Yes. we are not commit the assignment .
Pegasystems Inc.
FR
Can you share the tracer output?
CGI
SE
Attached the tracer output
Pegasystems Inc.
FR
Thank you.
Usage of pxDeleteAssignment activity is saying the following: This activity can be called standalone or from a flow utility shape. If UpdateHistory is set to true it will add a History entry about the Deletion of assignment.
Can you call it from a utility shape for a quick try instead of calling it from your activity.
CGI
SE
Currently,pxDeleteAssignment api is being invoked from flow utility itself. Does it make any difference to invoking it from other flow utility instead of directly refer it?, However, I'll give try ?
CGI
SE
The reason of using the pxDeleteAssignment activity is , pxChangeStage Api is not deleting the open assignments ,which are created using Spin off shape / StartFlow activity
CGI
SE
Used Ticket feature to clean up assignments (https://collaborate.pega.com/question/delete-open-assignment-change-stage)