Map the Context Definition to Data Sources and Activate the Definition
After you create the context definition, map the definition’s nodes and attributes to
objects and their fields. The mapping feeds data into the definition and this data is used by the
expression set to evaluate the qualification of service process products.
Required Editions
Available in: Lightning Experience
Available in:
Enterprise and
Unlimited Editions with the required licenses
User Permissions Needed
To create context mappings:
Product Catalog Management Designer OR Financial Services Cloud Extension OR
FSC Service
In this example, we’re mapping the AccountUserContext context definition’s nodes and
attributes to the Account and User objects. These objects have fields that are similar to the
attributes in the context definition’s nodes.
From Setup, in the Quick Find box, enter Context Definitions, and
then select Context Definitions.
To open the AccountUserContext context definition that you want to map the data to, select
AccountUserContext from the definitions list.
SelectMap Data.
Click Add Mapping.
The mapping page opens on a new tab.
Provide the mapping details.
Enter AccountUserMapping as the name.
Enter a description.
Select Automatic Input Schema mapping and Automatic
sObject mapping
as
the mapping type.
Select Mark as Default.
Click Map.
Map the context definition’s nodes and attributes to the objects and their fields.
To map the nodes to objects, select a node and then select the object.
This mapping forms a connection between the node and the object.
To map attributes to object fields, select an attribute, and then select the field.
This mapping forms a connection between the attribute and the field.
Here’s the
mapping of Account and User nodes, and their attributes to the corresponding Account and
User objects and fields.
Note Do not manually map the Catalog, Category, and CategoryProduct nodes and their
attributes to objects and fields. The Context Service derives their mapping
automatically.
Save the mapping.
Return to the context definitions list.
Activate the AccountUserContext context definition.
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.
