Siebel Business Process Framework: Workflow Guide > Administering a Workflow Process > Monitoring a Workflow Process >

Setting Monitoring Levels for a Workflow Process

The monitoring level you set determines the frequency that Siebel CRM uses to log data and the data that the views display for a workflow process instance. For more information, see Stopping a Workflow Process Instance and Removing a Workflow Process from the Run-Time Environment.

Monitoring Workflow Process Instances

The Workflow Instance Monitor view allows you to monitor workflow process instances, step instances, and aggregate data.

To monitor instances of a workflow process

1. Log in to the Siebel client.
2. Navigate to the Administration-Business Process screen, and then the Workflow Instance Monitor view.
3. In the Workflow Process list, query the Name field for the workflow process you must monitor.
4. Monitor the workflow process, using values from the following table.

   List Name or View Tab	Description
   Workflow Process	Displays definitions of workflow processes that have monitoring turned on. A workflow process with a Monitoring Level that is not set to NONE is turned on. For more information, see Monitoring Level.
   Process Instances	Displays the related log instances for the workflow process that you choose.
   Step Instances	Displays the steps and process properties for the workflow process that you choose.
   Aggregate Data	Displays aggregate data as a chart view for the workflow process that you choose.

   For more information, see Removing a Workflow Process from the Log File and Using Instance Monitoring to Diagnose a Workflow Process.

Monitoring Level

If the Monitoring level is set for a deployed workflow process, then the workflow process instance remains in the Workflow Instance Monitor view after it finishes and Siebel CRM no longer displays it in the Workflow Instance Admin view. Siebel CRM might not display any records in the Step Instances or Aggregate Data views, depending on the monitoring level that is set for the workflow process you choose.

Setting the Monitoring Level Parameter

When Siebel CRM creates a workflow process instance, it reads the monitoring level from the workflow process. This level remains constant throughout the lifetime of the instance unless Siebel CRM pauses it. If Siebel CRM pauses an instance, then it rereads the monitor level from the workflow process when it resumes this instance.

Table 29 describes parameters for monitoring levels and their corresponding frequencies for log writing that you can set for a workflow process.

To set the monitoring level parameter

1. In the Siebel client, navigate to the Administration-Business Process screen, and then the Workflow Deployment view.
2. In the Active Workflow Processes list, set the Monitoring Level field.

Guidelines for Setting the Monitoring Level

The monitoring level determines how frequently Siebel CRM writes data to the disk. The run-time environment for Siebel Workflow sets this frequency according to the type of workflow process and to the monitoring level you choose. Monitoring can cause a performance overhead. It is recommended that you set the monitoring level to one of the following values:

• 0 (None) or 1 (Status) for a workflow process that Siebel CRM runs in a production environment.
• 2 (Progress) or higher only to debug a workflow process. If you set the monitoring level to Debug, then Siebel CRM writes the log to the disk after every workflow process step.

Monitoring Level and Compatibility with the 7.0 Workflow Process

Siebel CRM sets monitoring levels for a 7.0 flow workflow process according to the following value of the persistence frequency:

• NONE. Siebel CRM sets the monitoring level to NONE.
• ON_PAUSE or EVERY_STEP. Siebel CRM turns persistence on and sets the monitoring level according to the following value of the persistence level:
  • ALL_STEPS. Siebel CRM sets the monitoring level to PROGRESS.
  • CURRENT_STATE. Siebel CRM sets the monitoring level to STATUS.

Beginning with the Siebel CRM 8.1 release, persistence and monitoring are separate features that serve different purposes. Persistence affects quality of service and is controlled during development. Monitoring is an administrative tool and is controlled during deployment. Monitoring typically does not affect the functionality of a workflow process.