The short answer is: yes, you only get end-to-end visibility if you model the overall process. Currently there is no way to link serial standalone processes into a single view that can track the status of all of them.
Instead, if you want end-to-end visibility, you would have to model this using referenced processes. You can model “order processing”, “invoicing” and “shipping” each as standalone processes that can be run independently. Then, you could define a single parent process, and drag-and-drop the “child” processes into the overall parent . At runtime, in MWS you can then see the status of the overall set of processes, and drill into them to see the status of the children as well.
Note that in our planned webMethods 8 release, we will also provide a facility to make the referenced processes dynamic – i.e. you may not know which child process to execute until runtime (based on some data or condition). This may get closer to the functionality you desire, if you don’t want to model all the process sequence up front.
Cheers,
Michael
#webMethods#BPM#webMethods-BPMS