---
schema_version: "1"
id: 272f779393b5c449612ddcd953c5bb8f46de6b686e16014e1d73d1dd76686897
title: Define Execution Rules for a Decomposition Rule
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_define_conditions_for_a_decomposition_rule.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_define_conditions_for_a_decomposition_rule.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 143783c68ae570d454911464b5679369c60385db4663ab1303d87a72a747cf34
description: To apply logic that determines when a specific decomposition rule runs, define execution rules that specify the conditions for the rule. By default, products decompose into fulfillment line items independent of execution rules.
products:
  - Revenue Cloud
release: "264"
---
# Define Execution Rules for a Decomposition Rule

To apply logic that determines when a specific decomposition rule runs, define execution rules that specify the conditions for the rule. By default, products decompose into fulfillment line items independent of execution rules.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d187987e67">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d187987e67 ">To define conditions for when a decomposition rule runs: </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d187987e67 ">
              <p>Fulfillment Designer</p>
              <p>OR</p>
              <p style="margin-bottom:0;">DRO Admin User</p>
            </td>

          </tr>
        </tbody>
      </table>

To prevent order orchestration failures during decomposition or plan composition, complete these configuration prerequisites:

- For every context definition attribute you create, define a corresponding tag and map it to an sObject field.
- Confirm that all tags are present so that resources appear correctly in the Condition Builder.
- Confirm that all attributes are mapped to prevent incorrect condition evaluations during rule execution.
- To apply changes to the context definitions, clone the DRO RuleLibrary version, associate the new context definition, and activate it.

To control when a decomposition rule executes, create an execution rule. Execution rules contain the conditions that must be met before the decomposition rule is executed.

1. From the App Launcher, find and select **Dynamic Revenue Orchestrator**.
2. From the app navigation menu, select **Products**.
3. Click a product.
4. Click the **Decomposition** tab. On the Decomposition Workspace, select a decomposition rule by clicking the connector icon on the line that connects the source and target products. A side panel opens with the **Details**, **Execution Rules**, and **Attribute Mapping** tabs.
5. In the side panel, click the **Execution Rules** tab.
6. Click **Configure Execution** Rules.
7. In the **Condition Builder** modal, configure the conditions.
8. In the **Based On** field, select Sales Transaction Items.
9. Select a Condition Requirement to determine how multiple conditions within the rule are evaluated:
    
    - - For every condition to be met, select **All Conditions Are Met (AND)**.
        - For at least one condition to be met, select **Any Condition Is Met (OR)**.
        - To create complex logic, select **Custom Logic Is Met**.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)
        
        Note If a decomposition rule condition (ruleset) contains multiple dynamic rules, they are evaluated separately. The condition evaluates to true if at least one individual dynamic rule is true, applying **OR** logic between the rule results.
10. In the **Resource** field, select a tag or attribute.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)
    
    Note The items available in the resource list are determined by your tags and attributes configuration:
    
    - Tags: Sourced from the Sales Transaction Item (STI) context nodes within the active context definition mapped in Setup. If an STI context node does not have a defined tag, it does not appear in the resource list. If a tag is defined but is not mapped to an object field, the condition evaluates to false at runtime.
    - Attributes: Populated from the source product or product classification attributes.
11. From the **Operator** dropdown, select a value, such as Equals.
12. Enter or select a Value.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)
    
    Note For picklist resource tags, enter the text value manually.
13. Save your changes.

Let's explore an example of a execution rule in action:

Imagine you sell a Cloud Security Suite with a service tier attribute that can be either Standard or Enterprise. You want the suite to decompose into different fulfillment patterns based on this style.

Single Execution Rule: To ensure only enterprise-tier suites follow a specific decomposition rule, go to the execution rule builder. In the Based On field, select Order Line Items. Set the condition to Service Tier Equals Enterprise. The rule executes only when an order line item contains an enterprise-tier suite.

Multiple Execution Rules: If you want the same decomposition rule to apply to both Standard and Enterprise tiers, you can create two separate execution rules—one for each tier. Because multiple rules are evaluated using OR logic at the ruleset level, the decomposition rule executes if either tier is detected in the order line item.

![Execution rule criteria showing the Standard laptop bag style selected as the condition.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_execution_rule_attribute.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)

Note Enter the text value manually for resource tags of picklist type.