Document Options Quick Reference
Scan Document Options settings in table format, including file naming, storage, edit behavior, and general generation options.
Use this version when you want the same quick reference in table format.
Attachment and File Name Format
Attachment and File Name Format
Define the naming pattern for generated documents.
Text string with optional merge fields. Use single braces: {!Object.Field}.
SD-####.pdf
Standard fields, custom fields, lookup fields up to 5 levels, and user fields like {!User.FirstName}
Use it when generated files need to be searchable and easy to identify outside Salesforce.
Keep names under 80 characters when possible. The maximum length is 255 characters. Include the .pdf extension. Null merge fields resolve to blanks. Very long names may be truncated by the file system.
Examples:
Proposal for {!Opportunity.Account.Name}
Legal Contract - {!DocumentID}
{!DocumentName} for {!Opportunity.Account.Name}Restricted Characters:
/ \ : * ? " < > |Supported Merge Fields:
Standard fields from base object
Custom fields
Lookup fields (up to 5 levels)
User fields:
{!User.FirstName}
Attachment & File Options
Create Salesforce Attachment and link to record
Automatically create an attachment in Notes & Attachments.
Creates an attachment on each generation. Uses the output file name. Links it to the base record.
Use it only when another process still depends on legacy attachments (uncommon).
Counts toward Attachment storage. Not recommended for most new implementations.
Create Salesforce File and link to record
Automatically create a file in Salesforce Files.
Creates a file on each generation. Uses the output file name. Links it to the base record. Supports sharing and collaboration.
Use it for most Lightning-first and modern Salesforce implementations.
Counts toward Files storage. Review file sharing rules if access matters.
Create Salesforce Attachment only when emailed
Create an attachment only if the document is emailed.
Skips attachment creation for download-only or preview-only actions. Creates the attachment only during email send flows.
Use it to reduce storage when many generated documents are never emailed.
Applies only to Attachments. It does not control Files.
Delete related Salesforce Attachment/File upon S-Doc deletion
Control whether generated files are deleted with the S-Doc record.
Deleting the S-Doc record also deletes related files or attachments. If disabled, the related files remain.
Keep it enabled for cleaner storage and fewer orphaned records.
Disable it only when retention rules require files to remain after the S-Doc is removed.
Allow Edit
Enable Live Edit for generated documents.
Adds an Edit option on generated documents. Users can open the file in a browser-based editor and save changes.
Use it for working drafts and minor post-generation edits.
Avoid it for legal, compliance, or highly formatted documents. Requires the S-Docs Edit Document permission.
Allow naming of new Salesforce Attachment with each edit
Let users rename attachments created during edits.
Prompts the user to enter a new attachment name after editing.
Use it when users need more descriptive version names.
Requires Allow Edit and works only when Create new Salesforce Attachment with each edit is also enabled.
Create new Salesforce Attachment with each edit
Create a new attachment on every edit instead of overwriting the old file.
Preserves prior versions by creating a fresh attachment after each edit.
Use it when version tracking matters more than storage efficiency.
Requires Allow Edit. Increases Attachment storage over time.
Show Content Version JSON field
Reveal a field for setting custom values on the generated ContentVersion record.
Shows the Content Version Field Assignment JSON input and lets you map custom values to file metadata fields.
Use it when downstream reporting, automation, or integrations depend on custom file metadata.
Works only with Salesforce Files. Fields must exist on ContentVersion. Invalid JSON causes errors. Merge fields inside the JSON use double braces: {{!Field}}.
Show Content Version JSON field Example:
Document Options - Other Options
Template contains international characters (Unicode fonts)
Enable Unicode character support.
Checkbox
Allows non-English and non-Latin characters to render correctly. Works with the Unicode enforcement setting.
Use it for accented characters, non-Latin scripts, or special symbols.
Enable it before testing translated or multilingual output. Unicode Enforcement Options
Show warning messages during document generation (Legacy)
Control whether non-critical warnings appear during generation.
Checkbox
Shows warning messages such as null merge fields, missing lookup data, field access issues, and non-critical formatting warnings.
Keep it enabled during testing and rollout.
Disable it only when known warnings create noise for users. Critical errors still appear.
Redirect back to record
Return users to the source record after generation.
Checkbox
Sends the user back to the base record after the document is generated.
Use it when document generation is part of a record-based workflow.
Leave it disabled when users usually review, edit, or email the document next.
Attach related case articles to outbound email
Include related case articles in the outbound email.
Checkbox
Adds related case articles to the email along with the generated document.
Use it for case response templates and support workflows.
Works only when the base object is Case and only during email send flows.
Unicode enforcement level
Set how aggressively Unicode handling is applied.
Picklist
Controls how strongly S-Docs enforces Unicode rendering. Options are blank or none, Data, and Strict.
Increase it only when Unicode output needs more support.
Higher levels add processing overhead. Also enable Template contains international characters.
Maximum versions retained in archive
Limit how many saved template versions are kept.
Text field (numeric)
Creates a new template version on each save and deletes the oldest versions when the limit is reached.
Use lower values for stable templates and higher values for heavily revised templates.
0 or blank keeps all versions and can increase storage over time.
Maximum versions retained in archive Options
List of merge fields that cannot be null
Block generation if required merge fields are empty.
Text area
Runs validation before generation. If any listed field is null, generation stops and the user sees an error.
Use it to enforce required business data before users generate a document.
Enter one field per line. Use double braces: {{!Object.Field}}. Do not use commas or semicolons.
Unicode Enforcement Options
(blank/None)
Standard handling
Fast
English-only documents
Use the default when Unicode support is not needed.
Data
Enforces Unicode in merge fields
Minimal
Western European languages
Good for accented Latin characters and lighter multilingual needs.
Strict
Full Unicode enforcement
Moderate
Asian, Arabic, Hebrew, and other complex scripts
Use it only when lower levels do not render characters correctly.
Maximum versions retained in archive Options
10
Keep the last 10 versions
Stable templates with occasional edits
Reduces stored version history.
25
Keep the last 25 versions
Templates under active revision
A balanced default for many teams.
50
Keep the last 50 versions
Complex templates with frequent changes
Keeps more rollback points.
0 or blank
Keep all versions
Rarely recommended
Use only when full retention is required and storage is monitored.
Last updated
Was this helpful?