We have been experimenting with sub tasks for a while (parent child relation is set up within a custom activity).
What is the planned/expected behavior of certain lifecycle events (e.g. complete parent task)?
Currently, the CompleteTaskCmd firstly calls task.complete (in this case, a history event for this task is fired too). Afterwards, the task is deleted using the DB session (according to the hibernate mapping, all sub tasks are deleted too; cascade="all-delete-orphan").
What is the recommend way to extend this behavior (e.g. fire history events for all sub tasks)? One solution might be to implement a custom command (requires to implement a custom TaskServiceImpl as well).