Triggers are used to automatically create and assign corrective actions. Think of a trigger as a rule or business logic that a newly collected inspection is evaluated against to determine if a new corrective action is necessary.
A trigger consists of three core components and can include automated assignments and a completion window if Hierarchy-Based Access Control (HBAC) is enabled.
The three core components are:
- Inspection Type: A trigger is applied to a specific inspection type, like a routine, reinspection, or complaint inspection.
- Inspection Attribute: This specifies what a trigger should look at to determine if a corrective action should be created. Triggers can currently evaluate by the number of critical violations, total number of violations, or Hazel Score.
- Thresholds: These are set for each attribute by the user, and determine when a corrective action is created. For example, you could set a threshold of greater than 3 critical violations or a Hazel Score of less than 50.