Triggers define under which circumstances a process will be instantiated. They are events, which either start a process automatically or - as in the case of a manual trigger - allow an external event to initiate a process start. There are several types of triggers enabling process start by different resources: a performer, an incoming mail, a point in time or a JMS message. Each process needs at least one trigger, needs to be used as a sub-process or by an event action in order to be executed.
Please refer to the chapter Working with Triggers to get information on how to add, modify and delete triggers and how to set up parameters depending on the type of trigger you use.
Stardust currently supports the following trigger types:
A manual trigger - a user having the corresponding grant can start a process from the Stardust Workflow Execution Perspective.
A timer-based trigger - a process can be started at some point in time, whereby multiple instances of the process can be created depending on the defined periodicity.
A mail trigger - an incoming email starts a process passing all the information contained in the email as input data.
A JMS trigger - an incoming message starts a process passing all the information contained in the body of the message as input data.
For additional configurations and use of the respective trigger, refer to the Managing Daemons and the Audit Trail Model chapter of the Operation Guide.
A scan trigger - starts process instances via an implemented Scan tool.