Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Understand Execution Conditions for Order Fulfillment

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Revenue Management

            Understand Execution Conditions for Order Fulfillment

            When you configure fulfillment plans, Dynamic Revenue Orchestrator directs you to create conditions that control when those fulfillment steps are executed.

            Required Editions

            Available in: Enterprise, Unlimited, and Developer Editions

            For example, set a condition so that a representative follows up by phone only if the customer lives in the same country. Or a condition that says that after a pause, fulfillment doesn’t continue until a credit check comes through.

            When an entity in DRO requires, or allows, conditions to be set, it launches the Condition Builder pane.

            The Condition Builder pane

            To configure logic for your fulfillment processes, use the Condition Builder. To set up these rules, seeDefine Execution Rules for a Decomposition Rule

            Example
            Example This image shows three conditions.
            • Condition #1: There's a fulfillment order line item tag called FulfillmentItemAction that equals Add.
            • Condition #2: There's a tag called OriginalQuantity that's greater than 100.
            • Condition #3: There's a tag called FulfillmentOrderID that doesn't equal 1221.

            The Custom Condition Logic says (1 OR 2) AND 3. That means that condition #3 must be met, and that either condition #1 or #2, or both, must be met.

            The Conditions pane with conditions filled in as described in the text

            Let's look at some possible examples after an order is submitted.

            Order #1:

            • FulfillmentItemAction equals Add. Condition one is met.
            • OriginalQuantity equals 150. Condition two is met.
            • FulfillmentOrderID is 1221. Condition three isn't met. The condition requires that FulfillmentOrderID type is something other than 1221.

            Because condition #3 isn't met, the set of conditions isn't met, and the entity associated with this rule doesn't run.

            Order #2:
            • FulfillmentItemAction tag equals Add. Condition one is met.
            • OriginalQuantity equals 90. Condition two isn't met. The condition requires the value to be greater than 100.
            • FulfillmentOrderID is 1000. Condition three is met. The condition requires the value type to be anything except 1221, and it is.

            This set of conditions is met according to the custom logic and the entity associated with this rule runs.

             
            Loading
            Salesforce Help | Article