Define Dependencies and Fulfillment Scenarios

Learning Objectives

After completing this unit, you’ll be able to:

• Define complex dependency linking steps across orchestration lanes.
  
• Create product fulfillment scenarios.
  

Connect Fulfillment Steps

Dependencies are the glue that holds your orchestration together. In Dynamic Revenue Orchestrator (DRO), you define both within-lane and cross-lane dependencies to make sure that each fulfillment stream executes in the correct order, with proper coordination between steps and teams.

So far in this module, Julian has set up technical products, step groups, and steps. Now, it’s time to link the steps within and across the orchestration lanes. Follow along in your Developer Edition org.

Dependencies Within Lanes

Define dependencies within lanes to establish the precise sequence in which individual steps are executed. For example, in the Invoicing lane, Julian defines dependencies so that the Generate Invoice step logically follows Items Delivered, and Email Invoice follows Generate Invoice.

Similarly, in the Inventory Management lane, Create Shipping Order depends on Pick and Pack.

Create these dependencies.

1. From the App Launcher, find and select Fulfillment Workspaces.
   
2. Go to the Laptop Pro Master Orchestration workspace.
   
3. In the Invoicing lane, on Items Delivered fulfillment step definition, click .
   
4. As Generate Invoice is dependent on Items Delivered, click + on Generate Invoice.
   
5. In the New Fulfillment Step Dependency Definition window, enter ItemDel_GenInv in the Name field.
   
6. Save your work.
   

As the step group is imported from your work in the Simple Order Orchestration with Revenue Cloud module, Generate Invoice is already linked to Email Invoice.

Now, in the Inventory Management lane, set the fulfillment step Create Shipping Order to depend on Pick and Pack. Name the fulfillment step dependency definition as PickPck_ShpOdr.

Here’s how the Invoicing and Inventory Management lanes with all steps connected now look like.

Now, it’s time to create dependencies across lanes.

Dependencies Between Lanes

Cross-lane dependencies help you ‌coordinate across functional areas. For example, Warranty Activation from the Activation Service lane completes before Generate Invoice in the Invoicing lane and Activate Subscription in the Subscription Management lane. This makes sure that invoicing and subscription steps begin only after the warranty setup is done.

Set up the dependencies within the Laptop Pro Master Orchestration workspace.

Inventory Management Lane

1. On the Create Shipping Order step definition, click.
   
2. As Items Delivered depends on Create Shipping Order, click + on Items Delivered in the Invoicing lane.
   
3. In the New Fulfillment Step Dependency Definition window, enter ShpOdr_ItemDel in the Name field.
   
4. Save your work.
   

Similarly, set the dependencies for other lanes.

Invoicing Lane

Set the fulfillment step Warranty Activation to depend on Items Delivered. Name the fulfillment step dependency definition as ItemDel_WarAct.

Activation Service Lane

Set the fulfillment step Generate Invoice to depend on Warranty Activation. Name the fulfillment step dependency definition as WarAct_GenInv.

Subscription Management Lane

Set the fulfillment step Activate Subscription to depend on Warranty Activation. Name the fulfillment step dependency definition as WarAct_ActSub.

Check if your fulfillment workspace looks like this. If you can’t see all of these steps at once, zoom out of the workspace.

With the dependencies in place, Julian is now ready to link the plan to the Laptop Pro Bundle product to trigger the orchestration.

Create a Product Fulfillment Scenario

Product Fulfillment Scenarios direct DRO to qualify a group of fulfillment step definitions when a specific product appears on an order. You can group these steps in a swimlane on the workspace and tie them to either commercial or technical products.

Now link the decomposed technical products to their respective step groups.

1. In the Laptop Pro Master Orchestration workspace, click anywhere in the Invoicing fulfillment step group.
   
2. In the side panel that opens, go to the Related tab and in the Scenarios section, click New.
   
3. In the Create Product Fulfillment Scenario window, add these details.
   
   • Name: Scenario Laptop Pro Invoicing
   • Action: Add
     
   • Product: Laptop Pro Bundle
     
4. Save your work.
   

Back on the Laptop Pro Master Orchestration workspace, the new scenario now appears in the Scenarios section.

Repeat ‌steps 1-4 to add these scenarios to other lanes, and see the explanation for each product fulfillment scenario.

Now, when a user orders the Laptop Pro Bundle, the Laptop Pro Master Orchestration plan is ready to trigger automatically.

Next Steps

In this unit, you built a complete complex product orchestration plan, and linked cross-lane dependencies. In the next unit, you create and submit an order to see the decomposition and orchestration in action.

To pass the challenge and move on to the next unit, click Check Challenge to Earn Points.

Resources

• Salesforce Help: Design Your Order Decomposition
• Salesforce Help: Design Your Order Orchestration
• Trailhead: Efficient Sales with Revenue Cloud (see unit: Discover and Configure Products)