Last updated Mar 15, 2018

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.


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”
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
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