Introduction to Triggers in Frends
The Create Start Element is used to mark the starting point of the Process. A Start Element contains a single Trigger configuration. Multiple Start Elements can exist in the root level of the Process, but they all have to lead to the same Element.
Start Elements also exist, for example, within Scopes or Loops. A Start Element within a Scope does not contain a Trigger configuration, it's only used to mark the starting point of the Scope.
Triggers are registered by the Agent and can only activate if the triggering event is registered by the hosting server.
Triggers are an integral part of any Frends Process as they are the way that a Process can be started dynamically based on an event that the Agent is able to receive. The Trigger also acts as a starting point for the Process and the first step in the Process diagram.
This means that if you are creating a REST API you should use and configure an HTTP Trigger or an API Trigger as the start event for that integration Process. Likewise in the case of a batch job you should most likely use a Schedule or a File Trigger.
Triggers in the Process
Triggers are used when developing a Process and they are the first Element in the Process Editor Canvas. You can then configure the Trigger to match the integration scenario that is being developed.
Note that you can have as many Triggers as you would like in any Process and you can use different Trigger types together, however as independent Elements. This means that you can create a Process that has a File Trigger which runs the Process whenever a file is created in a specific folder and you can have a Schedule Trigger which runs the Process every 6 hours.
Triggers also use the #hashtag notation to offer relevant information about the event that initiated the Trigger, as an example the File Trigger offers the name and metadata of the file that it was triggered from. You can then use this information to build logic in the Process itself.
Different Trigger types
Currently Frends supports the following Triggers:
Manual
Schedule
File
API
HTTP
Queue
Service Bus
RabbitMQ
Conditional
The next article is Introduction to Manual Trigger