Users can now configure the workflow to send result files via email to recipients configured within the email component. This document outlines how to configure and utilize the feature, along with the steps and conditions required for successful execution.

1. Configuring the Email Component

1.1 Adding the Email Component

To send result files after the workflow execution, users must include an Email Component in the workflow.

2. Attachment Options in the Email Component

Once the email component is added, users will see three options for attachments:

• None: No attachment will be included in the email.
• File: Allows users to attach a file to the email. This is particularly useful when sending documents like Excel sheets, etc.
• Data: Attaches a JSON file containing the result data.

3. Select Step Options

In the email component configuration, users can select a step from which to pull data for the attachment. The steps available in the dropdown menu are based on components added to the workflow before the email component.

Step Selection Rules:

• Excel Step: If the selected step is Excel, the user must select File as the attachment type.
• Other Steps (e.g., M3 Filter, REST API, Transform, Code):For all other steps, Data should be selected as the attachment type.

4. Workflow Execution and Email Sending

When the workflow is executed, the result file (either as a data or file attachment) will be sent to the email addresses listed in the To field of the email component configuration.

5. Error Handling for Incorrect Attachment Type

If the user selects a step such as Transform, Code, Rest API, M3 Filter, etc., and selects File as the attachment type, the workflow will fail with an error during execution. This is because Data must be selected as the attachment type for these steps.

6. Known Issues and Future Enhancements

• CC/BCC Email Addresses:

  Currently, users configured in the CC and BCC fields do not receive the email. This issue will be addressed in future sprints.