Re: Anyone using Triggers to enforce data validation & business rules?

On 9/23/2014 2:20 PM, Nathan Andelin wrote:

I believe the manual states that up to 300 Triggers can be configured per
File. The call order is *Before Triggers, then Constraints, then *After
Triggers.

In regard to business logic / validation in a trigger, if the design
were to have one before trigger for each business rule in a table, then
the first trigger to send an escape message will short circuit the rest
of the validations. If TRIGGER1 fails the validation, TRIGGER2 and
TRIGGER3 will not run. If a given transaction has multiple errors,
you'd only know about one at a time.

If the design were to put all the validation for a given table into a
single trigger then the trigger could send multiple diagnostic messages
before escaping out, thus informing the application of all of the
validation failures at once.

Under the Trigger Mediator concept, all calls are made to just one program
(the Mediator) which implements utility type plumbing then calls a Trigger
Handler which is specific to the File-Event in question.

Which could be for before or after triggers or both.
--buck