Save the progress of a row of service tasks

[fellowtom]

Hi,

I have a theoretical question. My desired process consists of a lots of service tasks which do different things. If I have like 10 service tasks in a row and kill the process at the last one (errors could happen everytime), nothing was saved (ofc, since service tasks are no waitstates). So everything is done again on instance-restart. But they do work which schould not be done twice (create documents/folders, cooperate with other dbs/programs). When the process gets bigger its also no good option to place a waitstate behind every single service task. This would make the process confusing. I had a look at moneytasks example and the "extend activiti designer" part in user guide, but I'm not sure if this is what I need.
I would just like to have a service task that is handled like a waitstate on entry. What is a good solution to solve this problem? I'm glad for every hint.

Greetings

[trademak]

This is exactly the reason why we introduced asynchronous behavior for service tasks and other activities. You can read about it in the user guide. The async attribute should be set to true.

[fellowtom]

Hi,

wow, this was heavy wrong interpretation of asnychronous behaviour of myself.

The async attribute should be set to true.

Done and works perfect now (ofc…). Very useful, thank you very much.