If you’ve developed more than a handful of triggers, you already know trigger development is simple, until it is not. Sure, creating that first quick trigger on the Lead object to set the LeadScore was pretty painless. But what happens when you have 5, 50, or even 100 triggers? Without a solid trigger architecture, those simple triggers quickly become a nightmare. You’ll spend more time hunting down order of operation issues, managing governor limits, and/or debugging trigger recursion than it took to originally develop the code. This is why establishing a solid trigger architecture is key. It should be established prior to any trigger development.
What is a Trigger Architecture?
A trigger architecture is a framework (also commonly referred to as pattern, template, foundation, and/or factory) for how triggers are organized and executed within an instance.
A good architecture will be based on the following principles:
The Gears Trigger Architecture delivers a solid trigger architecture base via a managed package installation. The package reduces the overall trigger footprint (down to a single line of code) and exposes trigger functionality via configuration.