File names

Every file Sliick Docs produces gets a name from one of three rules. This page collects them, because the wrong name is the most common reason two generations on the same record appear to overwrite each other.

Runtime files, with no pattern set

<Record Name> - <Template Name> - <date and time>

This is the default, and it is what most templates should use: repeat generations, and different templates on the same record, stay distinguishable in the Files list and in anything the file is emailed or sent on to.

The default appears in the empty File name pattern box as a greyed hint rather than being written in as a value, so blank stays blank.

Runtime files, with your own pattern

The per-template File name pattern is used exactly as typed and is never auto-suffixed. Merge-field tokens work as they do everywhere else, for example {{Account.Name}} - Summary.pdf, plus two built-ins available from the field picker:

Token	What it stamps
{{GeneratedDate}}	The generation date, in the generating user’s time zone.
{{GeneratedDateTime}}	The generation date and time, in the generating user’s time zone.

Automation contexts stamp in the automation user’s time zone.

Note: if two documents generated on the same record appear to overwrite each other, the template has an explicit pattern with no timestamp in it. Clear the pattern to take the default, or add {{GeneratedDateTime}} to your own.

Proof files

<Template Name> - v<Version Number> - Proof - <Record Id>.<ext>, where the extension is pdf or docx.

Rules that apply to every name

• The extension auto-swaps to .docx for Word output. See Word output.
• Illegal filename characters are stripped automatically.
• The whole name is capped at 255 characters, which is the Salesforce limit for a file title.