Message Start Event (HTTP)

Issues a URL that awaits an HTTP request. Starts a new Process automatically when an HTTP request is received. Capable of inserting values accepted as receive parameters to Business Data.

Configs: Common
  • Step Name
  • Note
Configs: Editing permission
  • Data Items
    • Editing permission
      • (Editable)
      • (No display)
Configs: API key
  • API key
URL, Reception Parameter (Opens in new tab)
App
  • App name
Name
  • Event name
Node Number
  • Number
URL
  • Starting/Receiving URL
    • http s://{YOUR DOMAIN}/System/Event/MessageStart/{APP ID}/{NODE NUMBER}/start
    • ${var[applicationRoot]}System/Event/MessageStart/{APP ID}/{NODE NUMBER}/start
Allowed Hosts/Networks
  • (Overview of related IP Address Filtering)
Reception Parameter
    • Reception Parameter Name / Detail / Required / About Parameter Value / Fixed Value
Data Visibility from Parent Process
  • Data Item
    • Data Visibility from Parent Process
      • (Allow)
      • (Forbid)

Capture

Notes

  • You can check the launching URL and parameter details in the other page after clicking the [URL, Reception Parameter] button in the property screen
  • The value of API key (key) can be set arbitrarily with halfwidth alphanumeric characters, at most 100 in length
    • Even though it is possible to leave the API key blank, please set the API key to tighten the security
  • If the incoming HTTP request data does not meet the Data Item constraints, such as required settings and minimum/maximum character length, the process will not start
  • It may not be started automatically due to the limit on the number of startups on the entire Workflow platform
  • Communication from the external network is not permitted by default on the Workflow platform
    • To allow communication from an external network, change the settings in [IP Address Filtering] < [System Settings] (M312: System Administrator Authority Required)
    • It is possible to set an IP address filter for each trigger URL
  • If the incoming request has a “Questetra-Debug: true” header, it will start as a debug process
    • If the caller is a debug process, or the header has been explicitly added
    • Human Task handling in the debugging Process is assigned to the final editor of the App
  • When a Process is started by calling this event from a [Throwing Message Intermediate Event (HTTP)], etc. within the same platform, a parent-child relationship is established with the started Process as a child and the calling Process as a parent
    • The child Process has the ID of the parent Process as Process attribute information
  • [Service Task (Start Child Process)] is an item for sending an HTTP request to this Start Event to start a child Process
    • When a [Message Start Event (HTTP)] is set, the corresponding [Service Task (Start Child Process)] will appear in the modeler palette one by one

See also

%d bloggers like this: