Requirements for Creating Orchestration Plan Context Mapping
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.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions
User Permissions Needed
To create the custom context definition:
DRO Admin User
Keep these considerations in mind when creating a mapping.
Create one mapping entry for a specific object for DRO to orchestrate.
Map an orchestration type to only one context definition to maintain an exclusive
relationship between the orchestration process and its logic.
Use the same orchestration type while creating the mapping as the usage type of the
orchestration components.
Create the Orchestration Plan Context Mapping entry using these fields:
FIELD NAME
REQUIREMENT
DESCRIPTION
Object Name
Mandatory
The API name of the object for orchestration.
Context Definition
Mandatory
The context definition to be used for the object.
Context Mapping
Mandatory
The name of the context mapping to apply.
Root Node Name
Mandatory
The node name that represents the root in the context definition.
Item Node Name
Optional
The node name that represents an item in the context definition.
Orchestration Type
Mandatory
Select Generic orchestration type.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.