@fml2 ,
I am not really talking about the task description inside the process definition.
it seems that there are both task object (child of a given execution) and activity instance for a task
Yes , I read this , thank you
Are the activity instances stored in the DB (in the same way as tasks and executions)? I do not see them in the Database schema from your previous link?
the activity instance itself is not an entity, as it can be different things (task, subprocess, …). But, when you look at the execution table for example, you can see that the activity instance id is referenced here.
Reason for this is that the activity instance represents the current state of the process instance and can be calculated at any time.
So the activity instance is something temporary, which is calculated on the fly? Something like a linking object?
What confused me - is that it has its own identifier - [task id from the definition xml] + [UUID]
and this is not the UUID of the Task or the UUID of the execution.
So I thought that it may correspond to a real “persistent” object in the DB.
But anyway, I do not really need to delve that deep in the internal implementation, it was more curiosity.