
Throwing Message Intermediate Event (HTTP)
Transmits an HTTP request to the destination specified in Access URL. Also capable of saving the received response to a Data Item.
Capture
Network Settings Header Send Parameter
Notes
- Also possible to embed business data to Access URL
- Also possible to specify variables as values in Access URL or SEND Parameter
- If the connection destination (request destination) is Message Start/Catching Intermediate Event (HTTP), by clicking [Connecting to Message Start/Catching Message Intermediate Event (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
- Send Parameter has the following limits:
- Parameter name: 100 characters
- Fixed value: 1000 characters
- Content-Type when specifying the request body directly: 200 characters
- File name when saving the response: 200 characters
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
Pingback: Incorporate Optical Character Reading into Workflow (AI-OCR/BPM Integration) – Questetra Support
Pingback: System Settings – App External Connectivity – Questetra Support
Pingback: Common Password Request – Questetra Support
Pingback: Catalogue Request Correspondence Flow – Questetra Support
Pingback: Daily Report-weather record – Questetra Support
Pingback: Entrusted-Delivery Flow – Questetra Support
Pingback: Contract Approval Process – Questetra Support
Pingback: Salesforce Cooperation Process – Questetra Support
Pingback: Company Regulation Creation Flow – Questetra Support
Pingback: Designing Request Handling – Questetra Support
Pingback: Design Request – Questetra Support
Pingback: Understanding HTTP Authorization Settings – Questetra Support