pooled workflows

[giorgio]

Hello, can someone explain the comportamiendo workflows type of pool? namely the step of taking possession of the workflow, I mean, this is what I understand but apparently not:

Creates a workflow type pooled into a group of users previously created, this is achieved, the task appears in the pooled tasks for each user belonging to this group, and manage to enter the task they are given the option taking up the task, then at that moment what I understand, if not corrected me so, the task disappears from the pooled TAKS for all users in the group, and now appear in the task to do, do who took, what I interpret as that goes, is hiding or is eliminated or becomes the task, and now become an established and Trea Review and Aprova type, but it seems that this is not entirely true, as if it were really so, to approve or reject this new task, ejcutarian my custom code we have defined in such workflows, not executed. I do not know if it has become clear, I hope someone can help me, thanks in advance

Greetings.

[giorgio]

Good, I autorrespondo myself, and post this in the forum for all those who serve, because although it was in front of the nose has cost enough to find this, thank you very much to all who have been helping me what they have been, giving me ideas to capture this property.

In the end it was so easy to use this syntax. In this way we get the owner of the workflow, since process_definition, in the case of the workflows of this type have pooled empty until we take possession of the task, what happens is still not how to capture this event in order to assign the property just in time to take possession, as now I can only assign when you finish the task, as I do in the process definition does not tell if someone knows how to capture the event of taking possession to do so at this time .

bpm_package.children . properties [ "my: tecnico"] = bpm_package.properties [ 'cm: owner'];

a greeting.