global with sharing class PluggableTriggerApi

Provides interfaces that can be used to create plugins to be executed during the trigger of objects shared between multiple packages. Unlike creating multiple triggers, multiple plugins will always be called in a defined order.
To set up a plugin, create a fferpcore__Plugin__mdt record with a fferpcore__ExtensionPoint__c of PluggableTriggerApi.PluginConstructor, a fferpcore__ClassName__c that matches an Apex class that extends that interface, and a fferpcore__AdditionalData__c of the sObject name. Plugins are called in order of the fferpcore__PluginNumber__c field, which should be set to 1 or higher.

Sample Code

//Note: This sample code is for demonstration purposes only. It is not intended for
//use in a production environment, is not guaranteed against defects or errors, and
//is in no way optimized or streamlined.

global class BillingDocumentTriggerPluginConstructor implements fferpcore.PluggableTriggerApi.PluginConstructor
{
    global Schema.SObjectType sObjectType()
    {
        //This plugin will only be used for Billing Documents.
        return fferpcore__BillingDocument__c.SObjectType;
    }

    global PluggableTriggerApi.Plugin construct(List<SObject> objects, PluggableTriggerApi.Context triggerContext)
    {
        return new BillingDocumentTriggerPlugin(objects);
    }
}

/**
 * An example plugin class that would block billing documents from being deleted.
 */
global class BillingDocumentTriggerPlugin implements fferpcore.PluggableTriggerApi.Plugin
{
    private final List<SObject> m_records;
    public BillingDocumentTriggerPlugin(List<SObject> records)
    {
        m_records = records;
    }

    global void onBeforeInsert() {}

    global void onBeforeUpdate(Map<Id,SObject> existingRecords) {}

    global void onBeforeDelete() {}

    global void onAfterInsert() {}

    global void onAfterUpdate(Map<Id,SObject> existingRecords) {}

    global void onAfterDelete()
    {
        for (SObject record : m_records)
        {
            record.addError('Cannot delete billing documents');
        }
    }

    global void onAfterUndelete() {}
}

global interface Plugin

Interface that plugins should extend. The objects being processed by the trigger should be stored on instances extending this interface.

Methods

global interface PluginConstructor

Constructs a plugin during a particular trigger execution. This is responsible for deciding whether a plugin is appropriate to the current trigger, and passing trigger context to the plugin being created.

Methods

global virtual with sharing class Context

Additional information regarding the trigger context that the plugin is being called in. Currently unused, but in place for later expansion.