-
1. Re: Modeling a retry
kukeltje Oct 8, 2008 8:53 AM (in response to oravecz)There are so many ways to model this, none of which probably is wrong. 2 nodes is an option, one with timers, one with a real task (so it is visible in the process) Three nodes is even more visible, but that is up to you...
-
2. Re: Modeling a retry
oravecz Oct 8, 2008 9:41 AM (in response to oravecz)Great, thanks. I just wanted to make sure there wasn't a way to do it with a single node.
-
3. Re: Modeling a retry
kukeltje Oct 8, 2008 12:26 PM (in response to oravecz)We'll there might be, just not sure if it will work, therefor I did not suggest it.
You could try making a task node with a task that is not created when the node is entered. Then put the two timers on them but the second timer action should be slightly different. It should create the task instead of leaving the node. But... if a task-node has no tasks, the token automatically continues. This is not what you want, so you should set signalling to false... this is just from the top of my head so things might be missing, but if feels fabricated...