Bookshelf v7.5: Running Generate Triggers

Siebel Business Process Designer Administration Guide > Workflow Policies Server Administration > Creating Database Triggers >

Running Generate Triggers

When running Generate Triggers, remember the following tips, especially if you are deleting a policy:

Deleting a policy and then running Generate Triggers does not remove the database trigger. When you delete a policy, you must run Generate Triggers with the remove parameter set to TRUE. This removes all triggers. You must then rerun Generate Triggers to reset the triggers for existing policies.

You need to stop and restart the Workflow Monitor Agents when running Generate Triggers.

Generate Triggers needs to be rerun whenever you change policy conditions. Generate Triggers does not need to be rerun when changing policy actions.

For SQL Server, you should have your default database set correctly. To determine your default database, launch the SQL Server Enterprise Manager and navigate to the SQL Server Machine name. Then, click Security and then click LOGIN. The default database will be listed to the right.

To generate triggers using the GUI

In the Siebel Client, select View > Site Map > Server Administration > Enterprise Operations > Component Requests.

Click New.

Select Generate Triggers from the Component Job list. This creates a new line entry but does not start the task.

Click New in the Component Request Parameter Applet to modify parameter settings. The component-specific parameters for Generate Triggers are in Table 79. See Siebel Server Administration Guide for a description of the generic and enterprise parameters.

Enter your Privileged User name and password.

Click the Component Request form applet menu, then select Submit Request.

To view changes to the state, refresh the screen by clicking Run Query from the applet menu.

Upon completion, the Status field contains either Success or Error. It is recommended that you view the log details. To do this, click Screen Enterprise Operations. In the Show field, select Tasks, then click the view tab called Task Info Log.

Table 79. Component-Specific Parameters for Generate Triggers
Name	Value	Description
Remove	TRUE or FALSE (default)	Set to TRUE to generate "DROP TRIGGER" statements to clean up the triggers. Remove does not generate "CREATE TRIGGER" statements.
Trigger File Name	Valid file name on the Siebel Server	Name and output location for the SQL script file. The default is TRIGGER.SQL. The file is created in the root directory of the Siebel Server during installation.
EXEC	TRUE or FALSE (default)	Determines if the SQL script file runs automatically or manually. If TRUE, the SQL script file runs automatically. EXEC should be set to FALSE if you are running a Sybase server (all Siebel versions) or MS_SQL server (Siebel versions 4.x). This is to prevent connected users from getting an error message when Siebel generates database triggers. You should make sure that no one is logged into the database before you generate triggers. Also, if you are creating a large number of triggers because there are too many workflow policies, the triggers should be applied by the user and not by the Generate Triggers server process. The Exec parameter should be set to FALSE in this case.
Mode	ALL or WORK or ASGN	Set to ALL to create both Workflow Policy triggers and Assignment Manager triggers. Set to WORK to create only Workflow Policy triggers. Set to ASGN to create only Assignment Manager triggers.
Privileged User Name/Privileged User Password	Assigned Privileged User name and password	All users must enter a Privileged User name and password. The Table Owner is considered a Privileged User, so you may enter the Table Owner name and password in the Privileged User name and password fields.