Common process initial event
This is the traditional event that indicates the beginning of the process. By selecting this type of process beginning, the users that have permission to start this process can start it through the Fluig request opening screen. Permissions are set through the attribution mechanism for this activity. For processes defined as public, any user can open requests in this process. Although this initial activity can be made in conjunction with other types of initial activities, Fluig will only accept one object instance for common start by diagram.
Conditional initial event
This event allows a new request workflow to be created whenever a conditional script returns true in a given time range. It is necessary to configure an integration user that will be the one used to open requests. When releasing a process containing a conditional initial event, an activity will be created in Fluig’s Task Scheduler, which is responsible for the periodic execution of the conditional script, as well as the creation of the request if the conditional script conditions are true.
Signal initial event
This initial event should be configured to monitor the issuance of a certain signal. When the signal this event is monitoring is issued by any activity issuing signals, a new workflow request opens. It is necessary to configure an integration user that will be the one used to open requests. It is possible to use more than one initial signal activity to monitor the issuance of different signals. However, in a scenario monitoring multiple signals, it is recommended that a multiple initial event or parallel initial event be used.
Timer initial event
This enables the creation of workflow requests in a given time range. It is necessary to configure an integration user that will be the one used to open requests. When releasing a process containing a timer initial event, an activity will be created in Fluig’s Task Scheduler, which is responsible for creating periodic requests for the process.
Multiple initial event
It allows to start a workflow request, periodically analyzing a set of conditions for a workflow request to be opened. These conditions may include one or more conditional scripts, as well as one or more signals to be monitored. If any conditional script has its conditions met or one of the signs has been issued, a workflow request will be opened to that process. It is necessary to configure an integration user that will be the one used to open requests. When releasing a process comprising a multiple initial event, an activity will be created in Fluig’s Task Scheduler, which is responsible for monitoring conditional signals and scripts related to this activity, as well as the opening of requests if one of the related conditions becomes true.
Parallel initial event
The behavior of this component is basically the same as the one for the multiple initial event but with an important difference. For a request to be opened in this process, it is necessary that all grouped conditions in this event be true.