Activating Workflow Policies for Siebel Clinical

This system administration task describes how to activate the workflows and workflow policies required for Siebel Clinical. Table A-6, "Workflows in Siebel Clinical" shows a list of workflows for Siebel Clinical.

To activate the workflow policies for Siebel Clinical  

1. Navigate to the Administration - Business Process screen, then the Workflow Deployment view, and perform the following steps:

   1. Query for all the workflows using the following criteria, and activate the workflows:

      • *Clinical*

      • SWI - Protocol*

   2. Verify that each activated workflow is added to the Active Workflow Processes list view at the end of the screen.

2. Navigate to the Administration - Runtime Events screen, click Menu (the cogwheel icon), and select Reload Runtime Events.

3. 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.

4. Navigate to the Administration - Server Management screen, then the Jobs view, and perform the following steps to generate triggers for the workflow policies returned from your query:

   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.

5. From the srvrmgr command utility, perform the following steps:

   1. Create a component definition for the LS Clinical Rollup policy group 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 the words 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 that the database triggers monitor.

      The SleepTime parameter represents the time in seconds for processing requests. The default value is 20 seconds. Setting the SleepTime parameter to a low value or zero can have serious negative performance consequences.

   2. Enter the following command to enable the LS Clinical Rollup component:

      enable component definition LSCLIN

6. Navigate to the Administration - Server Configuration screen, then the Synchronize view, and perform the following steps:

   1. Click Synchronize.

   2. Verify that the Workflow Monitor Agent is running.

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

7. Navigate to the Administration - Server Management screen, then the Tasks view, and perform the following steps to set the action interval for the Workflow Monitor Agent task:

   1. Navigate to the Parameters view.

   2. In the Tasks list, query for the Workflow Monitor Agent in the Component field.

   3. In the Task Parameters list, query for Action Interval in the Parameter field and set the value to 10.