Trigger bindings details

When you create a trigger binding, you specify the following information. This information is then displayed in the Triggers table.

Column	Description
Name	Text name for the binding. Names must be unique.
Marketing Operations Object	The object the trigger is defined for. The default is Any Marketing Operations Object.
Template	The template to use as a filter. The template provided is a filter that applies to all instances of objects for that template. Projects are objects that have templates. So specifying a filter criterion that restricts the search to a specific template. The default for this criterion is Any Template, meaning either that all templates for the object are included in the filter, or that the object specified does not have templates to consider.
Context	The context for the trigger. For example, the context could be a task or workflow. A default of Any means that any context is considered for the filter criterion.
Event	An event for the filter operation. Only events that correspond to the selected object, template, and context are displayed, unless Any Event was selected for the object, in which case all events are displayed.
Deferred	The procedure runs sometime after the transaction is committed. The transaction that enclosed the trigger it not present in the procedure context. The procedure is provided a separate transaction context.
Validating	A validating trigger invokes a procedure to validate data before the current transaction is committed. The trigger sets up the procedure call with an enclosing context, which contains the database transaction.
Exclusive	Exclusive bindings denote a procedure that may not be executed with other procedures, even if multiple bindings match. (If multiple exclusive bindings match, all the exclusive bindings are executed.) If this box is not checked, the binding is inclusive. Inclusive bindings denote procedures that will be executed with other procedures if more than one trigger's selection criterion matches. If any matching procedure is exclusive, then only an exclusive matching procedure will be executed. Only the most specific exclusive bindings match. So, for example if you have three exclusive triggers, a global one, one on all projects, and one on a particular project template, then if the event fired matches all three, only the one for the particular project template runs.
Procedure	The procedure bound to the trigger; that is, the procedure to execute when the trigger fires.