Siebel Clinical Trial Management System Guide > Setting Up Siebel Clinical >

Activating Workflow Policies for Siebel Clinical

This system administration task describes how to activate the workflows and workflow policies required for Siebel Clinical. For a full list of workflows provided for Siebel Clinical, see Table 26.

To activate the workflow policies for Siebel Clinical

1. Navigate to the Administration - Business Process screen, then the Workflow Deployment view.
2. Query for all the workflows using the following criteria, and activate the workflows:
   • Clinical*
   • LS Clinical*
3. Verify that each activated workflow is added to the Active Workflow Processes list view at the bottom of the screen.
4. Navigate to the Administration - Runtime Events screen, click the cogwheel icon, and select Reload Runtime Events.
5. Navigate to the Administration - Business Process screen, then the Workflow Policies view, and perform the following steps:
   1. Query workflow policies for LS Clinical*
   2. Set the activation date to one day before today's date for all policies.
   3. Check that expiration date is NULL for all policies.
6. Navigate to the Administration - Server Management screen, then the Jobs view, and generate triggers for the workflow policies returned from your query as follows:
   1. Define a job for Generate Triggers component with the following parameters:

      EXEC: True

      Mode: ALL

      Privileged User: <%SADMIN%>

      Privileged User Password: <%PASSWORD%>

   2. Start the job and query until the status is Success.
7. From the srvrmgr command utility, create a component definition for the policy group LS Clinical Rollup as follows:

   Component definition: LSCLIN

   Component type: WorkMon

   Component group: Workflow

   Run mode: Background

   Full name: LS Clinical

   Description: Monitors LS Clinical Workflow Manager events

   Parameter DfltTasks=1, GroupName=LS Clinical Rollup, SleepTime=30

   NOTE:  When working with component definition commands, launch and run the srvrmgr program for the enterprise; that is, do not start srvrmgr with the back slashes (/s) (or -s for UNIX).

   The component alias must be unique across the enterprise, and must not be more than 30 characters in length. Also be careful not to use keywords in the component description, such as for or component, unless they are enclosed in quotes.

   The component definition command starts a task to perform actions on LS Clinical Rollup group policy as a result of updates on the corresponding tables monitored by the database triggers.

   The SleepTime parameter represents the time in seconds for processing requests.

   The default value is 20 seconds. Setting the SleepTime user property to a low value or zero can have serious negative performance consequences.

8. Enter the following in the srvrmgr command utility to enable the LS Clinical Rollup component:

   enable component definition LSCLIN

9. From the srvrmgr command utility, create a component definition for the LS Clinical Trip Report policy group as follows:

   Component definition: LSCLIN_TRIP

   Component type: WorkMon

   Component group: Workflow

   Run mode: Background

   Full name: LS ClinicalTrip Report

   Description: Monitors LS Clinical Trip Report Workflow Manager events

   Parameter DfltTasks=1, GroupName=LS Clinical Trip Report, SleepTime=30

   The component definition command starts a task to perform actions on LS Clinical Trip Report group policy as a result of updates on the corresponding tables monitored by the database triggers.

10. Enter the following in the srvrmgr command utility to enable the LS Clinical Trip Report component:

    enable component definition LSCLIN_TRIP

11. Navigate to the Administration - Server Configuration screen, then the Synchronize view and click Synchronize.
12. Check that the Workflow Monitor Agent is running.

    If it is not activated, then start the Workflow Monitor Agent task again.

13. Navigate to the Administration - Server Management screen, then the Tasks view.
14. Navigate to the Parameters view.
15. In the Tasks list, query for the Workflow Monitor Agent in the Component Field.
16. In the Task Parameters list, query for Action Interval in the Parameter field and set the value to 10.