Siebel CRM Siebel Clinical Trial Management System Guide Siebel Innovation Pack 2016 E52416-01 |
|
Previous |
Next |
View PDF |
Table A-5 lists the system preferences that you can use to configure core functionality in Siebel Clinical Trial Management System and to integrate Siebel Clinical Trial Management System with third-party applications.
Table A-5 System Preferences in Siebel Clinical
System Preference | Functionality |
---|---|
CL - BudgetingApp CustomerCode |
For more information, see Chapter 12, "Setting Up and Configuring Clinical Operations Integration." |
CL - BudgetingApp RequestURL |
For more information, see Chapter 12, "Setting Up and Configuring Clinical Operations Integration." |
CL Highest Preference SDV Rule |
This setting determines the priority order in which to implement the 3 methods (Manual, Site, and Status) to change the SDV Required field of a subject record. Valid values for this system preference are Status and Manual. The default value is Status. To understand the priority order for each value in this system preference, note the following scenario:
If you set this system preference to Status, then the 3 methods are implemented in the following priority order: Status, Manual, and Site. Note the following:
If you set this system preference to Manual, then the 3 methods are implemented in the following order: Manual, Status, and Site. Note the following:
|
CL – Verify TripReportApprover |
This setting turns on or off approver verification for trip reports. When enabled, the User Verification screen is launched during the approval process for trip reports to verify the user login credentials of the approver. To enable approver verification for trip reports, set the value to Y. The value is set to N by default. |
Clinical_Training_Commit_Freq |
This setting determines how frequently updated site records are saved in the Siebel database when you run the batch job to publish training plans and associate training topics with the site records. The default value for this system preference is 10. This value indicates that each time 10 site records are updated in the batch job those site records are saved in the Siebel database. If the value for this system preference is 10, if 92 site records must be updated in the batch job, and if a failure occurs during the job run, then the result of the batch job is that the number of site records saved to the Siebel database is a multiple of 10 (for example, 60 site records), and not 0 site records. If you run the batch job again, then only the remaining 32 updated site records are saved in the Siebel database. |