Siebel Business Process Designer Administration Guide > Workflow Policies > About Testing Workflow Policies >
Testing New Policies and Monitoring the Results
You need to test your new workflow policies by entering data that meets all the workflow policy conditions you defined in the policy. Test each of the newly defined workflow policies, workflow policy conditions, and workflow policy actions to verify that:
- The policies, conditions, and actions are correctly defined
- The policies, conditions, and actions accurately define the transactions (the correct columns) you want to monitor
- The actions are what you want and occur when you want them
- The action interval and sleep times are correctly defined
Correctly testing your workflow policies and eliminating any problems are critical before implementing the policies in your production environment.
Make sure your database triggers are created, the email and pager server processes are running, and your Workflow Agent processes are running before you test and monitor the new policies.
You verify your action by checking to see if the proper action occurs. That is, you can check that the email arrives or the pager goes off. You can monitor Workflow Agent progress using the Workflow Policies Log view.
The Workflow Policy Log view displays a log of all the records that meet a policy condition tracked by the Workflow Monitor Agent process. You access the Workflow Policy Log view from the Siebel client.
The view contains the following fields:
- Policy. The name of the policy.
- Workflow Object. The name of the workflow policy object.
- Object Identifier. The ID of the workflow policy object for which the policy condition was met.
- Object Values. Identifying information for the row that met the policy condition.
- Event Date/Time. The date and time the policy condition was met.
Once you have verified that the workflow policies work as expected, you can migrate the workflow policies to your production environment.