Publish message templates publishing-template-messages

Template publication template-publication

When the message template created on the control instance is complete and once you have tested it, you can publish it. This process will also publish it on all execution instances.

Publication lets you automatically create two message templates on the execution instances, which will allow you to send messages linked to real-time events and batch events.

When publishing transactional message templates, typology rules are also automatically published on the execution instances.
Whenever you make any changes to a template, make sure you publish it again for these changes to be effective during transactional message delivery.
  1. On the control instance, go to the Message Center > Transactional message templates folder of the tree.

  2. Select the template you want to publish on your execution instances.

  3. Click Publish.

Once publication is complete, both message templates to be applied to batch and real-time type events are created in the tree of the production instance in the Administration > Production > Message Center Execution> Default > Transactional message templates folder.

Once a template is published, if the corresponding event is triggered, the execution instance will receive the event, link it to the transactional template and send the corresponding transactional message to each recipient. For more on this, see Event processing.

If you replace an existing field of the transactional message template, such as the sender address, with an empty value, the corresponding field on the execution instance(s) will not be updated once the transactional message is published again. It will still contain the previous value.
However, if you add a non-empty value, the corresponding field will be updated as usual after the next publication.

Template unpublication template-unpublication

Once a message template is published on the execution instances, it can be unpublished. For more on the template publication process, see this section.

  • Indeed, a published template can still be called if the corresponding event is triggered: if you are no longer using a message template, it is recommended to unpublish it. This is to avoid sending an unwanted transactional message by mistake.

    For example, you published a message template that you only use for Christmas campaigns. You may want to unpublish it after the Christmas period is over, and publish it again next year.

  • Also, you cannot delete a transactional message template that has the Published status. You must unpublish it first.

This capability is available starting Campaign 20.2 release.

To unpublish a transactional message template, follow the steps below.

  1. On the control instance, go to the Message Center > Transactional message templates folder of the tree.

  2. Select the template you want to unpublish.

  3. Click Unpublish.

  4. Click Start.

The transactional message template status changes back from Published to Being edited.

Once unpublication is complete:

  • Both message templates (applied to batch and real-time type events) are deleted from each execution instance.

    They no longer appear in the Administration > Production > Message Center Execution > Default > Transactional message templates folder (see this section).

  • Once a template is unpublished, you can delete it from the control instance.

    To do so, select it from the list and click the Delete button on top right of the screen.