This content has been marked as final.
Show 3 replies
-
1. Re: Best practices for cancelling a workflow
dslevine Mar 25, 2007 1:29 PM (in response to pwfarwell)I am handling this in my workflow application similar to the second way you are considering, by adding a "cancel" node and linking that with transitions. I only link it to the major nodes though, and assume that it can make it to a major node before being cancelled.
I would be curious to hear others' design opinions on this topic. -
2. Re: Best practices for cancelling a workflow
catlinit Mar 27, 2007 8:31 AM (in response to pwfarwell)I too am looking at the use of 'cancelling' a workflow.
It appears its possible to cancel a task instance but there is no concept of cancelling a process instance or holding this state at the process instance that differentiates between normal and aborted termination of the process.
Any suggestions as to the best way to implement this functionality? -
3. Re: Best practices for cancelling a workflow
kukeltje Mar 27, 2007 10:45 AM (in response to pwfarwell)"CatlinIT" wrote:
It appears its possible to cancel a task instance but there is no concept of cancelling a process instance
May I ask where you got that impression from? I'm looking at the apidocs now and see a ProcessInstance.end() method"CatlinIT" wrote:
or holding this state at the process instance that differentiates between normal and aborted termination of the process.
Here you might be correct. I'm not sure it can be detected directly in which nodes the tokens were when they ended. OTOH, it might be possible to retrieve all tokens who have an end and ask in what node they were.. you do have to implement this yourself, but that is not to difficult