---
schema_version: "1"
id: f7c5f372b2430dcf724d2f2bcfc44e88127ce8062f3b376b4996276bdd9bd666
title: Considerations for Creating a Non-Sales Transaction Context Definition
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_context.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_business_processes_context.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b18de66be6c5c06a67a3488c4f27ce73764d30210fc085d35bec1e22cbc274fc
description: 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.
products:
  - Revenue Cloud
release: "264"
---
# Considerations for Creating a Non-Sales Transaction Context Definition

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.

### 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="d85860e69">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d85860e69 ">To create or extend the context definition:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d85860e69 ">DRO Admin User</td>

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

Prerequisite: [Enable Permission for Context Service Users](https://help.salesforce.com/s/articleView?id=ind.dro_enable_permission_for_users.htm&release=264.0.0&type=5 "Create and manage context definitions easily and efficiently by assigning permission set licenses to your users. Add permissions to specific user personas to complete the work assigned to their role. System admin users have default access to Context Service without requiring any specific permission set licenses.").

See [Context service](https://help.salesforce.com/s/articleView?id=ind.context_service.htm&language=en_US).

- Define one root node for your object. To orchestrate a collection like a Collection Plan object with multiple items, add child item nodes.
- Define an Id attribute for root and child nodes (if applicable). The Id is used to identify the record to orchestrate. Map the Id attribute to the object's Id field.
- Define the StartDate attribute used to schedule the fulfillment steps.
- To show an identifiable label for the context definition, define a Name attribute . Otherwise, the record Id is shown.
- Generate tags for all the attributes.
- Add appropriate mappings with the root and child nodes mapped to their respective object fields based on your use case, and activate the context definition.

![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 every attribute tag in a rule condition, define a corresponding object field mapping to prevent execution failures during rule evaluation or fulfillment.
- To maintain data consistency across the orchestration lifecycle and to provision multiple mappings, map all the root nodes and applicable child nodes to their respective objects.