Throwing Message Intermediate Event (HTTP)

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 Process)] is more suitable for connecting to a [Message Start Event (HTTP)] in applications on the same workflow platform
• In a debug process or a process 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 process will be started as a debugging process
  • It is also possible to explicitly specify the Questetra-Debug header in the [Header] tab of the property

See also

• Settings when Questetra to be OAuth2 client
• R2250 Business Data Embedding (HTTP)
• R2251: HTTP Method
• R2253: Custom HTTP Header
• R2252: OAuth Token Getting Procedure
• R2271: Output of Date and Datetime Data via EL syntax
• R2272: Output of Strings via EL syntax
• M225: Auto Sending of HTTP Request with Business data Inserted