M221: Auto Starting Triggered by HTTP Request

By placing [Message Start Event (HTTP)] which is a mechanism of HTTP Start at the top, a new issue that takes over request data will be automatically started every time it receives an HTTP request. For example, you can build inter-system collaboration, such as launching a "Payment Reminder process" from the backbone system easily.

1. Usage Example of HTTP Start

a. Starting by Other Systems

"Error Address Corresponding flow" will be Started automatically by the customer management system

b. Starting by Other App

Automatically passing the Order data in "Contract flow" to the "Production flow"

2. Setting HTTP Start

1. Receiving Data Item

Set the data viewing level (read/write permission) to Editable (read-write)

• After releasing the Model, you will be able to see the Starting URL (request URL) or "Names" of parameters, etc.
• As a data receiving parameter, you can specify the [Field name] set in the data item

3. Preparing Mechanism of Data Transmission (External Setting)

1. Request URI

Specify App ID and Event Node number using Path Parameter

2. POST body parameter

Specify "API key" and "business data that you want to update with"

$ curl https://sample.questetra.net/System/Event/IntermediateMessage/123/0/start \ -d "key=XYZXYZ" \ -d "data[0].input=foo" \ --data-urlencode "data[1].input=日本語"

• Request parameters can be either of GET / POST (POST is recommended, GET is partially prohibited)
• File data are transmitted in POST multipart
• System variable of “${var[applicationRoot]}” is available if it is the communication on the same Workflow platform
• The value of the API key can be arbitrarily set
• It is possible to filtering source IP address for each start URL (M312)

R2182: Error Notification of HTTP Start
R2210: Naming Convention for Data Receiving Parameter

---

X. Workflow-Sample

• 2017-01-10 (Telephone survey Process): Episode 517: Method of Starting up a Large Number of Workflows
• 2015-07-21 (Acceptance of Updated Information): Tributary in Each Subsidiary Merges to Form Mainstream
• 2015-04-27: Cooperation of Invoicing Flow and Accounting System
• 2015-04-13: Platforming the Translation Workflow
• 2015-03-02: Outsourcer - Outsourcee, Cooperate Workflow Platform
• 2015-02-09: Workflow Starts Automatically at '3,2,1, Action!'
• 2014-12-22: Using SaaS Workflow for Backend of Smartphone App for Business
• 2014-12-15: Labor Saving of Mailing Work, the Backend for it
• 2014-11-25: Importing the Records of Decision-making of the Past in Bulk
• 2014-10-06: Data Structure of an 'In-house Questionnaire' that Gathers n Answers to One Project
• 2013-12-02: Processin Business Data in Child Process (Translating) (Document Translation flow)
• 2013-05-31: Automation for Invoice PDF (Invoicing flow)
• 2013-04-08: Age of Cloud-based Workflow Capable of Running Even a Core System of 1 Million Dollar Worth (Orders-Operation-Bill Issuance)