How can you configure parallel vs sequential routes in a CLM workflow?

How can you configure parallel vs sequential routes in a CLM workflow?

• A. By using parallel branches within a Stage (for concurrent approvals) or sequential Transitions (for ordered steps); ensure tasks are assigned to appropriate Roles
• B. Parallel routes are not supported
• C. Always use sequential only
• D. Use random paths

Answer: (A)

Configuring routing in a CLM workflow hinges on how you group and sequence the tasks. You create parallel branches inside a Stage to run approvals at the same time, which is useful when multiple parties can review independently. For ordered steps, you model the flow with sequential Transitions so one step completes before the next begins. Assigning each task to the appropriate Roles ensures the right people receive the tasks in each path. This approach covers both parallel and sequential needs and is supported by the platform. Parallel routes are indeed supported, so you don’t have to stick to only sequential steps, and there’s no concept of random paths in this context.

Configuring routing in a CLM workflow hinges on how you group and sequence the tasks. You create parallel branches inside a Stage to run approvals at the same time, which is useful when multiple parties can review independently. For ordered steps, you model the flow with sequential Transitions so one step completes before the next begins. Assigning each task to the appropriate Roles ensures the right people receive the tasks in each path. This approach covers both parallel and sequential needs and is supported by the platform. Parallel routes are indeed supported, so you don’t have to stick to only sequential steps, and there’s no concept of random paths in this context.