Description:
This step retrieves the email template.
Inputs
- templateID– Select a template to get data
- varToStoreEmailTemplate– Variable/Global to store the email template data
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “getEmailTemplateDataDef” example.
- Create a new process definition named “getEmailTemplateDataDef” and open it in designer mode.
- Drag a “getEmailTemplateData” step to the canvas.
- Connect the dots between the start and “getEmailTemplateData” step as shown above.
- Define a variable or a global to store the result.
- Click the "getEmailTemplateData" step to configure its "Required" properties. Provide a name for the step. Select a template from the drop-down list to retrieve data. Provide a variable or a global reference to store the email template after execution. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should retrieve the email template data.
- To manage these templates, navigate to the Manage Config - Email Templates page.
- The email template used in this example is shown below.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.