Basics of Process Route Shape
Basics of Process Route Shape
Use case: Suppose you have a route shape that
directs documents to different execution paths. For example, if the company
value is "Company A," the document follows the Company A execution
path. If the value is "Company B," it takes the Company B execution
path. Now, imagine that changes are required in the business logic for both
execution paths. The team handling the Company A execution has already
completed their changes. However, the team working on Company B's changes has
not finished their updates, creating a dependency for the entire application
deployment.
By utilizing a process route shape, you can decouple the
application. Replace the route shape with a process route shape, allowing you
to deploy the process route component separately from the sub-processes. This
approach enables you to decouple the application, providing flexibility in
managing dependencies
Process Route shape
By using the process route shape, you can route documents to
different execution paths based on a specified value
Process Route component
It is a deployable component that routes messages to
various sub-processes based on a certain value determined at runtime.
Important points
·
When the sub-processes are configured as data
pass-through, they will not have separate execution records on the process
reporting page. The process log of the parent process will contain details
regarding the execution of the sub-processes.
·
Please make sure that you do not set the default
path to a stop shape. Instead set the default path to an exception shape. If
not the documents going via default path will end up showing as success in the
process reporting page.
Comments
Post a Comment