Configuring Database Triggers

This topic describes how to configure the Generate Triggers server component. You can configure this server component from the Siebel client or from the command line. The Siebel client and the command line use the same parameters.

Caution: If you incorrectly define a Workflow Policy condition, then running Generate Triggers can result in an invalid database trigger. An invalid database trigger can prevent Siebel CRM from processing normal user transactions. It is recommended that you thoroughly test your Workflow Policies in a test environment before you migrate them to a production environment.

To configure database triggers

  1. Navigate to the Administration - Server Management screen, then the Jobs view.

  2. In the Jobs list, create a new record.

  3. In the drop-down list for the Component/Job field, choose Generate Triggers.

  4. In the Job Parameters list, click New to modify component-specific parameters, using values from the following table.

    Name Value Description

    Remove

    TRUE or FALSE (default)

    Set to TRUE to create DROP TRIGGER statements to clean up the database triggers. Remove does not create CREATE TRIGGER statements.

    Trigger File Name

    Valid filename on the Siebel Server

    Defines the name and output location for the SQL script file. The default value is TRIGGER.SQL. Siebel CRM creates this file and then places it in the root directory of the Siebel Server during installation.

    EXEC

    TRUE or FALSE

    Set to TRUE to run the SQL script file automatically. Set to FALSE to run the SQL script manually. For more information, see Using the EXEC Parameter.

    Mode

    ALL, WORK, or ASGN

    Select one of the following values:

    • ALL. Creates database triggers for Workflow Policies and Assignment Manager.

    • WORK. Creates database triggers only for Workflow Policies.

    • ASGN. Creates database triggers only for Assignment Manager.

    Privileged User Name and Privileged User Password

    Assigned Privileged User name and password

    To make sure the user enters a Privileged User name and password, you can define the username and password. Siebel CRM considers the Table Owner (Oracle/DB2) or Database Owner (MSSQL) as a Privileged User. You can enter the Table Owner or Database Owner username and password in the Privileged User name and password fields.

    For a description of generic and enterprise parameters, see Siebel System Administration Guide

  5. Enter the Privileged User (Table or Database Owner) username and password.

  6. In the Job Detail form, choose the applet-level menu, and then choose Start Job.

  7. To view changes to the state, choose the applet-level menu, and then click Run Query to refresh the screen.

    The Status field contains Success or Error after Siebel CRM refreshes the screen. You can view the log details.

  8. If EXEC equals FALSE, then you must manually run the SQL script file.

    For more information, see Manually Running the SQL Script File.