---
schema_version: "1"
id: 8984f288f7902cbabc1c5acf50b0d280d0225aa9973144a9841255126dd4be54
title: Create Custom Context Definition and Map Business Objects
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_create_custom_context_definition_and_map_business_objects.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_create_custom_context_definition_and_map_business_objects.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 30d4a660b76c39350ef8dda6f4ab4e67020e0b0bf57f1d6c61a37e6cd961c922
description: Extend a standard context definition where you want to inherit all the standard components such as nodes, attributes, and mappings. Then add components to the extended context definition based on your business requirements.
products:
- Revenue Cloud
release: "264"
---
# Create Custom Context Definition and Map Business Objects
Extend a standard context definition where you want to inherit all the standard components such as nodes, attributes, and mappings. Then add components to the extended context definition based on your business requirements.
### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions of Revenue Management
User Permissions Needed
To extend a standard definition and to map attributes to fields:
DRO Admin User
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.").
To make sure that your nodes and attributes are updated with the right input data, create a mapping structure for your context definition. After you create your context definition, search for objects, and click the node and attribute icons that you want to connect to the object fields to start mapping.
1. From Setup, in the Quick Find box, enter Context Definitions and select it.
2. For the SalesTransactionsContext record, click , and select **Extend**.
3. Enter a name for the context definition, and click **Next**.
4. Save your changes.
5. On the Custom Definition tab, open the new context definition.
6. For the OrderEntitiesMapping record, click , and select **Clone**.
7. Save the new mapping by entering a name and for the new mapping record, click , and then select **Edit sObject Mapping**.
8. To set this mapping as your default mapping, select **Mark as default**, and then click **Map**.
The page shows the mapping attributes on the left, and the entity fields on the right.
9. Delete these field mappings between the Sales Transaction node and the Order object by using the Delete icon: Order, OrderAction, OrderItem, OrderItemAttribute, OrderItemDetail, OrderItemGroup, OrderItemRecipient, OrderItemRelationship, and OrderItemTaxLineItem.
10. In the Connect Objects section on the right, click **Add**, find and select the business process object that you want to orchestrate, and save your changes.
11. To map the Sales Transaction node attributes with the new business process object fields, click a mapping attribute, and then click the field that you want to map the attribute to.
Important You must delete the default mapping where the OrderID attribute of the FulfillmentTransaction node is mapped to the OrderID field in the FulfillmentOrder object. Then, if the FulfillmentOrder object already has a field that references the business object, map the FulfillmentTransaction node's OrderID attribute to that field. Otherwise, create a custom field on the FulfillmentOrder object and map the OrderID attribute to that field.
For information on the expected context structure and mapping from sales transactions to objects like order and quote, see [Dynamic Revenue Orchestrator Context](https://help.salesforce.com/s/articleView?id=ind.dynamic_revenue_orchestrator_context.htm&release=264.0.0&type=5 "The Salesforce DRO solution comes with its own predefined context definitions that are used to map sales transactions to objects like order and quote.").
For information on mapping sales transactions to your business process object, see [Extend Sales Transaction Context Definition](https://help.salesforce.com/s/articleView?id=ind.qocal_extend_your_transactions_with_custom_field_support.htm&release=264.0.0&type=5 "Extend or customize default features to meet business-specific requirements by creating and mapping custom fields in Revenue Management.").
12. Save the mapping changes. On the mapping details page, click **Activate**.
13. From Setup, in the Quick Find box, enter Context Definition Settings and select it.
14. In the Sales Transaction Context Definition section, select the new context definition and configure the context nodes that are used to orchestrate the business process.
15. Save your changes.
#### See Also
- [Configure Procedure Plan Definition for Business Process Orchestration](https://help.salesforce.com/s/articleView?id=ind.dro_configure_procedure_plan_definition_for_business_process_orchestration.htm&release=264.0.0&type=5 "Use the procedure plan definition to determine the correct context definition and mapping, and orchestrate the business process to create a sales transaction fulfillment request.")