Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Classes of currently 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 emailemails anymore, or the sales process could even be blocked if your template contains errors). Please test beforehand the creation of a new email associating it with a single channel such as the a test ticketshop, so that it will not impact your real ticketshops. When your test is conclusive, you can associate your points of sales with the new model and delete the initial modelold one. Carefully follow the instructions below:

You may already have a document associated with some (or all) sales channels. In production, 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 Keep your existing documents and create a new one for designer associated to the test ticketshop:

Step 1: To create Create the new document type then a new and choose “Design Editor” type template

...

Step 2 : Notethat 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 pause the point of sale in order to avoid errors with current files on cases in the ticketshop. Plan for these changes when you believe there are no customers connected to the ticketshop.Image Removed

Importante note:  You 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.

...