Catching Message Intermediate Event (HTTP)

Catching Message Intermediate Event (HTTP)

Holds a token and listens for HTTP requests at a specific URL. Receiving an HTTP request, the token advances. Capable of receiving values in parameters and overwriting business data.

Configs: Common
  • Step Name
  • Note
Configs: Editing permission
  • Data Item
    • Editing permission
      • (Editable)
      • (No display)
Configs: API key
  • API key
Reception Parameter, IP address filtering (Opens in new tab)
App
  • App name
Name
  • Event name
Node Number
  • number
URL
  • https://{YOUR_DOMAIN}/System/Event/IntermediateMessaget/{APP_ID}/{NODE_NUMBER}/receive?key={API_KEY}
  • ${var[applicationRoot]}System/Event/IntermediateMessaget/{APP_ID}/{NODE_NUMBER}/receive?key={API_KEY}
Allowed Hosts/Networks
  • (Overview of related IP Address Filtering)
Reception Parameter
    • Reception Parameter Name / Detail / required / About Parameter Value / Fixed Value
Auto-Processing Log
  • view_column (Column)
    • drag_handledelete Date and Time (Default)
    • drag_handledelete Process ID (Default)
    • drag_handledelete Version (Default)
    • drag_handledelete Type (Default)
    • Add
      • (Add All)
      • Log ID
      • App ID
      • App Name
      • Node Number
      • Step Name
      • User ID
(Logs list)
    • Date and Time / Process ID / Version / Type
  • (Display control)
    • (View)
      • 10, 20, 50, 100, 200, 500, 1000
    • Page

Capture

Notes

  • You can check and copy the receiving URL to clipboard in the property screen
  • You can check the Reception Parameter and IP filtering Details in the other page after clicking the button in the property screen
  • Even though it is possible to leave the API key blank, please set the API key with halfwidth alphanumeric characters, at most 100 in length to tighten the security
  • Numeric-type Data Items in which an arithmetic expression has been set cannot be set to Editable
  • Please make requests with POST (application/x-www-form-urlencoded or multipart/form-data)
  • If successfully processed, the HTTP response code 200 is returned
    • The response body is “empty” (text/plain)
  • If processing fails, an HTTP response code other than 200 is returned
    • In this case, the token remains here, and the listening state of this event continues
    • An HTTP response code of 400 and an error message in XML format (text/xml) are returned in the following cases
      • The received data does not include content for the required settings in the process data item that will store the data, and does not meet the minimum/maximum number of characters and input validation conditions of the item
      • Invalid values for parameters such as App ID
      • The token has not yet reached this event and the API is not ready to receive requests
      • R2212: XML Format of Error Responses for Receiving HTTP Requests
    • HTTP response codes in the 400s are returned, but the response body is not specified in the following cases
      • The received HTTP request has exceeded the data size limit that can be received via HTTP communication
      • The HTTP request format (method/Content-Type) is not the required format

See also

Scroll to Top

Discover more from Questetra Support

Subscribe now to keep reading and get access to the full archive.

Continue reading