Triggers

The 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 exists e.g. within Scopes. 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 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.

These events can include:

1. A file is created to a designated folder

2. A webservice call is recieved by the Agent

3. A message appears in a queue the Agent is subscribed to

4. A schedule is activated in it's time window

5. A manual message is sent by the user through the FRENDS UI

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.

Using Triggers

Triggers are used when developing an integration 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 developped.

Note that you can have as many triggers as you would like in any process and you can combine different trigger types together. This means that you can create and integration process that is run whenever a file is created to a folder AND atleast 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 following triggers:

• File Trigger

• HTTP Trigger

• API Trigger

• Schedule Trigger 

• Queue Trigger

• Manual Trigger

• Service Bus Trigger 

• Conditional Trigger 

The type of trigger that started the process can be checked by reference #trigger.type. It can have values as string:

ManualTrigger
FileWatchTrigger
QueueTrigger
ScheduleTrigger
ServiceBusMessageTrigger
HttpTrigger
HttpApiTrigger
SubProcess

The last one is Conditional Trigger.