In case some of your processes are integrated with a frontend implementation, what would be preferred? Lets say a use case where a user “starts” a process by filling out some details, after which this is further handled in the backend by Camunda/backend services.
Would it be preferable to have multiple user tasks, or just one user task? What would be pros and cons? For now I do not see added value in multiple user tasks, and I do see a challenge if the user wants to go back to a previous step on the frontend (because you need to be able to go back in your process as well).
Absolutely, having it as a single task is much better, but it depends on whether it is considered a single task or not.
In the provided example, all shown actions are typically considered a single task within the overall process and are assigned to a specific individual.
However, what if adding attachments needs to be done by a different assignee or department? What if adding attachments requires human verification of the added details before it can be activated?
Thanks for your reply. For now, in our use case, all tasks are for one individual going through a frontend “wizard/step by step flow”. So you argue that if that is the case, this is best modelled in one user task in the process?
