Is it logical that the essense of triggers, that after initializing and before execution, they would validate and derive their business rule script based on a lookup query that is contained in another object?
So, rather than initially fire & do it's stuff the trigger first must check a few global then granular conditons and/or perhaps call an overall method that says, validate me, which both checks if the current conditions. For example, on data inport objects that are populated should not have certain business rule triggers execute in favor of a data scrubbing routine. Also a global value checks if the trigger active or not, and may even return its core business rules and conditional logic.
This may be able to better facilitate the expanding scope of business rules.
...psuedo snipit...
tr_01{
if new(i)
a = new(i) oA
b = new(i) oB
// Validate does a lookup returns bool IsValid and sBr or similar Error msg/code
call oTr = Validate_Trigger ("tr_01", a, b)as object
if oTr IsValid....
// sBr is a business rule script dynamically rendered based on Validate...
