How to add conditions to relevant fields in an Event Pipeline
Applies to user roles: People with access to Objects in Settings
Available on platforms: Vatix Workspace web app
You can show the people handling an Event only the fields that matter for that Event at each stage. When you add conditions to a relevant field, it appears only on the Events it applies to, such as injury details on accidents.
Before you start
- You need access to Objects in Settings. If you don't have it, contact the people in your organisation responsible for configuring it.
- The field you want to show and the field it depends on must both exist on your Events. You can add fields in the Field Manager.
How to add a condition to a relevant field
- Click the gear icon in the top right to open Settings, then select 'Objects' > 'Events' > 'Pipelines'.
- Click the Event Pipeline you want to change, then select the stage.
- In 'Relevant & Required Fields', select the checkbox next to the field you want to show only on some Events.
- Click 'Only show if' next to the field.
- In 'Select a field', choose the field this one depends on. Fields already relevant in this Event Pipeline are listed first, under 'Relevant in this pipeline'.
- Choose a comparison, such as 'is' or 'is any of', then select or enter the value if it needs one.
- To add another condition, click 'Add condition', then choose 'and' or 'or' between the conditions. With 'and', the field appears only when every condition matches. With 'or', one matching condition is enough.
- To make the field required on the Events it appears on, turn on 'Required when shown'.
- Click 'Publish' in the top right.
When you click 'Only show if' again to close the conditions, a summary appears under the field name, for example 'Only shown if Event type is Accident'.
Note: If you close a condition before it's finished, you'll be asked to finish it, or to remove it with the cross at the end of the row.
Which comparisons you can use for each field type
| Field type | Comparisons |
|---|---|
| 'Dropdown', 'User', 'Lookup' | 'is', 'is not', 'is any of', 'is none of', 'is empty', 'is not empty' |
| 'Short Text', 'Long Text', 'Number', 'Location' | 'is', 'is not', 'contains', 'does not contain', 'starts with', 'is empty', 'is not empty' |
| 'Date', 'Date/Time', 'Time' | 'is empty', 'is not empty' |
Conditions using 'is not', 'is none of' or 'does not contain' also match while the field they depend on is unanswered, and the summary under the field name says so.
How required fields work with conditions
People handling an Event only have to complete a field set to 'Required when shown' on the Events it appears on.
How to remove conditions from a field
Click 'Only show if' next to the field, remove each condition with the cross at the end of its row, then click 'Publish'. The field then appears on every Event at that stage again.
What people handling the Event see
The field appears on an Event as soon as its conditions match, and disappears if the answers change. Anything already entered in it is kept.
Related articles