Service Task (HTTP Request to Start Event)

An automatic step that sends an HTTP request to Message Start Event (HTTP) on the same workflow platform. You can easily establish an inter-app connection simply by setting the send data. When a workflow App including Message Start Event (HTTP) is released, the corresponding Service Task is automatically generated.

Configs: Common
  • Step Name
  • Note
  • Token will move to Error Boundary Event when processing fails
  • Specify the data to be sent to the item set in the Start event on the receiving side
    • For Title/String-type data, character input and EL expression are also possible
    • For Data Items other than String-type, specify by selecting Data Items in the same type as the receiving side
  • P: Data item to save Started Process Id
    • (String-type single-line Data Item)



  • A Service Task is automatically generated for each Message Start Event (HTTP) in a released App
  • If a Message Start Event (HTTP) on the receiving side is deleted then the corresponding Service Task will also be removed automatically
  • The name of the Service Task is the App ID App Name Node Number : Step Name
  • The App designer sets the Data Items that will receive data and the value that will be transmitted on the sending side
  • Only Data Items that are editable at the Message Start Event (HTTP) on the receiving side are subject to configuration on the sending side
  • For Title and String-type single line Data Items on the sending side, EL expressions are acceptable
  • If the sent data does not satisfy the required settings or input check of the Data Item on the receiving side, the Process startup will fail
    • You can avoid unnecessary errors by setting the Data Item to be sent to the same as the Data Item on the receiving side

See also

1 thought on “Service Task (HTTP Request to Start Event)”

  1. Pingback: Message Start Event (HTTP) – Questetra Support

Comments are closed.

%d bloggers like this: