Processes can be configured to send email automatically. This is done by writing records to the EU_OUTGOING_MAIL and EU_OUTGOING_ATTACHMENT special platform objects from within the process logic workbook. The platform queues and delivers the emails asynchronously once the process has run.
How outbound email works
When a process writes records to EU_OUTGOING_MAIL, the platform adds those emails to an outgoing queue. If attachments are also defined via EU_OUTGOING_ATTACHMENT, the platform waits until the attachment files are ready before sending. Emails are sent from a platform system address by default. Instance-specific sender addresses can be enabled by support.
The total size of each email, including all attachments, must be under 20MB.
Step 1 — Register permitted recipients
The platform can only send email to addresses registered as permitted recipients. Any process output targeting EU_OUTGOING_MAIL will fail silently for addresses not on this list.
To register recipients, go to Email Management \> Outgoing Mail Recipients in the Configuration application. Click New, enter the number of recipients to add, and click Add. For each recipient, enter a Name and Email Address, add an audit comment, and click Save and Refresh.
Step 2 — Add attachments (optional)
To attach files to an outgoing email, define a named range in the process logic workbook with three columns: Email (must match the unique key of the corresponding EU_OUTGOING_MAIL record, in the format Sender Account::Date Submitted::Recipients::Subject), Attachment Name (the filename as stored in the Report File object, including extension), and Attachment File (leave blank — populated by the platform).
Add a second Process Output mapping this named range to EU_OUTGOING_ATTACHMENT. The platform will wait for attachment files to be available before sending.
Monitoring outbound email
Sent emails and any failures are visible in the outgoing mail log. See Email Security and Error Handling for a reference of possible failure states and their causes.