---
schema_version: "1"
id: e7e89155a43ac0c92f7a523fe1e7247e4d47369e60cf163fb8336db978865332
title: Orchestrate Non-Sales Transaction Business Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_orchestrate_non_sales_transaction_business_processes.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_business_processes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 77b64acf05757cd30f71ee5fd835b3ef23622ba77557611c8de9d1f09a20aeec
description: Dynamic Revenue Orchestrator (DRO) orchestrates objects even if they aren't based on sales transactions. For example, you can orchestrate the dunning processes by using DRO to trigger personalized workflows based on customer segments. DRO can orchestrate obligations to track and fulfill post-sale milestones like delivery or service level agreements.
products:
  - Revenue Cloud
release: "264"
---
# Orchestrate Non-Sales Transaction Business Processes

Dynamic Revenue Orchestrator (DRO) orchestrates objects even if they aren't based on sales transactions. For example, you can orchestrate the dunning processes by using DRO to trigger personalized workflows based on customer segments. DRO can orchestrate obligations to track and fulfill post-sale milestones like delivery or service level agreements.

### 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: 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 of <span>Revenue Management</span></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="d67841e73">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d67841e73 ">To orchestrate a non-sales transaction business processes:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d67841e73 ">
              <p>Submit Transaction and Orchestrate User</p>
              <p>and </p>
              <p>Submit Transactions
                User</p>
              <p>and </p>
              <p style="margin-bottom:0;">Permission sets specific to the object to orchestrate</p>
            </td>

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

Let's design a workflow to orchestrate for a non-sales transaction-based business process.

![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 usage type of the orchestration components you use in the fulfillment plan should be the same as the orchestration type selected in the Orchestration Plan Context Mapping entry.
- Add the Usage Type field to the fulfillment scenario, fulfillment step definition groups, fulfillment step definitions, and fulfillment dependencies record pages if it isn't already present.

1. DRO accepts any context definition and isn't restricted to the sales transaction context definition. You can create a context definition or use an existing context definition. Map the attributes in the context definition to fields of the object you want to orchestrate. See [Custom Context Definition to Orchestrate a Non-Sales Transaction Business Processes](https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_business_processes_context.htm&release=264.0.0&type=5 "To orchestrate a non-sales transaction business process, create a context definition and map it to the fields of the object to orchestrate. You can also extend an existing context definition by adding a mapping to the object that you want to orchestrate. Keep these considerations in mind when creating a custom context definition and its mapping.").
2. Create an Orchestration Plan Context Mapping entry to associate the context definition to the orchestration logic within DRO. See [Create Orchestration Plan Context Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_mapping.htm&release=264.0.0&type=5 "Create an orchestration plan context mapping entry to connect the business data in an object to the orchestration logic within Dynamic Revenue Orchestrator (DRO) by using the orchestration type. DRO includes the Generic orchestration type to orchestrate non-sales transaction objects."). Use the `Generic` Orchestration Type that is provided out-of-the-box from DRO to orchestrate non-sales transaction objects.
3. Create a fulfillment workspace and generate an orchestration plan with fulfillment step definitions groups, fulfillment steps, and fulfillment dependencies. Select the Plan or Item dependency scope when creating fulfillment dependencies. Other scopes are not valid for this orchestration.
4. Create a fulfillment scenario to link the object with the correct orchestration plan. To determine selection of the appropriate scenario during fulfillment, define conditions. See [Define Orchestration Plan Components](https://help.salesforce.com/s/articleView?id=ind.dro_define_orchestration_components.htm&release=264.0.0&type=5 "Create and organize fulfillment steps, their dependencies, and fulfillment processes in fulfillment workspaces.").
5. To show the orchestration plan's submission status and fulfillment progress on the object page, configure the orchestration plan summary component.
6. To initiate orchestration, submit the order to DRO by using the Orchestrate Transaction invocable action. See [Dynamic Revenue Orchestrator Standard Invocable Actions](https://developer.salesforce.com/docs/atlas.en-us.revenue_lifecycle_management_dev_guide.meta/revenue_lifecycle_management_dev_guide/dynamic_revenue_orchestrator_invocable_actions_parent.htm) .

- **[Considerations for Creating a Non-Sales Transaction Context Definition](https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_business_processes_context.htm&release=264.0.0&type=5)**  
    To orchestrate a non-sales transaction business process, create a context definition and map it to the fields of the object to orchestrate. You can also extend an existing context definition by adding a mapping to the object that you want to orchestrate. Keep these considerations in mind when creating a custom context definition and its mapping.
- **[Requirements for Creating Orchestration Plan Context Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_mapping.htm&release=264.0.0&type=5)**  
    Create an orchestration plan context mapping entry to connect the business data in an object to the orchestration logic within Dynamic Revenue Orchestrator (DRO) by using the orchestration type. DRO includes the Generic orchestration type to orchestrate non-sales transaction objects.