Throwing Message Intermediate Event (HTTP)

Overview

Transmits an HTTP request to the destination specified in Access URL. Also capable of saving the received response to a Data Item.

Configs: Common

mode_edit_outline Step Name
mode_edit_outline Note

Configs: Network Settings

mode_edit_outline Access URL *^#{EL}
- arrow_drop_down Insert reference…
  - Title
  - Case Start User
  - Case Start Organization
  - Case ID
  - Case Start Datetime
  - Case Sequence Number
  - App ID
  - App Name
  - (Data Items)
  - System Variable: Application Root
arrow_drop_down HTTP Method
- GET
- POST (application/x-www-form-urlencoded)
- POST (multipart/form-data)
- POST (Specify Request Body)
  - arrow_drop_down Data item to send as request body (String multiple lines / String Markdown / File) *
    - (Data Items)
      - mode_edit_outline Content-Type of Request body *
- PUT (Specify Request Body)
  - arrow_drop_down Data item to send as request body (String multiple lines / String Markdown / File) *
    - (Data Items)
      - mode_edit_outline Content-Type of Request body *
- PATCH (Specify Request Body)
  - arrow_drop_down Data item to send as request body (String multiple lines / String Markdown / File) *
    - (Data Items)
      - mode_edit_outline Content-Type of Request body *
- DELETE
arrow_drop_down Data item to save the response (String multiple lines / String Markdown / File)
- Not Save
- (Data Items)
  - mode_edit_outline (In case File-type is chosen) Saving file name *^#{EL}
    - arrow_drop_down Insert reference…
      - Title
      - Case Start User
      - Case Start Organization
      - Case ID
      - Case Start Datetime
      - Case Sequence Number
      - App ID
      - App Name
      - (Data Items)
      - System Variable: Application Root
arrow_drop_down Data item to save error details (String multiple lines)
- Not Save
- (Data Items)

Configs: Header

arrow_drop_down Authorization Header *
- Not use
- Use
  - arrow_drop_down Authorization Settings to use *
  - [Set from here]
add Header
- drag_handle (move)
- edit (edit)
  - mode_edit_outline Header Name
  - mode_edit_outline Header Value
- delete (remove)
- (specified Header Name)
- (specified Header Value)

Configs: Send Parameter

add Send Parameter
- drag_handle (move)
- edit (edit)
  - mode_edit_outline Parameter Name
  - mode_edit_outline Parameter Value
    - Fixed Value
    - Case ID
    - Title
    - (Data Items)
- delete (remove)
- (specified Parameter Name)
- (specified Parameter Value)

Capture

Notes

Also possible to embed business data to Access URL
Also possible to specify variables as values in Access URL or Send Parameter
For HTTPS communication, only requests to well-known port (443) are allowed.
If the connection destination (request destination) is [Message Start Event (HTTP)] or [Receive Task (HTTP)], by clicking [Connect to Message Start Event / Receive Task (HTTP)] button you can view information such as URL and parameters
- Connect to Event in the same server
- Connect to Event in the outside server
Data Item to save the response will be empty when the processing completed normally
In “HTTP Method”, if (Specify Request Body) is selected, the following limit applies:
- Content-Type of request body: 200 characters
If a File-type is selected in “Data Item to save the response”, the following limit applies:
- Saving file name: 200 characters
Send Parameter has the following limits:
- Parameter Name: 100 characters
- Fixed Value: 1000 characters
[Service Task (Start Child Case)] is more suitable for connecting to a [Message Start Event (HTTP)] in applications on the same workflow platform
In a debug case or a case started by clicking the [Debug only this node] button, a “Questetra-Debug: true” header is automatically added to the sending HTTP request
- If the destination is a [Message Start Event (HTTP)], the case will be started as a debugging case
- It is also possible to explicitly specify the Questetra-Debug header in the [Header] tab of the property