Triggers

Triggers can perform powerful custom validations and both pre- and post-event processing. Use triggers to integrate the out-of-box processing capabilities of HCL® Marketing Operations with custom business processes.

You can set up triggers so that events related to certain objects cause execution of a procedure. When such event occurs, Marketing Operations Procedure Manager runs the trigger.

For example, you want to insert data into a database whenever the state of a particular project changes from draft to active. To use a trigger to do insert data, you define the following.

• A procedure to insert a record into an external database table.
• A project template named DirectMail.
• A trigger binding for the DirectMail template, set to run when the state of a project changes, for example, from draft to active.

For projects that are based on the DirectMail template, the system calls the procedure when the specified state change occurs.

The following trigger rules apply:

• Triggers occur before or after an event.
• Triggers run on a subset of system events 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.