Samrat Roy [https://community.jboss.org/people/whizkid.samrat] created the discussion "Re: JBPM 5.1 Final Release with jboss-5.1.0.GA - Human Task taskId" To view the discussion, visit: https://community.jboss.org/message/727894#727894 -------------------------------------------------------------- sure thing , The jbpm5 Api suggests that to complete a task allocated to a user (in order to move the flow forward) i need to have a taskId.     public void complete( long taskId, String userId, ContentData outputData,TaskOperationResponseHandler responseHandler ); We are making a tender approval flow with human approvals, so as soon as a task is assigned to an approver , we want to capture the generated task id and current assignee and persist those along with the model data in our own tables, so as soon as the current assignee (Approver) takes an action, i would immediately know the taskID and hit the API , thus I need not bother about taskLists and fetching tasksAllocated to a user. The second thought is , Task object is internal to jbpm & contains nothing specific to the object (Model) on which the workflow is running , so even if a get a list of tasks allocated to a user, would it not require a seperate logic to identify which taskId corresponds to which process flow  ? Hence the question. Maybe I am missing the point somewhere ,  a nudge in the right direction is appreciated :) -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727894#727894] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

William Timpany [https://community.jboss.org/people/wtimpany] created the discussion "Re: JBPM 5.1 Final Release with jboss-5.1.0.GA - Human Task taskId" To view the discussion, visit: https://community.jboss.org/message/732372#732372 -------------------------------------------------------------- I am not sure if this will be of use, but we do a similar thing.  We create a relation between a "Human Task" and our own Application Model.  Since the Task ID does not exist before the Task is persisted, we pass our own Model Object ID to the Task.  I did not want to extend the Task Object to hold our FK, so I decided to use the "Priority" field in the Task to store the reference (this may have to change in the future if we need to use priorities).     The reason for not extending the Task, was that I wanted to use the vanilla JBPM code. We have a Script Task before the Human Task to inject our Model FK ID into the context, then use this context variable in the Task. Script Task: not the real code but it gives the idea.   // -- getBeanId returns Integer   kcontext.setVariable("myExternalModelID", MyExternalModelBean.getBeanId() ); Human Task:   Priority property: #{myExternalModelID} Doing it this way alows us to then Join our Model Bean to the JBPM Task:  MyExternalModelBean.beanId == Task.priority -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/732372#732372] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]