Triggers

You can set up triggers so that events related to certain objects cause execution of a procedure.

Assume you want to insert data into a database whenever the state of a particular project changes from draft to active. You can use a trigger to do this by defining the following:

A procedure to insert a record into an external database table

A project template, DirectMail

A trigger binding for the DirectMail template, set to fire when the state of a project changes (for example from draft to active).

If you create a project based on the DirectMail template, the system calls the procedure when the specified state change occurs.

The following trigger rules apply:

Triggers occur just before or just after an event.

Triggers are executed on a subset of system events, including those involving projects, requests, marketing objects, approvals, tasks, workflow spreadsheets, grid rows, users, invoices, budgets, accounts, and resources.

In general, define triggers at the most granular level possible. For example, rather than setting a trigger binding for any object, configure a trigger binding for a particular event for a particular project template.

You can view the list of trigger bindings for your installation by selecting Settings > Marketing Operations Settings and clicking Trigger Bindings.