How can activiti 6 be rejected?The scene is as followsA, B, C, DI hope to be able to refute C in the D link. The logs approved before C are still in, but C can be approved again.
Environmental Science: activiti 6.0 + java1.8
Could you post your BPMN diagram and/or XML and any code snippets you might have? I'm afraid it is hard to understand your description.
I think his English is as pool as me~
I think he want to implement the feature like below
SatrtEvent------UserTask A------UserTask B---------UserTask C--------UserTask D------EndEvent
If the assignee of D agree, the process go to end event. If reject, the process back to C.
But there isn't sequenceFlow from D to C.
In order to solve this problem, we should add a gateway between D and EndEvent when designing the BPMN diagram.
But if B and C will reject too, there are too many gateways and sequenceFlows.
Before 6.x , I solved this problem by pvm. Now I solved this problem by BpmnModel.
I wish I have described what I thought clearly. haha~
Are you still there? Can you put your code out
Hi Yuan,i meet the same problem u now!And i used BpmnModel too,then it can solve this problem on the scene of single wire,but if there are any branch,it does not work. It will produce the same task on multiple wires.So can u help me ?How did u solve this problem for multiple wire,can u paste your code out?
When my task node D refuses, it should be returned to the C processing.Excuse me, is there a API in activiti?This scene is too common.
Retrieving data ...