Create a Document Template by Using Context Service for Document Generation
Upload and configure a Microsoft 365, Microsoft Word or PowerPoint template. Then, use
Context Service to replace tokens with Salesforce data during document generation.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, Unlimited, and
Developer Editions
User Permissions Needed
To create a document template:
DocGen Designer
Note Data Transform provides feature parity between Context Service and OmniDataTransform, and
can be used alongside Context Service to apply transformations.
Prerequisites:
To use Context Service in a document template, make sure you’ve created a context
definition and context mapping and activated your context definition.
Make sure you have a Microsoft Word or PowerPoint file ready to associate with the Context
Service token mapping method when you create the document template. To include tokens, see
Tokens in Microsoft Word or Microsoft PowerPoint
Documents.
From the App Launcher, open Design Document Template.
Enter a Name for your template.
Choose the Template Type (Word or PowerPoint).
The default token mapping format is JSON, and Context Service is the default token mapping method.
Select the context definition and the associated context mapping.
Drag the .docx or .pptx file from your computer to the document template designer, or click
Browse to find the file.
Save your changes.
After you activate the document template, you can't delete the Microsoft Word or
PowerPoint file associated with it. You can deactivate the template and change the file
associated with the template.
此文章是否解決您的問題?
請讓我們知道,以便我們改進!
正在載入
Salesforce Help | Article
Cookie Consent Manager
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.