Siebel Life Sciences Guide > Information for Siebel Application Developers > Business Component User Properties >
Specific Business Component User Properties
The following business component user properties are specific to a particular C++ class. This means that the properties are valid only for business components that are based on the C++ class implementing the user property or any of the related derived C++ classes.
Group 1 Business Components
Table 30 lists the user properties that are related to the following business components:
- Action (class CSSBCActivity)
- Calendar (class CSSBCCalendar)
Table 30. User Properties Related to Group 1 Business Components
User Property Name
|
User Property Value
|
Description
|
Read-only Activity Types
|
,ActivityType1,Activity Type2,...,
Value must start and end with a comma, and no spaces between values.
Example:
,Attendee Call,Meeting Invitee,
|
Tells the business component which activity types are to be read-only at the record level. Activity Type is the field category.
|
Read-only Fields for 'Activity Type'
Activity Type is the category value.
Example:
Read-only Fields for 'Account Call'
|
,field1,field2,...,
Value must start and end with a comma, and no spaces between values.
Example:
,Contact Last Name,Opportunity,
|
Tells the business component which fields are to be read-only for a particular activity type. Activity Type is the field category.
|
Status Field
|
Field
Field from the business component.
|
Tells the business component which field is to be used to indicate the status.
|
Group 2 Business Components
Table 31 lists the user properties that are related to the following business components:
- Pharma Call Products Detailed (class CSSBCProductDetailed)
- Pharma GA Call Products Detailed (class CSSBCProductDetailed)
Table 31. User Properties Related to Group 2 Business Components
User Property Name
|
User Property Value
|
Description
|
Max Auto Generated Priority
|
Number
A numeric value.
Example:
3
|
Tells the business component the maximum number to go up to when auto-generating priorities for the products detailed.
|
Template Fields
|
Field1,field2,...
No start or end comma or spaces between values.
Example:
Name,Priority,Product Issue
|
Tells the business component what fields to copy from the Smart Call template if a Smart Call is chosen.
|
Group 3 Business Components
Table 32 lists the user properties that are related to the following business components:
- Pharma Account Call
- Pharma Attendee Call
- Pharma Template Call
- Pharma Contact Call
- Pharma Promotional Items Dropped
- Pharma Contact Call Sample Dropped
- Pharma Activity Product Issues
- Pharma Call Sample Dropped
- Pharma Meeting
- Pharma Meeting Attendee
- Pharma Meeting Activity
- Pharma Meeting Speaker
NOTE: Not all properties are used in all business components.
Table 32. User Properties Related to Group 3 Business Components
User Property Name
|
User Property Value
|
Description
|
Cascading Fields
|
,field1,field2,...,
Value must start and end with a comma.
Example:
,Start Date,Start Time,
|
Tells the business component which fields should cascade values to a child call component. Make these fields Force Active in the child call. Works in combination with the SubCall Component user property.
|
Must Detail Products
|
Y or N
|
Tells the business component whether detailed products are required for a call.
|
OnlySubmitByPosition
|
Y or N
|
Tells the business component whether the position that entered the record is the only one that can submit it.
|
Status Field
|
Field
Field from the business component.
|
Tells the business component which field is to be used to indicate the status of the activity.
|
SubCall Component
|
Business component name
Any business component name.
|
Tells the business component the child component to which it should cascade values. Works in combination with the Cascading Fields user property.
|
Template Components
|
Business component name
Any business component name.
|
Tells the business component what child components should be copied from the Smart Call template if a Smart Call is chosen.
|
Template Fields
|
Field1,field2,...
No start or end comma.
Example:
Name,Priority,Product Issue
|
Tells the business component what fields to copy from the Smart Call template if a Smart Call is chosen.
|
Attendee Call ReadOnly
|
,field1,field2,...,
Value must start and end with a comma.
Example:
,Start Date,Start Time,
|
Tells the business component what fields are read-only when the type is Attendee Call.
|
Validate Sample Ref #
|
Y or N
|
Tells the business component whether it should require a sample reference number when submitting a call.
|
Update After Submit
|
,field1,field2,...,
Value must start and end with a comma.
Example:
,Comment,
|
Tells the business component what fields are editable after a call is submitted. Generally this user property should be used only to make the Comment field editable.
|
Update After Synch
|
,field1,field2,...,
Value must start and end with a comma.
Example:
,Comment,
|
Tells the business component what fields are editable after a call is synchronized (with Siebel ePharma Handheld on a PDA). Generally this user property should be used only to make the Comment field editable.
|
Group 4 Business Components
Table 33 lists the user properties that are related to the Clinical Subject (class CSSBCBCClinicalSubject) business components.
These properties, used within the eClinical application, allow you to configure new buttons in the application that relate to subject activity. These user properties are at the Field level (Business Component > Field > Field User Properties).
Table 33. User Properties Related to Group 4 Business Components
User Property Name
|
User Property Value
|
Description
|
Template Type Code
|
No default.
Select CLNCL_SUBJ_VST_TMPL_TYPE from the List of Values
(Application Administration > List of Values > List of Values)
|
Defines the visit activity applied when the newly configured button is selected.
|
Subject Status Code
|
No default.
Select CLNCL_SUBJECT_STATUS from the List of Values
(Application Administration > List of Values > List of Values)
|
Defines the status for the subject that is applied when the newly configured button is selected.
|
Template Version Field Name
|
No default.
Must be made Force Active in the Business Component.
|
The corresponding Version ID Field Name that is populated with the version ID of the template version that created the activity.
|
Subject Consent Required
|
Y or N
Default=N
|
This flag indicates whether or not the subject has the Informed Consent Date filled in for the active template for your protocol site. If you set this to Y, and the date is not filled in correctly, an error occurs.
|
Append All Activities
|
Y or N
Default=N
|
When set to Y, activities are appended.
|
Configuring the Visit Generation Buttons
The standard Siebel eClinical application has three visit generation buttons (Screen, Rescreen, and Enroll) on the Subject form.
Using Siebel Tools, you can:
- Reconfigure the buttons to better suit your business needs
- Create new buttons for application of additional templates on the Subject form
The following flow chart illustrates the logic behind these buttons. The logic is the same for all three buttons, although content of the error messages does vary.
