Hi there.
I’m working in a process in which several actors work in parallel, so I use a parallel gateway. The issue here is that there is a deadline for the entire process, so I need to pass a default value from the unfinished human tasks to the gateway once the deadline is reached. I’ve approached the problem by using a boundary time that sets an expiration date for the task, and the task does expire, but the parallel gateway seems to keep waiting for the expired tasks to be performed. This is a piece of my diagram:
![bpm][bpm]
[bpm]: https://pbs.twimg.com/media/Cc-uYufW0AERI8z.jpg:large
Is this approach doable? I’ll appreciate any feedback.
1 Like
Got it!
The issue is solved by properly placing an exclusive gateway which makes sure only one flow gets the parallel gateway from the undone human task:
![bpm2][bpm2]
[bpm2]: https://pbs.twimg.com/media/CdCwBK_XEAMyQ20.jpg:large
Now the process throws its output and ends once reached the deadline, yielding default values for each undone human task. Anyway, if there is a simpler/better solution, please let me know.
Incidentally, the non-interrupting timer causes problems when used to make a loop. This is because a new task is created in each iteration, without terminating the originating one. This behaviour is avoided by using an ordinary boundary timer that kills the human task and creates a new one in each loop, or so it seems.
Incidentally, the non-interrupting timer causes problems when used to make a loop. This is because a new task is created in each iteration, without terminating the originating one. This behaviour is avoided by using an ordinary boundary timer that kills the human task and creates a new one in each loop, or so it seems.
Yes, that’s because you have a return to the Human Task. It will always create a new task.
What you need to do with the NIT (Email Reminder Task) is just have it point to an END. This way the email will be sent, the original task will remain and the process will continue…
regards
Seán
