M224 AUTO EVENT
Last updated Dec 18, 2017

Auto Sending of Email with Business data Inserted

By placing [Throwing Message Intermediate Event (E-mail)], an Email transmission event, an automated E-mail will be sent at each time the instance passing by. It is also possible to embed the business data that has been entered in the upstream processes into automated E-mail. For example, you can automatically send an email of the content of the reservations which has been confirmed through "Reservation process" to the customer (Reservation person).

M224-1-en


a. To External
Sending an email that is automatically inserted customer’s name, to promote coming to a store
b. To Internal
Delivering emails that is inserted a part of the order information to the members of the section, to share information at the same time as the order decision

a. Header Info
Set each of ‘To/Cc/Bcc’, ‘Subject’, ‘From’ and ‘Mail body’
b. Mail Body
Set up the body part of the Auto-sending e-mail
  • Data insertion command by referencing Business data is available as well (e.g. ‘Received date time is ${[Received Datetime:3]}’)
  • Embedding of System environment value which the Workflow platform manages is also available (E.g. ${var[applicationRoot]})
  • Email Address that does not comply with the standard specification (RFC5322) will result in an error. (e.g.: Contains consecutive dots)
  • E-mail attachments of over 5MB in total will result in an error
  • Usage like Mail delivery agency is prohibited. (Questetra BPM Suite SaaS Edition Terms of Service)
  • You may require to set the SPF record for your domain (Sender Policy Framework)

R2240 Inserting Business Data (Email)

R2241 SPF Setting

R2183 Error Notification on Email Sending

M224-2-en
M224-3



  • 2016-04-18 (Invoice Issuance flow): Episode 479: Cautions for Letting “Prorating” to Script Step
  • 2016-04-04 (Payment Confirmation flow): Episode 477: Business Process that Begins with a Request from the Outside is Worthy of Improvement
  • 2016-03-28 (Company Regulations Creation/Dissemination): Episode 476: Regulation Revision Flow is also “Regulation Browsing System”
  • 2016-02-01 (SLA Claim): Episode 468: Issuance of Service Credit on SLA
  • 2015-04-20: Centrally Management for the Quotation Data
  • 2015-03-23: Visualization and Labor Saving on Appraisal of Competitive Quotes
  • 2015-03-02: Outsourcer – Outsourcee, Cooperate Workflow Platform
  • 2015-02-23: Visualization of Progress inside BPO! (An example of fulfillment BPO)
  • 2015-02-09: Workflow Starts Automatically at ‘3,2,1, Action!’
  • 2014-12-29: Blog Article Posting Workflow, 400 Titles through Repetition in 5 Years
  • 2014-11-17: ‘Timed Event’ is Effective for Contract Renewal Process
  • 2014-09-16: What is all about ‘Full Automation’ of Business Process?
  • 2014-09-01: How to Create ‘Timed Email Transmission System’ in 5 Minutes for Non-programmers
  • 2014-08-25: How Long does it Take to Approve, in Average?
  • 2014-08-18: Status of ‘Trouble Ticket’, Automatically Shared
  • 2014-07-07: Cases that Business Data Altering is Inevitable
  • 2014-06-23: Update Order Management Process of Annual Service Agreement
  • 2014-06-16: Master Management to Make All the Client to “Input Select”
  • 2014-06-02: Trick for Eliminating Fluctuation from Client’s Name
  • 2014-05-26: Timed Updating of System Common “Choice XML”
  • 2014-05-07: Choices for both of Column A and B (Weekly report by store manager)
  • 2014-04-28: Standardization of the Hiring Process, Points to be Aware
  • 2014-04-21: Embedding Business Data in Auto-email! (Files, Choices…)
  • 2014-04-14: “Contrivance to Save In-house Ideas” on Workflow
  • 2014-03-31: Response to Brochure Request, Fully Automated?
  • 2014-03-17: Sending Certificate of Participation for Event in PDF (Workflow Automation)
  • 2014-02-10: Take Advantage of the Exhibition Questionnaire
  • 2014-02-03: Automatic Posting to a Blog System (OAuth 2.0 Connection)
  • 2012-07-02: Automatic “the Guide Mail” Transmission, One Month Prior to Contract Renewal