Supported Objects

Out of the box, Seven20 includes packaged trigger actions for the following standard objects:

• Account
• Contact
• ContentVersion
• EmailMessage
• Event
• User

All Seven20 custom objects include a packaged trigger action by default.

Adding new custom objects

The trigger framework supports any triggerable object, however for standard and org specific custom objects, an Apex Trigger needs to be created to enable support. Use the following boilerplate code, updating the SObject value as required:

trigger ObjectTrigger on SObjectType(
    before insert,
    before update,
    before delete,
    after insert,
    after update,
    after delete,
    after undelete
) {
    seven20.TriggerHandler.runTrigger(
        Trigger.old,
        Trigger.new,
        Trigger.oldMap,
        Trigger.newMap,
        Trigger.operationType
    );
}

If an object does not support all trigger contexts, e.g. a Platform Event, the unsupported contexts must be omitted from the trigger definition.

tip

Following the naming scheme of ObjectTrigger is recommended, e.g. AccountTrigger or CustomObjectTrigger.

info

If an object is supported by triggers, but not selectable as an option in either the Trigger Object or Trigger Object (Special) fields, please reach out to support to request it is added as a Trigger Object (Special) option.