After some usage of Camunda/BPMN processes in our organization, we came to a point of reevaluation. We’ve been using user tasks to signal to users what they have done/need to do (automatically opening/closing these tasks), based on the data that they have entered somewhere (which data ends up in the Camunda context). I’ve already asked about indirectly managing user tasks in here, but here’s an overview of our current modelling style:
As we’re not directly using a worklist, we don’t benefit much from using user tasks. On the contrary, modelling is quite cumbersome. What I’m wondering if whether we could use/create a reusable block that would better fit our needs - a block that is always active (eg “Some task”), that gets reevaluated every time the context of the process is updated. This would allow us to store the current “task” state (whether it is completed or not) and if that changes during the reevaluation - emit that change to the users/clients. Ideally this reusable clock will accept as input the conditions under which the task is completed/not. It sounds like DMN might fit this use case, but I’m not certain how exactly.
We’re looking for suggestions for the general direction of a potential solution, and if that is at all possible.