Doing reassigment the right way …
Very soon after my last post I decided to look closer to TMP svg chart, Task Management Process BPEL and TMS api, then I realized that TMS reassign is invoked by TMP BPEL process in many scenarios: Escalating, Claiming and Revoking a task. My main misunderstanding came from the fact that escalte.ftl (freemarker template used in tempo tests) lacked the <b4p:role>${role}</b4p:role>. When I used directly TMS reassign I can set directly the task state, but there were undesired side effects like the user can’t CLAIM a READY task.
Whenever the reassigment is done through the Escalate TMP operation task’s state always is set to READY due to the fact that the BPEL copy ever do it with a READY constant, I think that this is following standard documents on Human Workflow.
I just added the <role> parameter to the escalate.ftl template and modified the escalate method of the TaskActionHelper class.Now the delegate method of my TaskActionHelper class invokes the escalate one.
If you want to change the assigment of a READY state for a task on escalation you will need to modify the TMP BPEL end point invocation to include the state in the escalateRequest, then provide a business logic to guide Task States assigments before invoking Escalation.
For those who want to escalate (in the extjs ui future: delegate) a READY task you can change the line 145 of the file openinfomanager/modules/taskboard/taskboard.TaskController.js like this:
actionArr=['execute','claim','delegate'];
in order to make available to users Delegation of New Tasks.
ESCALATE through TMP is the right way for a reassignment. Remember that TMP is the process in charge of Task life cycle.
Best Regards.
