By placing the [Throwing Message Intermediate Event (email)] an automated email will be sent each time the Event is passed. It is also possible to embed business data that has been entered in the upstream Cases into the automated email. For example, it is possible to automatically send to the customer the reservation details confirmed in the "Reservation Acceptance App".
1. Usage Example of "Sending Email"
- a. To External Recipients
Send an email that automatically inserts the customer's name and encourages them to come to a store
- b. To Internal Recipients
At the same time as an order is confirmed, mail will be distributed within the department with part of the order information inserted, and information will be shared.
2. Setting Up Email Transmission
- a. Header Info
Set the 'To/Cc/Bcc', 'Subject' and 'From' fields
- b. Mail Body
Set the text part of the auto-sending email
- Using the Field Name of the Data Items you can insert the value of the item (E.g.: "Received date and time is #{＃q_datetime}.)
- Insertable values conform to assignment to String-type Data Item
- It is also possible to insert system constants managed by the workflow platform (e.g. ${var[applicationRoot]})
- Email Addresses that do not comply with the standard specification (RFC5322) will result in an error (e.g. An address containing consecutive dots)
- Emails over 10MB after MIME encoding will result in an error
- It cannot be used as a mail delivery agency (Questetra BPM Suite SaaS Edition Terms of Service)
- You may need to set the SPF record for your domain (Sender Policy Framework)
R2240: Available Items for Specifying Address (To/Cc/Bcc)
R2272: Output of Strings via EL syntax
R2241: SPF Setting
BPMN Icons: Throwing Message Intermediate Event (Email)
X. Tutorial
X. FAQ
- Can I Embed an Image File in the Body when Sending an Email?
- Can I Embed "a Hyperlink to Detail Page" in the Body of an Auto-sending Email?