You are here:
Define a reusable data structure for document templates by creating context definitions. These definitions organize Salesforce business data into nodes and attributes, capture relationships such as primary and related objects, and map the information into a structured JSON format. The mapped data provides token values used in document generation.
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, Unlimited, and Developer Editions |
For example, to generate a contract document with line items, the context definition must include Contract as the primary node and ContractLine as a child node. Map these nodes to the corresponding Contract and SalesContractLine entities their attributes mapped accordingly. You can also map attributes from related entities, for instance, map the attribute Contract.AccountName to the field Contract.Account.Name, where Account is a reference field on the Contract object. Attributes such as Contract.StartDate, Account.Name, and Contact.Email are defined in the structure and later referenced as tokens in the template.
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.