Siebel Business Process Designer Administration Guide > Workflow Policies > About Workflow Policies Server Administration >

Creating Database Triggers

The Generate Trigger (GenTrig) component on the Siebel Server allows you to create database triggers. Workflow Policies uses database triggers to identify which records match policy conditions. Run Generate Triggers when you:

• Create or delete new policies (including Assignment Policies), with the exception of Workflow Policies that have Batch Flag set to TRUE.
• Amend policy conditions or policy criteria.
• Change activation or expiration dates of policies, including Assignment Policies.

To run Generate Triggers, you must have installed Siebel Server, and the client you are using must be enabled to access the Siebel Server Administration screens. See the installation guide for the operating system you are using for more information on installing Server Manager.

CAUTION:  If you have incorrectly defined a policy condition, running Generate Triggers may result in invalid triggers. An invalid trigger can prevent execution of normal user transactions. For this reason, thoroughly test your policies in your test environment before you deploy them in your production system.

Generating triggers is a one- or two-step process, depending on how the EXEC parameter is set; the default setting is FALSE.

• If the EXEC parameter is set to TRUE, the Generate Trigger component automatically creates the SQL script and applies it to the server database.
• If the EXEC parameter is set to FALSE, generating triggers is a two-step process:
  • Use the Generate Triggers component from a Siebel Server to create the SQL script file, which is placed in the root directory of the Siebel Server installation.
  • Use your database vendor's SQL tool to execute the SQL script file against the server database.

You can run the Generate Triggers component from either the Server Manager graphical user interface (GUI) or command line mode. Both the GUI and the command line use the same parameters.

So the triggers are only there to create indicators for the Workflow engine check the policies conditions.