Siebel Business Process Framework: Workflow Guide > Administering Workflow Policies > About Testing, Troubleshooting and Migrating a Workflow Policy >

Troubleshooting a Workflow Policy

Because a workflow policy is based on database triggers, a workflow policy can take effect on a database record only after the record is committed. If you have a policy that is based on multiple database tables, the policy takes effect only if the records on those tables are committed.

For example, Opportunity Revenue is stored in the S_OPTY_POSTN table, and lead quality is stored in the S_OPTY table. A policy with conditions Opportunity Revenue > 10M and Lead Quality is High takes effect only when the records are committed on both tables.

Also keep in mind that multiple business components can be created for the same database table using search specifications. If you are creating a workflow policy component to monitor a business component, be sure to include the fields that are being used in search specifications as workflow policy columns. The workflow policy column can then be used in the policy conditions to allow appropriate behavior to be enforced.

Troubleshooting a Workflow Policy That Does Not Trigger

You can troubleshooting a workflow policy action that does not trigger.

To troubleshoot a workflow policy action that does not trigger

1. Make sure your test record meets your workflow policy conditions.
2. Make sure the Siebel client configuration file is pointing to the correct enterprise server.

   One error that can occur if the server is incorrect is ESC-00053, Error loading rule definitions.

3. Check the workflow policy activation date/time.
4. Check the monitor task:
   1. Check to see if the monitor is awake and running against the correct group.
   2. Search the Task Information log for the ROW_ID of your test record:
      • If ROW_ID does not exist, run GENERATE TRIGGERS.
      • Update your test record.
5. Check the Action Agent task:
   1. Check to see if the Action Agent is awake and running against the correct workflow policy group.
   2. Search the Task Information log for the ROW_ID of the test record.
6. Make sure your triggers are generated.

Tracing a Workflow Policy

Workflow Policies uses the General Events event for logging. To view informational messages, set the log level to 3. To view debugging information, set the log level to 4. For more information, see Tracing and Reporting a Workflow Policy.