All Conditions in Triggers

What is this article about?

• Get an overview of all evaluation options for trigger conditions, which determine the correct time to execute actions

Who is this article for?

• Account admins and users with the AddOn Permission to create Triggers

A trigger is a set of conditions or events that automatically initiate a task or process, eliminating the need for manual action. 

A significant part of the trigger configuration is ensuring the correct conditions and timing for an action to run. For this purpose, you always select an evaluation option out of two main categories:

1. An existing object is updated
2. A new object is created

This guide will focus on the available evaluation options that are part of these two categories.

1. Trigger Actions when an Object is Updated

Objects in your tables will change over time. For example, purchase orders will be confirmed, or your transports will reach a specific transport status. 

To base your trigger condition on changes or updates that are made to an object, select the category 'Row updated'. 

In this category, you can choose from three evaluation options:

1. Every time the row is edited
   
• This executes the action whenever a change is saved for the object, regardless of which fields, values, or statuses are affected.
• For example: This trigger condition is useful for keeping a partner or connected IT system in sync via API by pushing every update as an XML or JSON file.
2. Whenever the conditions match
• This executes the action whenever a change is saved for the object, while the specific trigger conditions continue to be true for that object.
• For example: This trigger condition is useful for keeping partners informed of changes when the object meets certain conditions. For instance, you can push all updates via XML or JSON files as long as a transport order's status remains 'in transit.'
3. Whenever the change matches the conditions
   
• This executes the action only once, when a field is updated in such a way that the trigger condition becomes true.
• For example: This trigger condition is useful for notifying partners or triggering actions as soon as an object meets a specific condition, such as when a transport order reaches a particular status or location.

2. Trigger Actions when a new Object is Created

New objects are added to a table on a regular basis, either trough integrations with partners, using the Bulk Importer, or by manually creating a new form. To base your trigger condition on the creation of a new object, select the category 'Row created'.

In this category, you can choose from two evaluation options:

1. Every time a row is created
   
• This executes the action whenever a new object is added to the table, regardless of any further conditions or details.
• For example: This trigger condition is useful for notifying partners or triggering actions as soon as a new object is created, such as sending an email alert when a new customer account is added.
2. Row created with field conditions
   
• This executes the action, whenever a new object is added to the table that meets specific trigger conditions. 
• For example: This trigger condition is useful for notifying partners or triggering actions when a new object meets certain conditions, such as creating a purchase order for a specific material type.

Note: A trigger can only have one of the above described evaluation options, but within the trigger condition, several rules can be combined.

This guide is part of a series. For more insights into how to set up triggers have a look into the related articles below.

If you have additional questions, please do not hesitate to reach out to us at: [email protected]