Switch to a new template version
When you publish a new version of a template, a Postflow can follow it automatically or stay on the version you chose. That choice is the version policy of the Postflow.
The two version policies
| Version policy | What it does |
|---|---|
| Latest published | The Postflow follows new versions automatically. This is the default. |
| Pinned version | The Postflow keeps one version until you change it. |
Change the version policy
- Open Postflows and choose the Postflow.
- On the Flow tab, choose the template step. It shows the template name and the version in use, for example v3.
- Under Version policy, choose Latest published or Pinned version.
- For a pinned version, pick the version under Pinned version.
- Choose Save.
The template step also shows Version in use and Latest published, so you can see at a glance whether the Postflow is behind.
Move pinned Postflows when you publish
When you publish a new version and pinned Postflows use the template, the publish dialog offers to move them. Tick the option, for example "Use v4 in the pinned Postflow Welcome card from the next item", and choose Publish. If a Postflow could not be moved, the editor tells you, and you change it on the Postflow itself.
Which items get the new version
An item gets its template version at the moment it becomes ready to print. So after a switch:
- Items that are still held, or waiting for approval, get the new version when they become ready.
- Items that are already ready, scheduled or in production keep the version they were given.
Check the new version before it goes out: open the template and use Preview or Proof PDF next to the version. See Preview and proof PDF.
A new version can add a required field. Items that arrive without a value for it need attention, so update your Salesforce flow or integration at the same time.
Open a support ticket in the portal. Tell us what you tried and, if you can, which item or Postbatch it is about.