Tokens for Document Clauses and Document Templates

Tokens Inside Clause Content

Placeholder and merge tokens are content tokens. Clause designers add them to document clause content so part of the clause can change without rewriting the entire clause.

Merge tokens mark values that Salesforce fills from mapped Salesforce data when you generate a document, for example, through your template's token-mapping method. See Context Service for Document Generation. Use merge tokens when the clause includes data from Salesforce fields. Merge tokens use curly brackets, for example, {{CustomerName}}.

With placeholder tokens, users provide a value at run time. Designers can set a default value during clause creation. At generation, Salesforce inserts the default when one exists. Users who have edit rights to the document can change placeholder values in supported experiences, such as quote special terms or Microsoft 365 contract authoring. Placeholder tokens use double angle brackets, for example, <<EffectiveDate>>.

Reference Clauses in Document Templates

If document templates contain clause tokens, Salesforce Document Generation can reference them from the clause library to fetch the latest version or a configured version. Salesforce supports two types of clause tokens.

• Clause Template Identifier: Copied into a document template in the format {{CL_<ClauseSetName>_<ClauseName>_<language>}}, this token resolves to a document clause's latest active version at document generation.
• Clause Template Version Identifier: Copied into a document template in the format {{CL_<ClauseSetName>_<ClauseName>_<language>_<ClauseVersion>}}, this token resolves to one specific version of a document clause.

Note For successful document generation, preserve the clause token format exactly as it's derived from the document clause. Altering the clause token causes resolution failure, resulting in blank clause content that requires manual correction.

How Tokens Flow from the Clause Library to the Generated Document

Tokens follow the clause lifecycle: Design the clauses in your clause library, assemble the template, generate the document, then complete any remaining placeholder values during authoring.

• Clause designers build library content and add content tokens, such as merge or placeholder tokens, where values can change.
• Template designers assemble Microsoft 365 templates by manually inserting clause content, clause tokens, or both.
• During document generation, Salesforce resolves merge tokens and clause tokens. If you set placeholder defaults, the system applies them, and users fill in any remaining placeholder values during supported authoring flows.
• Data true-up tokens are supported within clauses. See Data True-Up Tokens in Document Templates.