AnsweredAssumed Answered

Is there a generally accepted way to 'cancel' a UserTask

Question asked by trevershick on Aug 9, 2011
Latest reply on Aug 10, 2011 by jbarrez
My scenario is this:

UserA submits a document for approval.
UserB is assigned the UserTask 'Approve Document'.

Before UserB can 'approve' the document, UserA decides to cancel the whole workflow.

What is the generally accepted way to implement this case?
We have tried to 'delete' the user task, but this causes the flow to end properly (after a signal).
I've also tried to 'complete' the task with a status = 'Cancelled' and then use a decision on the flow to go to an alternate end.

It seems like there should be a simpler way to 'cancel' this user task (maybe with a boundary event) that would then stop the workflow by transitioning to an alternate endState.

Note - i'd like to have visibility into the system to see that this 'cancellation' of the workflow actually occured, so i don't think i want to 'delete' a process instance unless that would be accessible later.

Please help. I'd like to do this in the most correct manner possible.

Outcomes