cancel
Showing results for 
Search instead for 
Did you mean: 

Move between two tasks

jatz
Champ in-the-making
Champ in-the-making
We have a Activiti process which goes through a few tasks and also updates status on our domain object.

We reach a point where the User wants to have a task which can oscillate between two statuses. Hence we are looking at a process with no end if we keep the workflow attached to our domain at this point.

For example if the object reaches Verified the user can change it to Not Verified or back again to Verified and so on.

The question is if we should stop the process when we reach either Verified or Not Verified for the first time and then just do an update on the object without Activiti. Or is there a better solution to handle this scenario?

Thanks in advance.
3 REPLIES 3

trademak
Star Contributor
Star Contributor
That's an implementation choice I think. What you could do is add a receive task or an additional user task to keep the process running and be able to update the domain object.

Best regards,

jatz
Champ in-the-making
Champ in-the-making
Thanks for the reply. It makes sense to have a receive task which will keep updating the object and not move to a certain other task. Is there an issue keeping the process flow open? The only issue I find is that the process may be really long running and any updates to future versions may end up in us closing/cancelling these older flows.

jbarrez
Star Contributor
Star Contributor
>  Is there an issue keeping the process flow open?

Doesn't matter. The state is kept in the db and won't take any system runtime resources. It can be in that state for years.

Regarding updates, yes that is an issue you need to take in account when modeling new versions of your process. Unfortunately there isnt a standard fixed solution for this.