8/30/2023 0 Comments End all tasks![]() ![]() ![]() I avoided to use taskInstance.end(), which continues the token's execution. ![]() Those tasks should be cancelled and made "invisible" for the other actors. I didn't use taskInstance.cancel() method for the unfinished tasks because it is calling end() method too, which marks those tasks as done, and that is not true, also. How to handle this? Thanks for any answer. If two or many actors of the nodes in parallel are in front of their validation forms, their task instances are not set with an end date, even though the tokens and the process instance are ended. This does work if only the actor which rejects the process is in front of a validation form. I did like this: - get all unfinished tasks for the process instance and call tEnd(new Date()) for every task - get the token associated to every task from that list and call token.end() - call processInstance.end() I avoided to use taskInstance.end() because the end of the task instance does not mean the end of its token. The goal is to not allow the other owners of the nodes in parallel to see (and no more validate) their actions. If one of the owners of these nodes in parallel wants to reject the process, I would like to stop the task instance, then to stop all other task instances which are not already finished and finally to end the process instance. Hello, How to finally stop a process instance in the middle of the workflow, if I have multiple nodes treated in parallel (inside fork-join nodes) and one actor decide to cancel the process? I have a process in jBPM 3.0 where from the start state I open a fork to 4 task nodes, treated in parallel. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |