Hide last authors
gru 16.2 1 {{figure image="1_en_TemplatesEmail.png"/}}
gru 1.1 2
gru 16.2 3 Email templates are used by [[workflow actions>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.WebHome]] of type [[//Email//>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.EMail]], as well as for sending system mails such as password recovery mails.
gru 1.1 4
5 {{info}}
gru 16.2 6 To use mail templates with action of type //Email//, you need to enter the [[template variables>>doc:Formcycle.UserInterface.Variables]] for the template as the content of the mail. For example, when the mail template has been called {{code language="none"}}mail_demo{{/code}}, the mail's content must be {{code language="none"}}[%$$mail_demo%]{{/code}}.
gru 1.1 7 {{/info}}
8
gru 16.2 9 Furthermore, [[variables>>doc:Formcycle.UserInterface.Variables]], e.g. in order to add a link to the form or inserting the value of certain form fields.
gru 1.1 10
gru 16.2 11 Depending on the client, three or four system templates are available initially. You can also create your own custom templates.
gru 1.1 12
gru 16.2 13 * **User created**
14 Used for sending login information to users when their account has been created with either the option //Generate password// or the options //Set password manually// and //Send user credentials by email// selected.
15 * **User created (LDAP)**
16 Used for sending login information when an LDAP user account has been created. As it is not possible to send the password from an LDAP account, a different mail template is used.
17 * **Password set**
18 Used for sending login information to users when their account has been created with the option //Password set by the user//.
19 * **Password reset**
20 Used for sending password recovery mails to users.
gru 1.1 21
gru 16.2 22 == Reseting a template ==
23
24 You can reset a template to its default by clicking on //Reset//. All changes will be lost and cannot be restored.
Copyright 2000-2024