You are here:
Map Custom Context Definition with Sales Transaction
To start using a context definition, you must associate the context definition's newly created attribute with the context field in the sales transaction node.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
To start using a context definition, you must associate the context definition's newly created attribute with the context field in the sales transaction node.
| Available in: Enterprise, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To associate an attribute with a context field: | DRO Admin User |
Prerequisite: Create Custom Context Definition and Map Attribute to Field.
After the setup is complete, you can create and process orders by using the new context definition. The orders must contain the grouping key in the field that you mapped to the Orchestration Group Key. For more information on Orchestration Group Keys, see Cross-Plan Dependencies.

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.