You are here:
Configure Safety Cloud Triggers
The Safety Cloud package comes with its own list of functionality managed by a trigger framework. You can extend the Safety Cloud triggers with additional functionality, as described here.
Required Editions
| Available in: Enterprise and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To modify trigger settings: | Modify All Data |
Safety Cloud trigger functionality exists in a custom metadata type called Trigger Settings. These custom metadata records point to units of custom Apex logic.
All Safety Cloud trigger settings are enabled by default except for the Send Marketing Cloud Emails setting. When you’re ready to send communications to event attendees, you can pair this setting with the Marketing Cloud Engagement email setup.
We don’t advise turning off any of the other trigger settings unless there’s a specific reason.
To access and modify Safety Cloud triggers, and to create your own triggers, complete these steps.
-
Access and work with Safety Cloud triggers.
- From Setup, in the Quick Find box, enter Custom Metadata Types, and then select Trigger Setting.
- Next to the custom field that you want to edit and update, click Edit .
- Save your changes.
-
Activate a Trigger Setting.
- Access the trigger setting that you want to activate.
- Set the Active checkbox to True.
- Save your changes.
To block users from changing the status of a Health Verification record, you must activate the Block Status Change trigger.
Note The Block Status Change is set to Active by default. - Optional:
Create your own Trigger Module Class.
- To create your own Trigger Module Class and deploy a new Trigger Setting, create a class that inherits the Safety Cloud TriggerModule interface.
- After you create the class, create a trigger setting record with the name of your class, and then set it to Active.
- You can use Table-Driven Trigger Management (TDTM) to create and deploy a new Trigger for Safety Cloud.
For information about TDTM, see Table-Driven Trigger Management (TDTM) Overview.
Implementation example for creating the class:
public with sharing class MyTriggerClass implements safetycloud.TriggerModule { public void run(List<Health_Verification__c> healthVerifications, Map<Id, Health_Verification__c> oldHealthVerificationsById) { if (Trigger.isBefore && Trigger.isUpdate) { runCustomLogic(healthVerifications, oldHealthVerificationsById); } } private void runCustomLogic(List<safetycloud__Health_Verification__c> healthVerifications, Map<Id, safetycloud__Health_Verification__c> oldHealthVerificationsById) { //TODO: custom logic } }Accompanying Trigger Setting example:
<?xml version="1.0" encoding="UTF-8"?> <CustomMetadata xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <label>My Custom Trigger</label> <protected>false</protected> <values> <field>Active__c</field> <value xsi:type="xsd:boolean">false</value> </values> <values> <field>Class__c</field> <value xsi:type="xsd:string">MyTriggerClass</value> </values> <values> <field>Order__c</field> <value xsi:type="xsd:double">1.0</value> </values> </CustomMetadata>
Additional Key Trigger Settings
Person Accounts: Each person account has its own external Id. All Health Verifications are linked to a person account.
Set QR Code Logic:This setting sets the QR Code checkbox and date logic. You can disable this trigger setting and create your own QR code logic to suit your needs.
