Document Management in Salesforce

Design and create document templates directly in Salesforce without needing the Omnistudio managed package. Use an Omniscript to automate the document generation process. This method simplifies the process of generating various types of documents and eliminates the need to install additional packages.

• Export and Import of Document Templates in Salesforce Orgs
  Using a managed package to standardize document templates across various Salesforce orgs, including production and sandbox environments. This package facilitates the transfer of document templates by letting users to export them from a source org, such as a sandbox, and subsequently to import them into a target organization, such as production.
• Design Document Templates in Salesforce
  Use Design Document Template to design and generate documents from templates in the Microsoft Word (.docx), Microsoft 365 Word (.docx), and Microsoft PowerPoint (.pptx) formats. Integrate tokens or variables in the template by replacing tokens with object values. You can create templates without a managed package. The Microsoft 365 Word option is only available when you have a ContractManagementAddOn license in your org.
• Context Service for Document Generation
  Starting Winter '26, Context Service is the default token mapping method in Salesforce Document Generation (DocGen). It provides a visual way to extract and organize business data from different sources without an Omnistudio license. It then connects that structure to Salesforce data using context mappings. With Context Service, you define the structure of the data you want to use in your documents, making it easier to generate accurate, personalized content across contracts, quotes, and other business documents. When a document is generated from a document template, Context Service replaces the tokens with real data from the mapped fields.
• Context Filters for Document Generation
  Document generation often pulls data from complex models that return more records than a document requires. To exclude irrelevant data, use filters to control which data the context service fetches before generating a document. When you add a filter to a template, document generation applies the filter every time a document is rendered.
• Transform Token Data with Context Service for Document Generation
  Reshape and enrich token data before document generation by using a transform plug-in to apply Apex logic. You can build hierarchies, group related records, or perform custom calculations that the context service alone can’t handle. You can use a transform plug-in in conjunction with a context filter. Document generation applies the template’s context filter before running the transform plug-in.
• Add a Text Watermark to a Document Template
  Enhance document security and status visibility by adding a custom watermark to a Microsoft Word template. By using a token inside a text box, you can dynamically display the appropriate label in the generated document. Standard Microsoft Word watermarks found under the Design tab are not supported.
• Generate a Table of Contents Dynamically
  Synchronize heading titles and page numbers automatically within generated DOCX and PDF files. Use a dynamic Table of Contents (ToC) to maintain the navigation structure in documents where pagination fluctuates based on data injection, conditional clauses, or variable text.
• Generate Documents by Using User Locale Settings
  Generate documents that reflect a user’s language and regional settings. Translate token data for objects and fields that support translation. Apply locale-specific currency, date, and time formats based on the current user’s settings. Control translation at the document generation request level and refine behavior at the context definition level.
• Transform Context Data for Document Generation
  A DocGen transformation is how you prepare data before a document is generated. You can reshape flat data into hierarchies, group related records, and derive the values a template should show such as, nesting products under a bundle or calculating totals. The Data Processing Engine (DPE) uses a context definition to run that logic and output structured JSON; document generation then reads that JSON to fill the template. Together, the transformation step closes the gap between source records and a predictable structure for the template.