By placing the [Throwing Message Intermediate Event (HTTP)] an HTTP request will be sent each time the Event is passed in the workflow. It is also possible to embed business data that has been entered in the upstream Steps into the request. For example, you can automatically get weather information in the App "daily report with the weather information".
1. Usage Example of Sending an HTTP Request
- a. Acquisition of External Data
Retrieving data from an external site (e.g. Obtaining weather information or currency exchange information)
- b. Data Transmission to an External System
To transmit data (REST communication) to the Core system
- c. Data Transmission to Another App
Transmitting business data to another Workflow App (e.g. Handover business data to the newly started downstream Case)
- Use [Service Task (Start Child Case)] to newly start another Workflow App on the same workflow platform
Service Task (Start Child Case)
2. Setting Up HTTP Request Transmission
- 1. Setting Access URL
Set the URI of the destination server
- 2. Setting Content Data
Set the parameter name and 'Business data' (or fixed string)
- You can select GET, POST (application / x-www-form-urlencoded), etc.
- It is possible to embed Business data in the access URL.
- It is also possible to store the responses from the server-side in the Data Item
- HTTP requests will not be sent if connection destinations for HTTP communication are restricted on the workflow platform
R2250: Business Data Embedding (HTTP)
R2251: HTTP Method
R2253: Custom HTTP Header
BPMN Icons: Throwing Message Intermediate Event (HTTP)
3. Configure HTTP request Sending for an External API that has Access Restrictions
- a. Set up Basic Authentication Communication
Set the ID and Password to use the destination server
- b. Set up OAuth Authorization Communication
Configure settings to allow automatic communication with the connection destination server
- Authentication settings are set on a separate screen that opens with the [Set up setting] button
- OAuth communication in which Questetra is the client is available only in OAuth 2.0.
- HTTP communication from Workflow Apps will be restricted to authorized domains only
- The "access token" will be transmitted in the HTML header. (e.g. "Authorization: Bearer abcdefghijklmno")
- If 401 (Unauthorized) is received in the response of OAuth communication, it will be re-requested after re-acquiring the "access token"
R2252: OAuth Token Getting Procedure