Templating

Templating lets you drop live values into text using ${...} placeholders. When the text is used, each placeholder is replaced with the current value from the process - so names, messages, and settings adapt to each instance instead of being hard-coded.

Where you’ll use it

Instance Naming Template - give every process instance a meaningful name. Instead of a generic id, Register ${name} or Assign ${group} to ${user} produces a name you can actually scan in a list.
Messages and notifications - email subjects and bodies, or any text field that supports templating, can address people and reference specifics: Hi ${Candidate.First Name}, your interview is confirmed.
Integration parameters - connector settings that vary per environment or per call, such as a base URL like https://${shop}.example.com.

Writing a template

Reference a value by its name: ${Total}.
Reach into a nested value with a dot: ${Customer.First Name}.
Mix freely with plain text: Invoice for ${Customer.Name} - ${Total}.
You can also use system values where they’re offered, such as the instance id.

Good to know

If a placeholder doesn’t match a value, it’s left as-is in the text - so a typo shows up literally (e.g. ${Custmer.Name}). Check your names.
Values used in a URL are encoded automatically, so they stay valid.

Templating vs. document templates

Two different tools - don’t mix them up:

Templating (this page) - ${...} placeholders inside text fields.
Document Templates - full HTML layouts rendered to a PDF by Generate Document.