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
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions of
Agentforce Revenue Management
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
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.
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.