Hello,
I am trying to find a way to jump from one user task/call activity to another programmatically without having to provide a provision for it in the BPMN files (using events etc). Is there a way to do so? if yes, i'd be much obliged if someone could point me in the right direction
I am trying to find a way to jump from one user task/call activity to another programmatically without having to provide a provision for it in the BPMN files (using events etc). Is there a way to do so? if yes, i'd be much obliged if someone could point me in the right direction
Ahh I see. I don't think jumping into the internal workings of activiti & making the database changes directly would be practical for us
So the reason we wanted to avoid making BPMN file changes for this, is because given all the combinations possible for the 'from' user task to all the 'to' user task, if we want to be able to jump from any task to any other task, using something like a SignalBoundaryEvent would clutter our BPMN files pretty soon, leading them to be less readable, maintainable & more error-prone.
In your opinion, is there a more graceful & less cluttering way to make such a change in the BPMN file?
So the reason we wanted to avoid making BPMN file changes for this, is because given all the combinations possible for the 'from' user task to all the 'to' user task, if we want to be able to jump from any task to any other task, using something like a SignalBoundaryEvent would clutter our BPMN files pretty soon, leading them to be less readable, maintainable & more error-prone.
In your opinion, is there a more graceful & less cluttering way to make such a change in the BPMN file?
Thanks martin we really appreciate that solution
While implementing it we realized it would be awesome if we could conditionally invoke the custom parse handler. Adding it as a preBpmnParseHandlers or postBpmnParseHandlers in the Activiti configuration causes it to be invoked not only when the BPMN file is first parsed by the system but also whenever the BpmnDeployer (org.activiti.engine.impl.bpmn.deployer.BpmnDeployer) deploys a file after server start-up. Granted this deployment may not be very common but we have some efficiency concerns around this.
Is there a way to conditionally invoke the parse handlers? Also, out of curiosity, how frequently/when is the BpmnDeployer invoked generally?
While implementing it we realized it would be awesome if we could conditionally invoke the custom parse handler. Adding it as a preBpmnParseHandlers or postBpmnParseHandlers in the Activiti configuration causes it to be invoked not only when the BPMN file is first parsed by the system but also whenever the BpmnDeployer (org.activiti.engine.impl.bpmn.deployer.BpmnDeployer) deploys a file after server start-up. Granted this deployment may not be very common but we have some efficiency concerns around this.
Is there a way to conditionally invoke the parse handlers? Also, out of curiosity, how frequently/when is the BpmnDeployer invoked generally?
