Trigger binding dialog
When you create or edit a trigger binding, you specify information to define your trigger, such as template to filter. This information displays on the Trigger Bindings list page.
| Column | Description |
|---|---|
| Name | Text name for the binding. Names must be unique. |
| Marketing Operations Object | The type of object the trigger is defined for, such as project, request, marketing object, approvals, accounts, and invoices. The default is Any Marketing Operations Object. |
| Template | The template to use as a filter. After an object is selected, related templates are populated to allow users to specify trigger for a template. Your selection acts as a filter that applies to all instances of objects for that template. The default is Any Template, meaning either that all templates for the object are included, or that the object you chose has no templates. |
| Context | The context for the trigger. For example, the context can 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. You only see events that correspond to the selected object, template, and context, unless Any Event was selected for the object, in which case all events show. Typical events are Created, Updated, Status Changed, Member Assigned/Unassigned, and Objects Linked/Unlinked. |
| Deferred | The procedure runs sometime after the transaction is committed. If checked, the trigger runs after the configured action is completed; the trigger does not affect the operation on which the trigger is configured. This type of trigger is typically used for post-processing activities. |
| Validating | A validating trigger starts 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. If checked, the trigger runs just before completion of the configured action. Then, if the trigger returns failure, the action on which the trigger is configured rolls back and user receives errors that are reported by the trigger. This type of trigger is typically used for custom validations or any pre-processing activities. |
| Exclusive | If checked, the trigger procedure runs exclusively even if multiple trigger binding match the action that you selected. For example, if the trigger is not exclusive, whenever the user updates any workflow task, any trigger binding that is configured on the event "Project Updated" also runs. To prevent running multiple trigger bindings, select this check box. An exclusive trigger binding does not run with other procedures, even if multiple bindings match. If multiple exclusive bindings match, all the exclusive bindings run. If this box is cleared, the binding is inclusive. Inclusive bindings denote procedures that run with other procedures when the selection criteria for more than one trigger matches. If any matching procedure is exclusive, then only the exclusive matching procedure runs. Only the most specific exclusive bindings match. 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 that is bound to the trigger; that is, the procedure to run when the trigger fires. |