Managing Email Templates
SETTINGS > ADMINISTRATION
You can view and manage the contents of email templates by using the Settings application.
The following email templates are supplied with Orckestra Commerce Cloud by default:
|
•
|
CustomerPasswordChanged |
|
•
|
CustomerPasswordResetRequested |
|
•
|
ProductPriceExportTaskCompleted |
|
•
|
ProductPriceImportTaxkCompleted |
When the email templates are active, notifications can be automatically sent when a new customer is created, when a password is changed, when a password reset is requested, when an order is created, when a Return Merchandise Authorization (RMA) is created, or when an RMA is finished. These default email templates can also be modified as required, or you can create your own email templates to meet your business requirements.
You can also use template variables so that you can reuse the same data in multiple email templates. For more information about template variables, see Managing Template Variables.
Scopes and languages:
Email templates belong to a specific scope. They can either be inherited by the child scopes so that the email template of the parent scope is used, or overridden in the child scope to customize the content for that scope.
Email templates can be created in the global scope, in a sales scope or a dependent scope.
|
•
|
When you modify a template created in a given scope, the modification is effective for all the scopes that inherit from that template. |
|
•
|
When you modify a template created in a scope, the inheritance associated with the parent scope is broken, and that version of the template is effective for the current scope and its child scopes. |
You can also inactivate a template for a specific scope.
You can create email templates by adding content using the Orchestration Console. However, the email template must be bound to a trigger in the code that sends the email.
For each scope, the email template content can be modified by language-culture.
For the default language, and every language that you require, all the fields of the email templates are mandatory. When you do not use a language, all the fields must be left blank.
The language-culture that is used to send communications is resolved as follows:
| • | The preferred communication language of the customer is used by default. |
| • | When no communication language is defined, the order language of the last customer order is used. |
| • | When no order is defined, the default language of the system is used. |
The template that is used is set as follows:
| • | Find the template by name for a specified scope, with inheritance. If no template is found, or if the template is inactive, do not send any email. |
| • | Get the localized templates for the specified culture and system language |
| • | If the template in the specified language is not valid, use the system language. |
Understanding Email Template Behaviors:
Active templates are considered as ready, and can be sent as part of the automated processes.
Inactive templates are considered as not ready, and cannot be sent as part of the automated processes.
The Inheriting from scope status is displayed at the top left of the email templates details panel when an email template is inherited from a parent scope.
The following rules apply to email templates:
|
•
|
When you create or override a template, the state of the template is inactive by default. |
|
•
|
When you save the template, the state of the active status is saved as selected by the user. |
|
•
|
When you create a template with the same name as an existing template in the current scope the following message is displayed: |
A template with the same name already exists in the current scope.
|
•
|
When you create a template with the same name as an existing template in a parent scope the following message is displayed: |
A template with the same name already exists in a parent scope.
REFERENCES