Description:
This step removes the stored message from an email trigger.
Inputs
- msgIDVariable - Variable that holds the message ID
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
To use this step, the email trigger should be configured in the FlowWright application.
Example:
Let’s build and execute the “removeEmailMsgDef” example.
- Create a new definition called “removeEmailMsgDef”
- Select the definition and click the “design” button
- Drag the above steps from the toolbox to the canvas
- Connect the dots between the Start and the above steps
- Click on the “executeSQL” step to configure its “Settings” properties. Provide a step name. Select the connection string from the drop-down list. Provide the SQL statement to fetch the email message records from the deEmailMsgs table. Select the result form as XML. Click the Save button to confirm.
- Click the “getEmailMsg” step to configure its “Settings” properties. Provide a step name. Provide a variable/global to store the messageID, email from and to address, message content, and file lists.
- Click the “removeEmailMsg” step to configure its “Settings” properties. Provide a step name. Provide a variable/global reference to hold the message ID.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.
- Save the process definition, create a new process instance, and execute. Render the process instance. Click on the process step to view the properties. The step should remove the stored email with the variables/globals holding the email message body, from and to address, etc.
Definition Sample:
You may download the sample definition(s) from the link here and later import it (drag-drop) to 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 import. Then, save the definition to confirm the changes.