I have a sub-process that when it meets a certain set of conditions I want it to stop that single document dead in its tracks and not continue with the rest of the branches of the main process, WITHOUT throwing an exception.
I ended up being able to come at my issue from a different angle. I'm just letting it continue to the next branch of the main process and checking if it cached anything before running my next steps, instead of depending on boomi to stop it for me. Should've done this in the first place. But that boomi behavior sure is peculiar.
Thanks for your help.
If you open the Stop shape's configuration dialogue, you can achieve this by unselecting "Continue processing other execution paths?"
Using the stop shape in a subprocess doesn't halt the main process it is included in. See image.
Can you send that document to a Return Documents shape, and then to a Stop shape in the main process?
I tried that and for some reason it seems to stop everything that runs through if even one document hits the end and return.
Is this correct?
I want the entire process to stop just for that one document, yes.
Is the start shape of the sub process data passthrough or no data?
Data passthrough. The new weird development is I pulled out the entire sub-process and pulled it into the main one, just to see if the fact it is a sub process was the issue...
It is still happening.
In this screenshot the selected document hits end and continue, so it should go to main branch #2, but doesn't because one of the other documents hits end and continue.
It is not executing the next branch, even after a document hits the end and continue because of the flow control. So once the end and continue is reached by one document, the next document waiting at the flow control shape will continue down the path.
I took out the flow control and it is still behaving the same.
EDIT: Thanks for all your help, by the way.
With the Exception shape configured to 'Stop Single Document', you would need a Try/Catch BEFORE the Branch shape. This will catch the exception for the single document and not fail the entire process. And to be clear, the document stopped will be tied to the document result from the Start shape...
Stop Single Document
So in the latest screenshot, it looks like the entire process execution stopped at the "End and continue," which wouldn't seem right. Are you sure that actually happened? Sometime in Test Mode some of the shapes wont turn green because logging was truncated due to size.
Nope, not truncated, ran just two documents (one that hits continue and one that hits end). If I run a set of 5 documents I know will hit the continue shape, all the correct shapes go green and the documents are processed.
So the TEST was complete when you took the screenshot above?
I'm not sure if I'm missing a small detail or not. It is peculiar if the entire process execution completely stopped at that End and Continue shape. You might want to just get on a chat with Boomi support to come to a conclusion quickly.
Julie, I think the behavior from your process is explained here
How to use the Exception Shape
The exception shape will result in the process being marked as a failure
If you select "stop only a single document", the rest of the documents will complete the current "path" within the process, but other branches will not be processed. It is as if the branch were treated as a process, i.e. all documents will finish the branch, but ultimately, the branch will fail, and the rest of the branches will not execute.
To handle each document to follow its path based on its contents and logic, try catch is probably the solution.
Retrieving data ...