Context Definitions for Dynamic Revenue Orchestrator
Dynamic Revenue Orchestrator (DRO) context definitions contain the information required
to fulfill a sales transaction. A context definition includes the relationship between nodes and
their structure, attributes, context tags, and mapping. Context mapping updates the nodes and
attributes with the correct input data from Salesforce objects.
Required Editions
Available in: Enterprise, Unlimited, and Developer Editions
of Agentforce Revenue Management where Salesforce Dynamic Revenue Orchestrator is enabled.
Predefined Context Definitions
DRO’s predefined context definitions include:
Sales Transaction Context Definition
Provides the details of a sales transaction such as order line items, relationships,
and attributes to the Decomposition process.
Fulfillment Asset Context Definition
Provides the quantities and attributes of the fulfillment assets to the decomposition
process to determine the actions on the fulfillment order line items.
Customize Context Definitions for DRO
These predefined context definitions provide a baseline of functionality for sales order
decomposition and fulfillment. To customize or extend these context definitions, consult
these Context Service learning resources:
When you map a source product tag to a target product tag and if that target product tag is
mapped to a reference field in the context definition mapping, enrichment happens only if
the outcome of the mapping is compatible with the reference field of the target product tag.
We recommend that you avoid selecting such product tags for the target product in the Fields
& Attribute Mapping tab.
In the event of an enrichment failure, the Decision
Explainer Service (DES) captures the information in the log. See the Explainability Action
Logs section on Submit Order Action and Action Logs.
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.