Add new page for Foundations Pluggable Triggers

[mellisoncertinia]

The Winter '23 release of the Certinia Foundations package added a 'Pluggable Trigger' framework. We want to provide additional documentation to support its use.

[rcorfieldffdc]

Sounds good. Are these versioned, so a customer sees which version the text applies to?

…

On Thu, 13 Jun 2024 at 14:51, Martyn Ellison ***@***.***> wrote: ***Non-Certinia Sender**------------------------------* ***@***.**** commented on this pull request. ------------------------------ In pluggable-triggers.md <#1 (comment)> : > + when BEFORE_DELETE, AFTER_DELETE { + records = Trigger.old; + } + when else { + records = Trigger.new; + } + } + + + try { + fferpcore.PluggableTrigger target = + new fferpcore.PluggableTrigger.Constructor() + .construct(records); + + + switch on Trigger.operationType { That's a good point. I think with the new runTriggerHandler() method we can greatly simplify the Apex trigger code snippet provided here. Are you happy if I update this on/after Summer '24 ERD? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKIBRMF7JGKNS7UUE3SBXLLZHGPWZAVCNFSM6AAAAABJED3ADSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMJVHA3TEMBTHE> . You are receiving this because your review was requested.Message ID: ***@***.***>

[mellisoncertinia]

Sounds good. Are these versioned, so a customer sees which version the text applies to?
…
On Thu, 13 Jun 2024 at 14:51, Martyn Ellison @.> wrote: Non-Certinia Sender------------------------------ @.* commented on this pull request. ------------------------------ In pluggable-triggers.md <#1 (comment)> : > + when BEFORE_DELETE, AFTER_DELETE { + records = Trigger.old; + } + when else { + records = Trigger.new; + } + } + + + try { + fferpcore.PluggableTrigger target = + new fferpcore.PluggableTrigger.Constructor() + .construct(records); + + + switch on Trigger.operationType { That's a good point. I think with the new runTriggerHandler() method we can greatly simplify the Apex trigger code snippet provided here. Are you happy if I update this on/after Summer '24 ERD? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKIBRMF7JGKNS7UUE3SBXLLZHGPWZAVCNFSM6AAAAABJED3ADSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMJVHA3TEMBTHE . You are receiving this because your review was requested.Message ID: @.***>

The developers site isn't versioned so the documentation targets the most recent FDN package. I've add a sentence to make this clear. I don't expect the pluggable trigger framework to change much so hopefully we won't need versioning. From Summer '24 the products using the framework will publish details of their pluggable triggers in the technical pack (which is versioned). We'll be able to remove the 'Existing Pluggable Triggers' table and direct everyone to the technical pack.