- Sat Apr 27, 2019 12:53 pm
#824155
Hello there,
We have two processes, A and B. The scenario is that when Process A crosses the Routing Screen (continue button screen), then a trigger in the Before Routing section of Process A would derivate process B (which is totally different from process A). This derivation is done using routeCase() of WSDL Web Services.
The expectation we had was that the triggers of process B in its own Assignment, Before Routing and After Routing Sections would get executed when process B is derivated in this manner from process A.
The observation is that this does not happen. The triggers do not get executed.
Is this an expected behavior? If so, is there a workaround? The current workaround we have is that we replicate relevant parts of the trigger code of process B in process A and ensure that process B data is updated from process A, and then the derivation execution is done from process A.
Best wishes,
SGK
We have two processes, A and B. The scenario is that when Process A crosses the Routing Screen (continue button screen), then a trigger in the Before Routing section of Process A would derivate process B (which is totally different from process A). This derivation is done using routeCase() of WSDL Web Services.
The expectation we had was that the triggers of process B in its own Assignment, Before Routing and After Routing Sections would get executed when process B is derivated in this manner from process A.
The observation is that this does not happen. The triggers do not get executed.
Is this an expected behavior? If so, is there a workaround? The current workaround we have is that we replicate relevant parts of the trigger code of process B in process A and ensure that process B data is updated from process A, and then the derivation execution is done from process A.
Best wishes,
SGK