Triggers

Triggers are a way to build notifications, pages and such based on activity inside of the CAD. An example would be a popup message to remind communication specialists about specific operations required when bringing a patient to a specific hospital. There are many options for building Triggers, here are some supporting documents you may find helpful:

https://flightvector.atlassian.net/servicedesk/customer/portal/6/article/1076003047?src=-1494079992

https://flightvector.atlassian.net/servicedesk/customer/portal/6/article/1816231966?src=1853676418

*Note: a lot of these options are new in 6.9.0.0, if you don’t see the options, you are looking for, check your version.

Instructions

1. Go to Settings → Triggers

2. There are several events that will initiate a Trigger, you will see those options in the ‘Event' list. An easy way to think of this, every time “xyz” event occurs, this trigger will be initiated. Example would be if you select, ‘Commit request initially’ then every time a new request is started and the ‘Save and Continue’ or the ‘OK’ button is selected, for the first time, this trigger will be initiated. The same goes for all of the other options listed below.  For a list of definitions of all the 'Events’ see article here: https://flightvector.atlassian.net/servicedesk/customer/portal/6/article/1076003047?src=-1494079992

3. The ‘Conditions' are where you define the parameters that need to be met, when this ‘Event’ takes place, for the ‘Trigger’ to initiate. Perhaps it will only initiate when a patient is on board and landing at a specific hospital. This ‘Condition’ will be in the form of SQL (or new Condition Builder in 6.9.0.0) defining what conditions are searched for when the ‘Event’ occurs in the CAD. For instructions on using the ‘Condition Builder’, only available starting in 6.9.0.0, see the following documentation: https://flightvector.atlassian.net/servicedesk/customer/portal/6/article/1863090197?src=992303426 If you are on an older version, this documentation could help you build your conditions, 'Edit Display Filters’: https://flightvector.atlassian.net/servicedesk/customer/portal/6/article/2179235911?src=1449039625

4. The final part of setting up a ‘Trigger’ requires you to decide what ‘Action’ you want to occur should your ‘Conditions’ be met. Below you will see a list of these options in the “Add Action” portion of the ‘Trigger’.

a. After you select the ‘Action’ that you are going to use, you may need to add a message. Follow the image below. (*This is a new image that is only present starting in 6.9.0.0)

b. Make sure that after you add your ‘Action’, that you select ‘Add’ as shown below. If you don’t do this and save your ‘Trigger’, the ‘Action’ will not be added, and you will have to re-add it.

5. After you have your ‘Trigger’ all setup, you may decide that you want it to be delayed for a set time before the ‘Action’ takes place. You can do that by setting a delay as shown below.