Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

The feature is currently available for a subset of email templates (10) and is in the beta stage. We plan to expand the capability of using a new email designer editor across all transactional email templates:

Classes of available documents actually: ORDER_CONFIRMATION,LETTER,ORDER_ACKNOWLEDGEMENT,ORDER_REJECTED,PASSWORD_CHANGE,PASSWORD_RESET,RESET_OPERATOR_PASSWORD,NEW_ACCOUNT,AUTHORIZATION_CONFIRMATION,B2B_ACCOUNT

Warning: Switching to transactional emails in production can corrupt your ticketshop's ongoing sales (customers would not receive an email). Please test beforehand the creation of a new email associating it with a single channel such as the test ticketshop.When your test is conclusive, you can associate your points of sales with the new model and delete the initial model. Carefully follow the instructions below:

You may already have a document associated with some (or all) sales channels. To test the creation of your new designer transactional email directly in production, we recommend that you create a new type of document, then a new template.

Existing document:

Create a new document type then a new “Design Editor” type template

To set up a design editor for transactional email, you can follow the instructions in the release note.

Note that then, if your test is successful, you can switch the points of sale with the new model, then delete the initial model. For example here, there are two order confirmations. Before making this change you can suspend the point of sale to avoid errors with current files on the ticketshop.

Importante note: You will notice that every template newly created template will be generating a *.json file that is available for download. Currently (in Beta status of the release) the uploading is not yet enabled. In future releases, we'll enable the possibility to upload those templates so that you can test them first in testing environments (such as preproduction) before uploading a final version to your production environment.



  • No labels