Conditions

Conditions are requirements which need to be validated before the actions of the trigger can be applied. On this page we only highlight some conditions that might need a little bit of extra explanation:

Visitors (upcoming/last) active profile

This condition will check the active profile. The active profile is always - in this order:

• Profile of today

• first upcoming profile

• most recent profile in the past

There is always only 1 active profile

Visitor’s previous/current status

The previous status will be taken into account when using the trigger: When a visitor’s status changes. Otherwise the current status is used.

Visitor profile(s) validity (compared to past/future)

While this condition in itself is quite straightforward, we have noticed the devil is in the details when comparing timings. We even noticed that during development we unfortunately evaluate this condition differently in time based triggers. In the future we will solve this. For now the table below explains the expected behaviour:

Visitor’s type

This condition is only visible when Multiple Check-in is enabled for your tenant

It helps differentiate between one-time visitors and those who can check in multiple times:

• Visitor: Can only check in once.

• Original Multiple Check-in visitor: The primary visitor from whom all subsequent multiple check-ins are cloned.

• Multiple Check-in visitor

For more information see: Multiple Check-in .

Previous/current process step

The previous process step will be taken into account when using the trigger: When one of a visitor’s process steps changes. Otherwise, the current process step is used.

Checklist/Dropdown field to match “any” of the options

Dropdown

When dropdowns are used, the user can only select 1 item in the input field.

However, it's possible to create a trigger with a condition that checks multiple selections simultaneously:

Next logic is applied:

• IS → evaluates TRUE if the input item is ONE OF the selected items

• IS NOT → evaluates TRUE if the input item is NONE OF the selected items

Checklist

When checklists are used, the user can select multiple items in the input field:

However, it's possible to create a trigger with a condition that checks multiple selections simultaneously:

You can compare with many items, with next logic:

• IS → evaluates TRUE if the input items CONTAINS AT LEAST ONE OF the selected items (at least)

• IS NOT → evaluates TRUE if the input items DOES NOT CONTAIN ANY OF the selected items (none of)

Use case example: one asks the visitor during the registration which safety materials he has:

• Helmet

• Safety jacket

• Safety shoes

You want to define a trigger that needs to fire if the visitor has selected “Helmet” (regardless the choice for “Safety jacket” or “Safety shoes”).