29Siebel Pharma Developer's Reference
Siebel Pharma Developer’s Reference
This appendix contains information on configuring the Pharma application in the Siebel runtime repository. It assumes that you are familiar with the processes and conventions of working with the runtime repository to change one or more user properties. For further information about changing user properties, see Configuring Siebel Business Applications.
This appendix contains the following topics:
Overview of User Properties for Siebel Pharma
User properties are object definitions that are added as children to an applet, business component, control, field, or list column to configure specialized behavior beyond what is configured in the properties of the parent object definition.
Some Siebel Pharma features are driven by user properties. You can customize these features through their respective user properties. With user properties, you can control UI behavior, change default settings or leave them as they are, and enable or disable features.
This topic lists user properties that are specific to Siebel Pharma. For more information about user properties, and user properties that apply to all Siebel Business Applications, see the chapter on user properties in Siebel Developer's Reference.
Targeting Configuration
The Siebel Life Sciences targeting engine can be configured through the user properties found in the following two tables. The first table in this topic details the TargetCategory user properties.
Table TargetCategory User Property
| Field | Required | Description |
|---|---|---|
Name |
Required |
TargetCategory. |
Changed |
Read-only |
An indicator of whether or not the user property is changed. |
Value |
Required |
A value that the targeting engine uses to determine which saved lists are available to the business component. This value is strictly user-defined. Siebel Pharma ships with the default values, Contacts, for contact-related business components and, Accounts, for account-related business components. One TargetCategory can be active for each business component. |
Inactive |
Optional |
An indicator of whether the user property is active. |
Comments |
Optional |
Comments describing the user property. |
Table TargetId User Property
| Field | Required | Description |
|---|---|---|
Name |
Required |
TargetId. |
Changed |
Read-only |
An indicator of whether or not the user property is changed. |
Value |
Required |
A value the targeting engine uses to determine the field in the business component that will be matched against the saved list ID. If the TargetId record is not defined as a user property for the business component, the targeting engine defaults to ROW_ID. One TargetId can be active for each business component. |
Inactive |
Optional |
An indicator of whether the user property is active. |
Comments |
Optional |
Comments describing the user property. |
With these user properties, you can apply a target list in other business components and indicate what value in the business component will be stored for later retrieval. For example, to allow targeting functionality on opportunities, add the user property in the following table to each Opportunity business component.
Table Example TargetCategory User Property
| Field | Required | Description |
|---|---|---|
Name |
Required |
TargetCategory. |
Changed |
Read-only |
An indicator of whether the user property is changed (optional). |
Value |
Required |
For example, Opportunity (or any value you choose). |
Inactive |
Optional |
An indicator of whether the user property is active. |
Comments |
Optional |
Comments describing the user property. |
Once active, this user property will allow users to save a target list of opportunities and apply the list across screens in any Opportunity related business component.
Enabling Inventory Reconciliation Without Lot Numbers
As discussed in Managing Pharma Samples Siebel Pharma allows you to create sample products and associate lot numbers with the samples, then ship and disburse samples by lot numbers while maintaining and reconciling inventory without lot numbers.
Retaining Sample Product Visibility
To allow inventory without lot numbers while retaining sample product visibility, the administrator must do the following:
Use Siebel Web Tools to reconfigure fields and replace business components
Set the value of the Lots For Disperse Only system preference to TRUE
Check the Lot# Tracking flag in the Administration - Product screen
Deploy the changes to the Siebel runtime repository.
Reconfiguring Fields and Replacing Business Components
The following procedure shows you how to reconfigure fields and replace business components in the Siebel runtime repository.
To reconfigure fields and replace business components
Choose View, Object Explorer, and then the Flat tab.
Select Fields, and in the Fields list, query in the Picklist Column for PickList Pharma Samples Stocked Lots.
Lock each project by choosing Tools, and then the Lock Project.
In the Picklist column, replace each occurrence of PickList Pharma Samples Stocked Lots with Picklist Pharma All Unexpired Lots.
Choose View, Object Explorer, and then the Types tab.
Select Applet, and in the Applet list, query for any applet with the value Pharma Stocked Lot Pick Applet.
For each occurrence, set the Business Component to Pharma Sample Lot for Picklist.
Deploy the changes to the Siebel runtime repository.
Changing System Preferences and Enabling Lot Number Tracking
The following procedure shows you how to change system preferences and enable lot number tracking.
To change the system preferences and enable Lot# tracking
Log in to the Pharma web client as an administrator.
Navigate to the Administration - Application screen, then the System Preferences view.
Query for the following System Preference Name records:
Lots For Disperse Only
Samples Lots Enabled
Set the System Preference Value for each of these records to TRUE.
Navigate to the Administration - Product screen, then the Products view, and check the Lot# Tracking flag for each product that requires inventory reconciliation of samples without lot numbers.
Log out of the Pharma web client.
Editing the Labels of the LS Pharma HI Activity Calendar View Buttons
In the Siebel Pharma application, the LS Pharma HI Activity Calendar View has three buttons displayed on the LS Pharma Activity HI Calendar Applet. These buttons are:
New Contact Call. Creates a new contact call.
New Acct Call. Creates a new account call.
New Meeting. Creates a new meeting.
These buttons (or controls) are not configured at the applet level, but are generated by the specialized class of the applet, namely CSSSWELSHICalendarFrame.
Configuring the EditMode User Property
There are two special C++ classes for Pharma Medical Education:
CSSBCPharmaMEPlan
CSSBCPharmaMESubPlan
Both classes support the EditMode user property. When the EditMode user property value is set to Admin, the data ownership (granting update or delete privilege to the user) is not checked. This means that anyone on the sales team, for example, can update the fields in this business component.
Two existing BusComp classes, CSSBCPharmaMEActCost and CSSBCPharmaMEEventPos, are classes without this user property, and therefore require administrator privileges to update or delete.
Submitting Contact Details from Third-Party Applications
When you click the Submit button from the Contact Call Detail view, the C++ class CSSSubmitFrame validates the contact details data and then invokes the CSSBCSubmitBusComp class. This business component class is the great grandparent class of the CSSBCPharmaCall (BC [Pharma Professional Call]) class.
The Pharma Professional Call class wraps the SubmitImp method in a database transaction. The SubmitImp method contains a high level call submission function that automates the entire submission process. If any part of the submission fails, then all transactions performed up to that point are rolled back. The SubmitImp method is a recursive process that calls itself for each child call (Attendee Calls) and then continues with the parent. The process contains the following four main steps:
Create transactions for each sample dropped.
Create transactions for each promotional item dropped.
Set the status to Submitted.
Update the Last Call Date for the current user.
Invoking the Submit Functionality from Third-Party Applications
There are two ways to invoke the Submit functionality from third-party applications:
UI Layer
Business Object Layer
Invoking Submit Functionality From the UI Layer
The following procedure shows you how to invoke the submit functionality from the UI layer.
To invoke Submit from the UI layer
Invoke the CSSSubmitFrame method Submit on the Pharma Professional Call form applet.
Make sure that the property set is empty and contains no arguments.
To suppress the Submit confirmation dialog box, make sure that the business component user property, SuppressSubmitConfirmation, has the value Y on the business component Pharma Professional Call.
Invoking Submit Functionality From the Business Object Layer
The following procedure shows you how to invoke the submit functionality from the business object layer.
To invoke Submit from the Business Component object layer
Invoke the CSSBCSubmitBusComp class BCSubmit on the Pharma Professional Call form applet.
To skip the check for reconciled inventory periods, specify a property with Name equals SkipCheck in the input property set.
Specify a [Value] of Y or TRUE, for example, psIn.SetProperty("SkipCheck","Y").
Invoking Submit from the Contact Call Detail View
Perform the following task to access functionality that is equivalent to when a user clicks Submit from the Contact Call Detail view.
To invoke Submit from the Contact Call Detail view
Invoke the Validate class on the BC [Pharma Professional Call] form applet.
Invoke the CSSBCSubmitBusComp class BCSubmit.
For this method to work correctly, you have to specify at least one property in the Input property set. The information in the table in topic CSSBCPharmaCall Class Business Component User Properties lists the user properties that are related to the Pharma Professional Call business component.
Configuring Account Contacts
The user properties outlined in the following table must be defined before you can activate a targeting period.
The columns displayed in the Account Contacts List must be configured in the user properties.
Table User Properties Related to the Life Sciences Pharma Targeting Business Component
| User Property Name | User Property Value | Description |
|---|---|---|
CanMapColumnUpdate |
Y Default value: Y |
Set this to N to make targeting columns in Accounts Contacts List Read Only. |
MapColumn nn |
Default value: name of targeting fields |
Targeting fields in the Business Component. There are 72 fields defined with different field types. Targeting Data will be mapped and copied to these fields during activation. Only the fields that you define are used for product data mapping. |
The user property outlined in the following table must be defined before you can generate and update the column mapping.
Table User Property Related to the Life Sciences Pharma Target Details Business Component
| User Property Name | User Property Value | Description |
|---|---|---|
MapColumn nn |
Default value: Name of product attribute fields. |
Product data fields in the Business Component. Fields that contain data must be defined, so they can be used to generate column mapping, and can be updated by the Accounts Contacts List. |
Configuring Personalized Content Delivery
This section includes the following topics for configuring personalized content delivery:
Setting the Server Uncompression Location and Other System Preferences
The following procedure shows you how to set the Server Uncompression Location system preference and other system preferences for PCD in Siebel CRM.
You must set the Server Uncompression Location system preference so that when you select the Generate button in Siebel applications, the messaging plan contents will be uncompressed to the location specified by the Server Uncompression Location system preference.
To set the server uncompression location and other system preferences for PCD
Log in to the Siebel business application.
Navigate to the Administration - Application screen, then the System Preferences view.
Query for the Server Uncompression Location system preference.
Enter the server location path where you want uncompression to happen as shown in the following table.
Platform Sever Location Path Windows Server
For example, the server location path for a Windows server is:
C:\BuildFolder\swsm\applicationcontainer\webapps\siebel
You must always provide the
swsm\applicationcontainer\webapps\siebelpath in the Siebel Server installation path (BuildFolder\) where you want uncompression to happen; this applies also for hybrid environments.Non-Windows Server
For example, the server location path for a non-Windows server is:
/export/home/sblqa1/BuildFolder/applicationcontainer/webapps/siebel
Where
sblqa1is the user.Note: Before redeploying the siebel.war file or restarting tomcat server, it is recommended that you back up the files in<Siebel_Install_Path>\swsm\applicationcontainer\webapps\siebel\ filesystemand manually replace them after redeploying the siebel.war file.Set the other system preferences as described in the following table.
Table System Preferences for PCD
Name Value Description Decompressed Files Path
filesystem\assetsNote: On UNIX, the value is:filesystem/assets.Specifies the path of the decompressed messages. Do not use slash (\ or /) at either end of the string.
CheckForNeedToSync
N
If the CheckForNeedToSync user property is set to Y, then the next time you click Decompress in the Siebel Toolbar, only messages with the NeedToSync user property set to Y are decompressed. Otherwise, all messages are decompressed. When you click Decompress in the Siebel toolbar, the decompression time stamp is recorded in the S_USER table. Literature records have a calculated field called NeedToSync. The value in this field changes to True if the literature record is modified after decompression.
Availability of Messages in PCD Planner
Your system administrator loads and verifies messages in the Literature view of the Document Administration screen. The administrator can then associate categories to the messages to make them visible to users creating messaging plans. Users create new messaging plans using the PCD Planner. Messages that are loaded in PCD Planner appear in the Items tab. Access to the messages depends on the catalog visibility associated to the messages and the CanLoadInPlanner calculated field in the Admin Sales Tool business component. A message with the field, CanLoadInPlanner, set to Y is available to users and is loaded into PCD Planner.
The CanLoadInPlanner calculated field is set to Y if the following conditions apply:
The Literature record is of type Message.
The message has a status of Active; that is, the release date is before or is today’s date and the expiration date is greater than today.
The message is a supported file type.
The fields used to control the loading of messages in PCD Planner are listed in PCD Business Component Calculated Fields. For information about the user properties that control access visibility for loading messages in PCD Planner, see User Properties of LS PCD Business Service.
Availability of Messaging Plans in the PCD Viewer
After the user creates a messaging plan, the messaging plan goes through an approval process. When the messaging plan is approved, the administrator sets the status of the messaging plan as Released and associates a category with it to make it visible to the required users. When you click Detail from the Account Call and Contact Call form applets, the messaging plans are automatically loaded in the PCD Viewer.
Access to the messaging plans depend on the catalog visibility associated to the messaging plans and on the CanLoadInDetailer calculated field in the LS Admin Messaging Plans business component. When making contact calls, messaging plans that have the CanLoadInDetailer field set to Y are available to those users who have catalog visibility.
The CanLoadInDetailer calculated field is set to Y when the messaging plan verification status is Successful. The Successful verification status depends on certain conditions.
All presentation items in the messaging plan must:
Have a verification status of Successful.
Be active, that is, the release date of the presentation items must be before or is today’s date and is before the expiration date.
Contain supported file types.
All related messages and detail message content associated with each of the presentation items must:
Not have inactive messages
Be the highest, active version
The calculated fields that control the loading of messaging plans in the PCD Viewer and PCD Planner are listed in the table in PCD Business Component Calculated Fields. For information about user properties that control access visibility for loading messages in PCD Viewer and PCD Planner, see the table User Properties of LS PCD Business Service.
PCD Business Component Calculated Fields
The following information lists the calculated fields that apply to PCD business components.
Table Calculated Fields for PCD Business Components
| Business component | Calculated Field | Values | Description |
|---|---|---|---|
LS Admin Messaging Plans |
CanLoadInDetailer |
IIF (([Max Version Num] = [Version] AND [Product Owner Id] = LoginId() AND [HasInactiveMessages] = "N" AND [IsVerified] = "Y"),'Y','N') |
Messaging plans can be loaded in to the PCD Viewer if the messaging plan:
|
LS Admin Messaging Plans |
CanLoadInPlanner |
Y |
Load all messaging plans into PCD Planner, that is the Create Messaging Plan window. |
LS Admin Messaging Plans |
IsVerified |
IIF (Count(VerificationFailedMessages) greater than 0,"N","Y") |
If messaging plan has verification failed presentation items, set verification status to failed. That is, IsVerified is equal to N. |
LS MP Items |
IsVerified |
IIf([Verification Status] = LookupValue('VERIFICATION_ STATUS','Successful') AND [IsSupportedFormat] = "Y" AND [IsRelatedContentVerified] = "Y" AND [IsDetailContentVerified] = "Y",'Y','N') |
If the verification status (obtained from the join to the S_LIT_LSX table) of Message is Successful, and Message is of supported file type, and all the related and detail content associated with this presentation item is verified, then for this presentation item IsVerified is equal to Y. |
LS MP Items |
IsSupportedFormat |
IIF(([LitFileExt] = 'SWF' OR [LitFileExt] = 'swf' OR [LitFileExt] = 'jpg' OR [LitFileExt] = 'JPG' OR [LitFileExt] = 'GIF' OR [LitFileExt] = 'gif' OR [LitFileExt] = 'png' OR [LitFileExt] = 'PNG'), 'Y','N') |
Checks if the file type of the presentation item is supported. |
LS MP Items |
IsDetailContentVerified |
IIF (Count(Verified Detail Content) is greater than 0,"N","Y") |
Checks if all detail content associated with the presentation item is verified. |
LS MP Items |
IsRelatedContentVerified |
IIF (Count(Verified Related Content) is greater than 0,"N","Y") |
Checks if all related content associated with presentation item is verified. |
LS Detail Messages |
IsVerified |
IIf([Verification Status] = LookupValue('VERIFICATION_ STATUS','Successful')AND [IsSupportedFormat] = "Y" ,'Y','N') |
If the verification status (obtained from the join to the S_LIT_LSX table) of Message is Successful, and Message is of supported file type, then for this related item IsVerified is equal to Y. |
LS Detail Messages |
IsSupportedFormat |
IIF(([LitFileExt] = 'SWF' OR [LitFileExt] = 'swf' OR [LitFileExt] = 'jpg' OR [LitFileExt] = 'JPG' OR [LitFileExt] = 'GIF' OR [LitFileExt] = 'gif' OR [LitFileExt] = 'png' OR [LitFileExt] = 'PNG'), 'Y','N') |
Checks if the file type is supported. |
LS Related Messages |
IsVerified |
IIf([Verification Status] = LookupValue('VERIFICATION_STATUS', 'Successful') AND [IsSupportedFormat] = "Y" ,'Y','N') |
If the verification status (obtained from the join to the S_LIT_LSX table) of Message is Successful, and Message is of a supported file type, then for this related item, IsVerified is equal to Y. |
LS Related Messages |
IsSupportedFormat |
IIF(([LitFileExt] = 'SWF' OR [LitFileExt] = 'swf' OR [LitFileExt] = 'jpg' OR [LitFileExt] = 'JPG' OR [LitFileExt] = 'GIF' OR [LitFileExt] = 'gif' OR [LitFileExt] = 'png' OR [LitFileExt] = 'PNG'), 'Y','N') |
Checks if the file type is supported. |
Admin Sales Tool |
CanLoadInPlanner |
IIF (([Sales Tool Type] = LookupValue ("SALES_TOOL_TYPE", "Message") AND [IsActive] = "Y" AND [IsSupportedFormat] = "Y"),'Y','N') |
Literature item can be loaded in PCD Planner if:
|
Admin Sales Tool |
CanLoadInDetailer |
IIF (([Sales Tool Type] = LookupValue ("SALES_TOOL_TYPE", "Message") AND [IsSupportedFormat] = "Y"),'Y','N') |
Literature Item can be verified if type is equal to Message and is of supported file type. |
Admin Sales Tool |
IsSupportedFormat |
IIF(([LitFileExt] = 'SWF' OR [LitFileExt] = 'swf' OR [LitFileExt] = 'jpg' OR [LitFileExt] = 'JPG' OR [LitFileExt] = 'GIF' OR [LitFileExt] = 'gif' OR [LitFileExt] = 'png' OR [LitFileExt] = 'PNG'), 'Y','N') |
Checks if the file type is supported. |
About Recommended Messaging Plans
When a sales representative launches the PCD Viewer from the Contact Call Detail View, Account Contact Call View, or Account Call Detail View, all messaging plans available to the sales representative are loaded into the PCD Viewer by Life Sciences (LS) PCD Services. For more information about the user properties for the LS PCS Services, see User Properties of LS PCD Business Service.
In LS PCD Service, the OptimizeDetailingPlan method identifies messaging plans that are recommended for the call. These messaging plans are called Recommended Messaging Plans and have an asterisk (a star icon) suffixed to its name in the list of available messaging plans when displayed in the PCD Viewer.
By default, the OptimizedDetailingPlan functionality is configured to identify recommended messaging plans for Contact Call and Account Contact Call detailing only. If Objectives or Offers are associated to a Contact Call or Account Contact Call, recommended messaging plans are identified as outlined in this section.
However, if no Offer or Objective is associated to a Contact Call or Account Contact Call, fields for entering target segments, in the Contact Call or Account Contact Call views are available, and recommended messaging plans can be selected based on these field values.
Similarly, if no Objectives are associated to an Account Call, fields for entering target segments in the Account Call view are available, and recommended messaging plans can be selected based on these field values.
Configuring Target Segment Fields for Contact Call and Account Contact Call Views
The following procedure shows you how to configure target segment fields for the Contact Call or Account Contact Call views.
To configure fields for entering target segments in Contact Call view or Account Contact Call view
Add fields in Pharma Professional Call business component (BC) mapping to one or more extension columns in S_EVT_ACT_X. For example:
Field Name: Call Segment Code 1 Join: S_EVT_ACT_X Column: ATTRIB_01
Field Name: Call Segment Code 2 Join: S_EVT_ACT_X Column: ATTRIB_02
Configure the fields in Pharma Professional Call Form Applet.
In the Pharma Professional Call BC, update the BC user property Call Seg Code Fields with a list of segment code fields, with each segment code field separated by a comma. For example, Call Segment Code 1, Call Segment Code 2.
Configuring Target Segment Fields for Account Call View
The following procedure shows you how to configure target segment fields for the Account Call view.
To configure fields for entering target segments in Account Call view
Add fields in Pharma Account Call business component (BC) mapping to one or more extension columns in S_EVT_ACT_X.
For example:
Field Name: Call Segment Code 1 Join: S_EVT_ACT_X Column: ATTRIB_01
Field Name: Call Segment Code 2 Join: S_EVT_ACT_X Column: ATTRIB_02
Configure the fields in Pharma Account Call Form Applet.
In the Pharma Account Call BC, update the BC user property Call Seg Code Fields with a list of segment code fields, with each segment code field separated by a comma. For example, Call Segment Code 1, Call Segment Code 2.
By default, the OptimizedDetailingPlan functionality is not configured to identify recommended messaging plans for Account Call if an Objective is associated to the Account Call.
Configuring Fields For Account Call View When Objectives are Associated With the Account Call
The following procedure shows you how to configure fields for the Account Call view when objectives are associated with the Account Call.
To configure fields for Account Call view when Objectives are associated to an Account Call
Create one or more extension columns in S_ACCNT_SRC (for example, X_SEG_CODE1, X_SEG_CODE2) and apply these changes in the Siebel Business Applications database.
Add fields in Pharma Campaign Target Account BC and map these fields to the columns created in S_ACCNT_SRC. For example:
Field Name: Segment Code 1 Join: S_ACCNT_SRC Column: X_SEG_CODE1
Field Name: Segment Code 2 Join: S_ACCNT_SRC Column: X_SEG_CODE2
Configure the fields in Pharma Campaign Target Account List Applet.
In the Pharma Account Call BC, update the BC user property Objective Seg Code Fields with a list of segment code fields, with each segment code field separated by a comma. For example, Segment Code 1, Segment Code 2.
Optimize Detailing Plan Method
Signature of the Optimize Detailing Plan method is as follows:
ErrCode OptimizeDetailingPlan (const CCFPropertySet& inputArgs, CCFPropertySet& outputArgs)
The input parameters to this method are sent as an input property set (inputArgs).
The output of this method is an xml string, set in the output property set (outputArgs) with property name as RecommendedMsgPlans. For example:
outputArgs.SetProperty("RecommendedMsgPlans",<xmlstring>);
The xml string in the output property set should be in the following format:
<OptimizedDetailingPlan> <ListOfRecommendedMessagingPlans> <MessagingPlan> <Id> </Id> <SequenceNumber> </SequenceNumber> <OfferId> </OfferId> <ObjectiveId> </ObjectiveId> <SegmentCode> </SegmentCode> </MessagingPlan> <MessagingPlan> <Id> </Id> <SequenceNumber> </SequenceNumber> <OfferId> </OfferId> <ObjectiveId> </ObjectiveId> <SegmentCode> </SegmentCode> </MessagingPlan> </ListOfRecommendedMessagingPlans> </OptimizedDetailingPlan>
You can use your own logic to identify recommended messaging plans by overriding the OptimizeDetailingPlan method using a script.
To override OptimizeDetailingPlan
In Siebel Tools, query for LS PCD Service.
Right-click LS PCD Service, and click Edit Server scripts.
Update the Service_PreInvokeMethod function to override logic for OptimizeDetailingPlan as shown:
function Service_PreInvokeMethod (MethodName, Inputs, Outputs) { if(MethodName == "OptimizeDetailingPlan") { …….. User logic to identify Recommended messaging plans… set output property set… ….. return (CancelOperation); } else return (ContinueOperation); }
Identifying Recommended Messaging Plans
The default OptimizeDetailingPlan method identifies Recommended Messaging Plans. If an objective is selected for a call, the OptimizedDetailinPlan method:
Provides a list of messaging plans to be loaded to the PCD Viewer based on messaging plans associated with an objective
Associates a Target Segment Code matching the objective's Contact Target Segment Code fields, that is, one or more fields from S_CAMP_CON table.
Note: The field names from Action BC are configurable. If the Objective Id is null, then the segment code fields (one or more fields from Action BC) are used to match and search for Recommended Messaging Plans based on Target Segment Code field defined for each Messaging Plan.
Scenario for Identifying Recommended Messaging Plans
This scenario gives one example of identifying recommended messaging plans. You might use this feature differently, depending on your business model.
A sales representative (Sales Rep A) has an Objectives set up called Q1 Objective and has Dr. Adler as a target for this objective.
The Target Record of Dr. Adler has two custom extension fields to hold SegCode1 and SegCode2 for two products, A1 and B2, that Sales Rep A deals with.
The Sales Operation Manager has also five messaging plans, namely MP1, MP2, MP3, MP4, and MP5, associated with this Objective and each messaging plan has a Target Segment code specified as A1, B1, A2, B2, and A1.
Sales Rep A creates a call on Dr. Adler and selects Q1 Objective as Objective for the call. The OptimizeDetailingPlan finds matching messaging plans associated with Objective Q1 Objective that have Target Segment code as A1 and B2. This scenario results in MP1,MP4 and MP5 selected as recommended messaging plans.
Next, consider the situation where Sales Rep A creates another call on Dr. Adler and does not select Objective for the call. OptimizeDetailingPlan matches custom extension fields defined on the call business component (BC) to hold segment code values against Target Segment Code fields on the messaging plans to identify recommended messaging plans.
For Contact Calls with Marketing Communications, the LS PCD Service method provides a list of messaging plans to be loaded in the PCD Viewer based on messaging plans associated with Contact Call Offers for which the sales representative has access. For example, if Sales Rep A has access to three Contact Call Offers but is in the Access Group of only one of the messaging plans associated with the Contact Call Offer, then only that messaging plan can be loaded in the PCD Viewer.
Modifying a Tooltip in the PCD Viewer
You can customize the tooltips that are displayed when a user places the cursor over the buttons in the PCD Viewer.
To modify a tooltip in the PCD viewer
Navigate to folder
<Siebel installation path>\applicationcontainer\webapps\siebel\<language folder>\ISDData\<language folder>.Open the lfs.xml file and enter the tooltip string as shown in the following example:
<IDS_NEW_TOOLTIP>New ToolTip </IDS_NEW_TOOLTIP>Navigate to folder
<Siebel installation path>\applicationontainer\webapps\siebel\<language folder>.Open the
toolbar_buttons.xmlfile and locate the button tag for which tooltip is to be modified.Update the <toolTip> tag for the selected button with the string tag created in
lfs.xmlas follows:
<toolbars>
<toolbar toolbarId="Detailer - Standard" defaultState="DEFAULT" firstChangeInternal="false" buttonId="1">
<respectStates>
<toolbar name="Detailer - Standard"/>
</respectStates>
<button buttonId="2">
<label/>
<toolTip>IDS_NEW_TOOLTIP</toolTip>
<icon/>
…….
</button>
</toolbar>
</toolbars>
User Properties of the PCD Applets
Siebel business components are based on the CSSBusComp class, or on a C++ class derived from the CSSBusComp class. Business component user properties allow Siebel administrators to control and adjust the behavior of Siebel Life Sciences in the Siebel runtime repository.
The following is a list of PCD applets that display the Flex application user properties. Flex is a third-party application used by PCD:
LS Admin Edit Messaging Plan
LS Admin New Messaging Plan
LS Admin Preview Messaging Plan
LS Edit Personalized Messaging Plan
LS Personalize Messaging Plan
LS Preview Messaging Plan
LS Verify Message
The following information lists the user properties that apply to PCD popup applets that display Flex UI elements.
Table User Properties for PCD popup applets
Name Value Description FlexAppMode
MP-Admin
The Flex application launches PCD in the modes that determine the UI. For example, for preparing for a contact call, PCD is launched in ISDPreview mode. For message plan creation, the MP-Admin mode is launched.
Note: Do not modify this user property.InitMethod
EditMsgPlan
The method name in LS PCD Service that initializes the Flex application.
Note: Do not modify this user property.IntegrationObj
AdminMessagingPlanIO
Specifies the I/O (input/output) to be used for writing data to the database. For example, data is sent in XML format.
Note: Do not modify this user property.CallIOBS
Pharma Account Call IO BS
Name of the business service that executes the I/O for extracting call data.
CallType
Account Call
Contact Call
Specifies the type of call.
User Properties of LS PCD Business Service
The following information lists the user properties that apply to Life Sciences (LS) PCD Services.
Table User Properties for LS PCD Services
| Name | Value | Description |
|---|---|---|
LoadLOVTypes |
PCD_RESPONSE_TYPE MSG_PLAN_ITEM_TYPE VERIFICATION_STATUS MSG_DISPLAY_STATUS |
Specifies the LOV type values that are extracted and sent to the Flex application.
Note: Do not modify this user property.
|
SyncEndConfirmation |
Y |
If you click Uncompress, an asynchronous process starts and decompresses the messages. At the end of this decompression process, if the value of this user property is equal to Y, then the Siebel Business Application displays a message box to confirm the end of the decompression process. However, this user property value is ignored by the Siebel Server and no confirmation message dialog is displayed. |
SyncStartConfirmation |
Y |
If you click Uncompress, an asynchronous process starts and decompresses the messages. At the start of this decompression process, if the value of this user property is equal to Y then the Siebel Business Application displays a message box to confirm the start of the decompression process. However, this user property value is ignored by the Siebel Server and no confirmation message dialog is displayed. |
Verify Disabled Error Msg |
Verification cannot be done for this Literature Record |
In the Administration - Document screen, then the Literature view, verification is done only on literature records with type equal to Message. For records of type Message, clicking Verify displays the error message specified in this user property. |
No Messaging Plan Error Msg |
No Messages Available for Detail |
In Account Call and Contact Call form applets, if there are no messaging plans available, clicking Detail displays the error message specified in this user property. |
ViewModeForLoadingMPInDetailer |
Catalog |
Specifies the access type to be used for loading messaging plans in the PCD Viewer. |
ViewModeForLoadingMsgInPlanner |
Catalog |
Specifies the access type to be used for loading messages in PCD Planner. |
API for Using Multi-file Content
The message can access its component files in the main Flex content by making a call to the getMessageFileName(filename) application programming interface (API).
The parameter filename must be the filename of the component file in the Siebel Business Application. The Siebel Business Application returns the path of the component file. The message can then use the component file path to add additional component files to the PCD content.
For example, to access and load component files, the main message must call the following functions:
Application.application.getMessageFileName(fileName); if using Flex for content
creation
The syntax for childData API is as follows:
getMessageFileName(filename:String):void
API for Recording Section Data
PCD Viewer tracks various information such as the duration for which each message (digital content) in a messaging plan was presented. It does this by recording the timestamp when the presentation of a message started and the timestamp when the presentation of the message ended.
The message (digital content) performs additional tracking and make calls to the PCD Viewer to pass tracking information. The PCD Viewer takes the combined information and make calls to Siebel Business Application to write back presentation data.
For example, consider a message that has three critical sections where the start and end time of each section needs to be tracked along with start and end time of the entire message. To track section data. the message must pass the section's tracking information to the PCD Viewer by calling the following function:
Application.application.childData(sectionName, startTime, endTime); if using Flex for content creation
The syntax for childData API is as follows:
childData(name:String, start:Date, end:Date):void
When you close the PCD Viewer, data is written to the presentation detail applet. You can view the full section by section record of messages as shown in the example in the following table.
| Message Name | Section Name | Messaging Plan Name | Start Name | End Name |
|---|---|---|---|---|
Samp1 |
SampMP |
7:30 pm |
7:45 pm |
|
Samp1 |
Sec1 |
SampMP |
7:31 pm |
7:35 pm |
Samp1 |
Sec2 |
SampMP |
7:36 pm |
7:40 pm |
Samp1 |
Sec3 |
SampMP |
7:41 pm |
7:45 pm |
Pharma Service User Properties
This section includes:
LS Pharma Validation Service User Properties
The following information lists the user properties that apply to LS Pharma Validation service.
Table User Properties for LS Pharma Validation Service
| Name | Value | Description |
|---|---|---|
Account BC |
Account |
Shows the name of BC that represents Account entity, used by Validation engine to get Account Details. The default value is Account. |
Account Call BC |
Pharma Account Call |
Shows the name of BC that represents Account Call entity, used by Validation engine to validate Account calls. |
Account Contact Call BC |
Pharma Professional Call |
Shows the name of BC that represents Account Contact Call entity, used by Validation engine to validate Account calls. |
Contact BC |
Contact |
Shows the name of BC that represents Contact entity, used by Validation engine to get Contact Details. The default value is Contact. |
DEA Expiry Date Field |
DEA Expr |
Shows the name of the field that stores DEA number Expiry date. |
DEA Number Field |
DEA# |
Shows the name of the field that stores DEA number. |
Employee BC |
Employee |
Shows the name of BC that represents Employee entity, used by Validation engine to get employee details. The default value is Employee. |
Enable Auto Set Call Type |
Y |
Turns on or off the auto-setting Call Type in Call BC, when Validation is done. |
Enable Lot Cutoff Validation Sub Rule |
LOT CUTOFF SUB RULE, Y |
Shows Lot # cutoff rule on current Call. The first part of the rule is Rule name used to get error message from Message Category. The second part of the rule turns on or off the rule, while the third part of the rule displays an error, warn, or ignore message. |
Enable Lot Validation Sub Rule |
LOT VALID SUB RULE, Y |
Determines if dropped sample is not expired in current Call. The first part of the rule is Rule name used to get error message from Message Category. The second part of the rule turns on or off the rule, while the third part of the rule displays an error, warn, or ignore message. |
Enable Max Samples Per Allocation Period Sub Rule |
MAX PER ALLOC PERIOD SUB RULE, Y, WARNING |
Validates Quantity Dropped in call Allocated to Sales Rep in active period. The first part of the rule is Rule name used to get error message from Message Category. The second part of the rule turns on or off the rule, while the third part of the rule displays an error, warn, or ignore message. |
Enable Max Samples Per Call Sub Rule |
MAX PER CALL SUB RULE, Y, WARNING |
Validates Quantity Dropped in call for Maximum per call in active period. The first part of the rule is Rule name used to get error message from Message Category. The second part of the rule turns on or off the rule, while the third part of the rule displays an error, warn, or ignore message. |
Enable One Time Sampling Sub Rule |
Y |
To allow one time sampling to Contact with InActive but Not expired license. |
Enable Stop Sampling Sub Rule |
STOP SAMPLE SUB RULE, Y |
The first part of the rule is Rule name used to get error message from Message Category. The second part of the rule turns on or off the rule, while the third part of the rule displays an error, warn, or ignore message. |
License Expiry Date Field |
License Expiry Date |
The name of the field that stores License Expiry Date. |
License Number Field |
License Number |
The name of the field that stores the License Number. |
License Status Field |
License Status |
The name of the field that stores the License Status. |
Log Level |
1- Error, 2- Error and Warning 3 Error, warning and ignore/success |
Indicates level while logging validation results. |
Pharma Personal Samples BC |
Pharma Personal Samples List |
The name of BC for Sales Reps personal samples. |
Products Detailed BC |
Pharma Call Products Detailed |
The name of BC for products detailed in Pharma call. |
Professional Call BC |
Pharma Professional Call |
The name of BC for Contact call BC and Account contact call BC. |
Promotional Items BC |
Pharma Promotional Items Dropped |
The name of BC for Promotional items dropped in Pharma call. |
Required Fields To Submit: Account Call |
The names of Fields separated with comma, required to submit Account Call. |
|
Required Fields To Submit: Professional Call |
The names of Fields separated with comma, required to submit Contact Call. |
|
SRE PT Exception - DEA: Nurse Practitioner |
NJ| |
For each professional exception, the State names where Profession types that can be sampled with DEA number (state names before pipe (|)), or with out DEA number (state names after pipe). |
SRE PT Exception - License: Nurse Practitioner |
NJ| |
For each professional exception, the State names where Profession types that can be sampled with License number (state names before pipe (|)) or with out License number (state names after pipe). |
SRE Professional Types |
Physician |
The profession Types allowed to be sampled in all States with Valid License or DEA Number. |
Samples Dropped BC |
Pharma Call Sample Dropped |
The name of BC for Samples dropped in Pharma call. |
Valid License Status |
Active |
Indicates valid status value of License Number. |
Validate Lot# Field |
Lot Expiry Date |
The Name of Field for Lot Expiry date, that is to be verified in Lot expiry verification. |
Validation Results BC |
LS Pharma Call Validation Results |
The name of BC for inserting call validation results. |
Validation Rule 1 |
LICENSE EXPIRATION RULE, 1, IsLicenseExpired, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 10 |
CONTACT SAMPLING RULE, 1, IsValidProfToSample, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 11 |
PRODUCT PRIORITY RULE, 6, AreProdDetailedValid, ERROR, 5 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 12 |
MUST DETAIL RULE, 6, AreProductsDetailed, ERROR, 5 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 13 |
MUST DISBURSE RULE, 1, AreSamplesDropped, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 14 |
REQUIRED FIELDS RULE, 6, ValidateReqFields, ERROR, 5 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 15 |
CALL DATE RULE, 7, IsValidCallDate, ERROR, 7 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 16 |
REFERENCE NUMBER RULE, 6, ValidateSampRefNum, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 17 |
SRE PROFESSIONAL RULE, 1, IsValidSREProfType, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 18 |
SAMPLES REQUEST VALIDATION RULE, 7, AreSamplesRequestedValid, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 19 |
PROMOTIONAL ITEMS RULE, 7, ArePromoItemsDroppedValid, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 2 |
SUBMIT BY POSITION RULE, 7, IsValidPositionToSubmit, ERROR, 7 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 3 |
LICENSE RULE,1,IsValidLicenseNumber, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 4 |
LICENSE STATUS RULE, 1, IsValidLicenseStatus, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 5 |
PROFESSIONAL PROFILE RULE, 1, IsValidProfProfile, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 6 |
EMPLOYEE SAMPLING RULE, 1, IsValidEmpToSample, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 7 |
DEA RULE, 1, IsValidDEANumber, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 8 |
DEA EXPIRATION RULE, 1, IsDEAExpired, ERROR, 3 For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validation Rule 9 |
SAMPLES VALIDATION RULE, 1, AreSamplesDroppedValid, ERROR, 3For more information, see Format for Validation Rule N User Propertyin LS Pharma Validation Service. |
Values include:
|
Validator Type |
Pharma Call |
Type of Validation done by Validation engine. Currently, only Pharma Call type supported. |
Format for Validation Rule N User Propertyin LS Pharma Validation Service
Each Validation Rule can have a maximum of 5 components, where the rule name is mandatory. A description of each component in the Validation Rule follows:
Rule Name. Rule Names, which are mandatory, are defined in the List of Values. The LOV type is LS_VALIDATION_RULE_NAME.
Number indicating when to apply the rule. The number indicates when to process the rule, and depends on the Call Status as follows:
If the value is 1, then the rule is evaluated if the call is not signed (that is, for electronic signatures).
If the value is 2, then the rule is evaluated for Paper Signed calls upon call submit.
If the value is 4, then the rule is evaluated for Electronically Signed calls upon call submit.
If the value is 6, then the rule is evaluated for both Paper and Electronically Signed calls upon call submit.
If the value is 7, then the rule is evaluated whenever call validation is carried out.
Method Name. The name of the method that is called to validate the rule. Each rule that is supported by default has an associated method. If customers want to override the existing validation rule or create a new rule, then they can do so. If overriding the existing rule, then the method name must be changed to a different value. Customers can choose to leave the method name blank or they can enter a different value for the method name. If a new rule is created, then a new user property must be defined according to the rule format.
Type of failure message.The type of the message that must be logged when the validation rule fails. This can be an ERROR or a WARNING. If the validation is successful, then a message of type SUCCESS is logged. If the rule does not apply to the current call, then a message of type IGNORE is logged.
Type of Call. The type of the call to which the rule applies:
If the value is 1, then the rule applies to Contact Calls.
If the value is 2, then the rule applies to Attendee Calls.
If the value is 4, then the rule applies to Account Calls.
If the value is 3, then the rule applies to Contact and Attendee Calls.
If the value is 5, then the rule applies to Contact and Account Calls.
If the value is 6, then the rule applies to Attendee and Account Calls.
If the value is 7, then the rule applies to Contact, Attendee, and Account Calls.
LS Pharma Validation Service CE User Properties
The following information lists the user properties that apply to LS Pharma Validation Service CE.
Table User Properties for LS Pharma Validation Service CE
| Name | Value | Description |
|---|---|---|
Account BC |
Account |
The name of BC that represents Account entity, used by Validation engine to get Account Details. The default value is Account. |
Account Call BC |
Pharma Account Call |
The name of BC that represents Account Call entity, used by Validation engine to validate Account calls. |
Account Contact Call BC |
Pharma Professional Call |
The name of BC that represents Account Contact Call entity, used by Validation engine to validate Account calls. |
Contact BC |
Contact |
The name of BC that represents Contact entity, used by Validation engine to get Contact Details. Defaults to Contact. |
DEA Expiry Date Field |
DEA Expr |
The Name of the field that stores DEA number Expiry date. |
DEA Number Field |
DEA# |
The name of the field that stores DEA number. |
Employee BC |
Employee |
The name of BC that represents Employee entity, used by Validation engine to get employee details. Default to Employee. |
Enable Auto Set Call Type |
Y |
Turns on or off auto-setting Call Type in Call BC, when Validation is done. |
Enable Lot Cutoff Validation Sub Rule |
LOT CUTOFF SUB RULE, Y |
To see Lot # cutoff rule on current Call. First part of rule is Rule name used to get error message from Message Category. Second part states to turn On or Off the rule, while the third part of the rule is to Error, Warn, or Ignore. |
Enable Lot Validation Sub Rule |
LOT VALID SUB RULE, Y |
To see dropped sample is not expired in current Call. First part of rule is Rule name used to get error message from Message Category. Second part states to turn On or Off the rule, while the third part of the rule is to Error, Warn, or Ignore. |
Enable Max Samples Per Allocation Period Sub Rule |
MAX PER ALLOC PERIOD SUB RULE, Y, WARNING |
To Validate Quantity Dropped in call is crossing Allocated to Sales Rep in active period. First part of rule is Rule name used to get error message from Message Category. Second part states to turn On or Off the rule, while the third part of the rule is to Error, Warn, or Ignore. |
Enable Max Samples Per Call Sub Rule |
MAX PER CALL SUB RULE, Y, WARNING |
To Validate Quantity Dropped in call is crossing Maximum per call in active period. First part of rule is Rule name used to get error message from Message Category. Second part states to turn On or Off the rule, while the third part of the rule is to Error, Warn, or Ignore. |
Enable One Time Sampling Sub Rule |
Y |
To allow One time sampling to Contact with InActive but Not expired license. |
Enable Stop Sampling Sub Rule |
STOP SAMPLE SUB RULE, Y |
First part of rule is Rule name used to get error message from Message Category. Second part states to turn On or Off the rule, while the third part of the rule is to Error, Warn, or Ignore. |
License Expiry Date Field |
License Expiry Date |
The name of the field that stores License Expiry Date. |
License Number Field |
License Number |
The name of the field that stores the License number. |
License Status Field |
License Status |
The name of the field that stores the license Status. |
Log Level |
1-error, 2-error and Warning, 3- error, warning and ignore/success |
Indicates level while logging validation results. |
Pharma Personal Samples BC |
Pharma Personal Samples List |
The name of BC for Sales Reps personal samples. |
Products Detailed BC |
Pharma Call Products Detailed |
The name of BC for products detailed in Pharma call. |
Professional Call BC |
Pharma Professional Call |
The name of BC for Contact call BC and Account contact call BC. |
Promotional Items BC |
Pharma Promotional Items Dropped |
The name of BC for Promotional items dropped in Pharma call. |
Required Fields To Submit: Account Call |
The names of Fields separated with comma, required to submit Account Call. |
|
Required Fields To Submit: Professional Call |
The names of Fields separated with comma, required to submit Contact Call. |
|
SRE PT Exception - DEA: Nurse Practitioner |
NJ| |
The State names where Profession types that can be sampled with DEA number (state names before pipe (|)) or with out DEA number (state names after pipe). |
SRE PT Exception - License: Nurse Practitioner |
NJ| |
The State names where Profession types that can be sampled with License number (state names before pipe (|)) or with out License number (state names after pipe). |
SRE Professional Types |
Physician |
The profession Types allowed to be sampled in all States with Valid License and or DEA Number. |
Samples Dropped BC |
Pharma Call Sample Dropped |
The name of BC for Samples dropped in Pharma call. |
Valid License Status |
Active |
Indicates valid status value of License Number. |
Validate Lot# Field |
Lot Expiry Date |
The Name of Field for Lot Expiry date, that is to be verified in Lot expiry verification. |
Validation Results BC |
LS Pharma Call Validation Results |
The name of BC for inserting call validation results. |
Validation Rule 1 |
LICENSE EXPIRATION RULE, 1, IsLicenseExpired, ERROR, 3 |
Values include:
|
Validation Rule 10 |
CONTACT SAMPLING RULE, 1, IsValidProfToSample, ERROR, 3 |
Values include:
|
Validation Rule 11 |
PRODUCT PRIORITY RULE, 6, AreProdDetailedValid, ERROR, 5 |
Values include:
|
Validation Rule 12 |
MUST DETAIL RULE, 6, AreProductsDetailed, ERROR, 5 |
Values include:
|
Validation Rule 13 |
MUST DISBURSE RULE, 1, AreSamplesDropped, ERROR, 3 |
Values include:
|
Validation Rule 14 |
REQUIRED FIELDS RULE, 6, ValidateReqFields, ERROR, 5 |
Values include:
|
Validation Rule 15 |
CALL DATE RULE, 7, IsValidCallDate, ERROR, 7 |
Values include:
|
Validation Rule 16 |
REFERENCE NUMBER RULE, 6, ValidateSampRefNum, ERROR, 3 |
Values include:
|
Validation Rule 17 |
SRE PROFESSIONAL RULE, 1, IsValidSREProfType, ERROR, 3 |
Values include:
|
Validation Rule 18 |
SAMPLES REQUEST VALIDATION RULE, 7, AreSamplesRequestedValid, ERROR, 3 |
Values include:
|
Validation Rule 19 |
PROMOTIONAL ITEMS RULE, 7, ArePromoItemsDroppedValid, ERROR, 3 |
Values include:
|
Validation Rule 2 |
SUBMIT BY POSITION RULE, 7, IsValidPositionToSubmit, ERROR, 7 |
Values include:
|
Validation Rule 3 |
LICENSE RULE,1,IsValidLicenseNumber, ERROR, 3 |
Values include:
|
Validation Rule 4 |
LICENSE STATUS RULE, 1, IsValidLicenseStatus, ERROR, 3 |
Values include:
|
Validation Rule 5 |
PROFESSIONAL PROFILE RULE, 1, IsValidProfProfile, ERROR, 3 |
Values include:
|
Validation Rule 6 |
EMPLOYEE SAMPLING RULE, 1, IsValidEmpToSample, ERROR, 3 |
Values include:
|
Validation Rule 7 |
DEA RULE, 1, IsValidDEANumber, ERROR, 3 |
Values include:
|
Validation Rule 8 |
DEA EXPIRATION RULE, 1, IsDEAExpired, ERROR, 3 |
Values include:
|
Validation Rule 9 |
SAMPLES VALIDATION RULE, 1, AreSamplesDroppedValid, ERROR, 3 |
Values include:
|
Validator Type |
Pharma Call |
Type of Validation done by Validation engine. For future use. Currently, Pharma Call type is only supported. |
LS Pharma Call Utility Service User Properties
The following information lists the user properties that apply to LS Pharma Call utility service.
Table User Properties for LS Pharma Call Utility Service
| Name | Value | Description |
|---|---|---|
DrillDownView:Account Call 1 |
LS Pharma Account Call Detail Execute View |
Name of the View to Navigate depend on the User property for Accounts. |
DrillDownView:Accounts Contacts Call 1 |
LS Pharma Accounts Contacts Call Detail Execute View |
Name of the View to Navigate depend on the User property for Account Contacts. |
DrillDownView:Clinical Call 1 |
Clinical Trip Report Detail View |
Name of the View to Navigate depend on the User property for Clinical Trip Report. |
DrillDownView:Contact Call 1 |
LS Pharma Contact Call Detail Execute View |
Name of the View to Navigate depend on the User property for Contacts. |
DrillDownView:New Meeting |
Pharma Meeting Activities View |
Name of the View to Navigate depend on the User property for Meeting. |
LS Pharma Smart Call Template User Properties
The following information lists the user properties that apply to LS Pharma Smart Call templates.
Table User Properties for LS Pharma Smart Call Templates
| Name | Value | Description |
|---|---|---|
Best Lot BC Name |
LS Pharma My Sample Lots List |
Name of the Best Lot BC. |
Call Level Template Components |
Pharma Call Products Detailed, Pharma Promotional Items Dropped, Pharma Activity Decision Issue, Pharma Call Sample Dropped, LS Pharma Samples Request BC |
Used to list the BusComp names. The record gets copied over from the Smart Call template view BusComps to the Call detail view BusComps that are specified in this user property. BusComp names should be separated by comma. |
Call Level Template Fields |
Comment Associated Cost |
Used to list the field names. Only the fields that are specified in this user property gets copied over from the Pharma Template Call BC to Pharma Professional Call BC. Field names should be separated by comma. |
Child BusComp Call Detail |
Pharma Call Products Detailed |
Holds the name of the Product Detail BusComp. |
Child BusComp Sample Drop |
Pharma Call Sample Dropped |
Holds the name of the Promotional Item BusComp. |
Child BusComp Sample Request |
LS Pharma Samples Request BC |
Holds the name of the Sample Request BusComp. |
LS Pharma Samples Request BC Template Fields |
Product Allocation Id, Name, Quantity |
Used to list the names of the fields that are to be copied from the Sample Request BC of Smart Call view to Sample Request BC of Call detail view. The field names should be separated by comma. |
Parent Call BusComp Name |
Pharma Professional Call |
Holds the name of the Parent Call BusComp. |
Pharma Call Products Detailed Template Fields |
Product Allocation Id, Name, Priority, Indication, Product Issue |
Used to list the names of the fields that are to be copied from the Product Detail BC of Smart Call view to Product Detail BC of Call detail view. The field names should be separated by comma. |
Pharma Call Sample Dropped Template Fields |
Product Allocation Id, Name, Lot Name, Quantity |
Used to list the names of the fields that are to be copied from the Sample Drop BC of Smart Call view to Sample Drop BC of Call detail view. The field names should be separated by comma. |
Pharma Promotional Items Dropped Template Fields |
Product Allocation Id, Name, Quantity |
Used to list the names of the fields that are to be copied from the Promo Item BC of Smart Call view to Promo Item BC of Call detail view. The field name should be separated by comma. |
Pharma Smart Call Template BC Name |
Pharma Template Call |
Name of the Pharma Smart Call Template BC. |
Pharma Smart Call Template BO Name |
Pharma Template Call |
Name of the Pharma Smart Call Template BO. |
Product Allocation BO Name |
Pharma Personal Products & Samples |
Holds the name of the Product Allocation BO name. |
Product Allocation Detail BC Name |
Pharma Personal Products List |
Holds the name of the Product Allocation Detail BusComp name. |
Product Detail Fld Name |
Is Detail Active |
Holds the name of the field, which is used to construct the search specification to find out if the Products are active during creation of a call. |
Promo Item Dropped SearchSpec Fld Name |
Is Promo Item Active |
Holds the name of the field, which is used to construct the search specification to find out if the Promo Items are active during creation of a call. |
Required Fields on Best Lot BC |
Lot Name, Lot Id, Lot Expiry Date |
List of fields that needs to be set on LS Pharma My Sample Lots List BC. Lot Name, Lot Id, and Lot Expiry Date are the mandatory fields that needs to be set. Do not change. |
Sample Dropped SearchSpec Fld Name |
Is Sample Active |
Holds the name of the field, which is used to construct the search specification, to find out if the Samples are active during creation of a call. |
Sample Request SearchSpec Fld Name |
Is Sample Request Active |
Holds the name of the field, which is used to construct the search specification, to find out if the sample requests are active during the creation of a call. |
Set Smart Call Priority |
N |
If this user property is set to Y, use the priorities coming from the Smart Call. By default, this user property is set to N. |
LS Pharma Sample Transaction Admin Service User Properties
The following information lists the user properties that apply to LS Pharma Sample Transaction administration service.
Table User Properties for LS Pharma Sample Transaction Admin Service
| Name | Value | Description |
|---|---|---|
Business Object |
LS Pharma Sample Transactions |
Name of Business Object for Sample Transaction Administration. |
Personal Inventory BC |
LS Pharma Personal Inventory |
Name of Personal Inventory Business Component for Sample Transaction Administration. |
Pharma Call BC |
Pharma Professional Call |
Name of Pharma Call Business Component Sample Transaction Administration. |
Pharma Professional Call BC |
Pharma Professional Call |
Name of Pharma Professional Call Business Component Sample Transaction Administration. |
Sample Drop BC |
Pharma Call Sample |
Name of Pharma Sample Drop Business Component Sample Transaction Administration. |
Sample Transaction BC |
LS Pharma Sample Transactions |
Name of Pharma Sample Transaction Business Component Sample Transaction Administration. |
Sample Transaction Item BC |
LS Pharma Sample Transaction History Item |
Name of Pharma Sample Transaction Item Business Component Sample Transaction Administration. |
Sample Transaction Transfer In Item BC |
LS Pharma Sample Transfer In Item |
Name of Pharma Professional Call Business Component Sample Transaction Administration. |
LS Pharma Inventory Period Service User Properties
The following information lists the user properties that apply to LS Pharma Inventory Period service.
Table User Properties for LS Pharma Inventory Period Service
| Name | Value | Description |
|---|---|---|
Count: Business Object |
LS Pharma Inventory Audit Reports |
Name of Inventory Audit Report Business Object for Inventory Count. |
Count: Inventory Audit Report BC |
LS Pharma Inventory Audit Report |
Name of Inventory Audit Report Business Component for Inventory Count. |
Count: Inventory Period BC |
LS Pharma Inventory Period |
Name of Inventory Period Business Component for Inventory Count. |
Count: Personal Inventory BC |
LS Pharma Personal Inventory |
Name of Personal Inventory Business Component for Inventory Count. |
Reconciliation: Business Object |
LS Pharma Inventory Audit Reports |
Name of Business Object for Reconciliation. |
Reconciliation: Inventory Period BC |
LS Pharma Inventory Period |
Name of Inventory Period Business Component for Reconciliation. |
LS Pharma Inventory Administration Service User Properties
The following information lists the user properties that apply to LS Pharma Inventory Administration service.
Table User Properties for LS Pharma Inventory Administration Service
| Name | Value | Description |
|---|---|---|
Approval required: Close Out Count |
N |
Set this flag to Y or N to allow or disallow approval process for Close Out Inventory Count. |
Approval required: Disbursement |
Y |
Set this flag to Y or N to allow or disallow the approval process for Disbursement Adjustment. |
Approval required: Interim Count |
N |
Set this flag to Y or N to allow or disallow the approval process for Interim Inventory Count. |
Approval required: Inventory Adjustment |
Y |
Set this flag to Y or N to allow or disallow the approval process for Inventory Adjustment. |
Approval required: Location Inspection |
Y |
Set this flag to Y or N to allow or disallow the approval process for Location Audit. |
Approval required: Lost |
Y |
Set this flag to Y or N to allow or disallow the approval process for Sample Lost Adjustment. |
Approval required: Transfer In |
Y |
Set this flag to Y or N to allow or disallow the approval process for Received Samples adjustment. |
Approval required: Transfer Out |
Y |
Set this flag to Y or N to allow or disallow the approval process for Sent Samples Adjustment. |
Inventory Period Admin: Audit Report BC |
LS Pharma Audit Reports |
Name of Audit Report Business Component for Inventory Administration. |
Inventory Period Admin: Audit Report Item BC |
LS Pharma Audit Report Item |
Name of Audit Report Item Business Component for Inventory Administration. |
Inventory Period Admin: Business Object |
LS Pharma Audit Reports |
Name of Audit Report Business Object for Inventory Administration. |
Inventory Period Admin: Inventory Audit Report BC |
LS Pharma Inventory Audit Report |
Name of Inventory Audit Report Business Component for Inventory Administration. |
Inventory Period Admin: Inventory Period BC |
LS Pharma Inventory Period |
Name of Inventory Period Business Component for Inventory Administration. |
Inventory Period Admin: Personal Inventory BC |
LS Pharma Personal Inventory |
Name of Personal Inventory Business Component for Inventory Administration. |
Inventory Period Admin: Transaction Item History BC |
LS Pharma Sample Transaction History Item |
Name of Sample Transaction Item Business Component for Inventory Administration. |
Signature required: Close Out Count |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for Close Out Inventory Count. |
Signature required: Disbursement |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for Disbursement Adjustment. |
Signature required: Interim Count |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for the Interim Inventory Count. |
Signature required: Inventory Adjustment |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for Inventory Adjustment. |
Signature required: Location Inspection |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for the Location Audit. |
Signature required: Lost |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for the Sample Lost Adjustment. |
Signature required: Transfer In |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for Received Samples adjustment. |
Signature required: Transfer Out |
Y |
Set this flag to Y or N to allow or disallow the signature requirement for Sent Samples Adjustment. |
Siebel Pharma Business Component User Properties
Siebel Pharma uses the following business component user properties:
LS Pharma Call Promotional Items Dropped VBC - CE User Properties
LS Pharma Contact Assessment Attribute - CE BC User Properties
LS Pharma Contact Assessment Template - CE BC User Properties
LS Pharma Promotional Items Dropped Alloc VBC User Properties
LS Pharma Sample Transaction History Item BC User Properties
CSSBCActivity Class Business Component User Properties
The following information lists the user properties that are related to the Action (class CSSBCActivity) and Calendar (class CSSBCCalendar) business components.
Table User Properties Related to CSSBCActivity Class 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. |
CSSBCPharmaCall Class Business Component User Properties
The following information lists the user properties that are related to the following business components:
Pharma Account Call
Pharma Attendee Call
Pharma Template Call
Pharma Professional Call
Pharma Promotional Items Dropped
Pharma Professional 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. For example, Template Fields user property supports Pharma Promotional Items Dropped, Pharma Professional Call Sample Dropped, Pharma Activity Product Issues, and Pharma Call Sample Dropped. These BCs are not applicable to other user properties in the following table.Table User Properties Related to CSSBCPharmaCall Class Business Components
User Property Name User Property Value Description 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 Category is Attendee Call.
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.
Paper Reference Number Required
Y or N
If Y and the Paper Sign field is selected, then Ref # is a required field for call submission.
Applies to the Pharma Professional Call business component.
Sample Disbursed Required
Y or N
If Y, at least once sample must be disbursed before a call is submitted.
Applies to the Pharma Professional Call business component.
SRE Reference Number Required
Y or N
If Y and the signature is being captured electronically, Ref # is a required field for call submission.
Applies to the Pharma Professional Call business component.
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.
Update After Recreate Receipt
Last Name, Address, Start Date, Comment, Signature Captured
Value must start and end with a comma. You can add additional fields, but do not delete any of the default ones (preceding line).
Tells the business component what fields are editable after the user clicks Recreate Receipt.
Applies to the Pharma Professional Call business component.
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 the Siebel Mobile application for Siebel Pharma on a mobile device). Generally this user property should be used only to make the Comment field editable.
Validate Sample Ref #
Y or N
Tells the business component whether it should require a sample reference number when submitting a call.
LS Pharma Audit Signature BC User Properties
The following information lists the user properties that apply to the LS Pharma Audit Signature BC.
Table User Properties for LS Pharma Audit Signature BC
| Name | Value | Description |
|---|---|---|
Signature Header Text Field |
Calc Sign Header Text |
Field use by Signature header. |
Header Text Field: 2 |
Audit Completed Date |
Field used by Signature header. |
Header Text Field: 1 |
Owner Full Name |
Field used by Signature header. |
Checksum Field: 1 |
"Signature Header Text" |
Field used by Signature checksum. |
Checksum Field: 3 |
"Created By", "Created By" |
Field used by Signature checksum. |
Checksum Field: 2 |
"Signature Body Text" |
Field used by Signature checksum. |
Display About Box |
Y |
Disables the About box in the Signature Capture Dialog on the mobile device. |
Signature Date |
Y |
Enable Signature date. |
Signature Time |
Y |
Enable Signature time. |
Minimum Memory Required To Sign |
2500000 |
2.5 mega bytes. |
LS Pharma Call Products Detailed Alloc VBC User Properties
Virtual Business Components (VBC) are used to view data from an external system in Siebel Business Applications. Using this mechanism, no replication within the Siebel database is required.
The following information lists the user properties that apply to the LS Pharma Call Products Detailed Alloc Virtual Business Components (VBC).
Table User Properties for LS Pharma Call Products Detailed Alloc VBC
| Name | Value | Description |
|---|---|---|
Qty Field |
Priority |
Holds the name of the field to save from VBC to BC when a value of the field is modified or added. |
Copy Field 3 |
Name |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 4 |
Indication |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Source BusComp |
LS Pharma My Products List |
Holds the name of the parent Products BC, which is using to get the values for the VBC. |
Parent BusComp |
Pharma Call Products Detailed |
Holds the exact name of the parent Products Detailed BC. |
Copy Field 2 |
Product Allocation Id |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 1 |
Priority |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Query Field 1 |
Product Allocation Id |
Holds the name of the field to save from VBC to BC when a value for this field is modified or added. |
Qty Field 1 |
Indication |
Holds the name of the field to save from VBC to BC when a value of the field is modified or added. |
Copy Field 6 |
Alloc Start Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 7 |
Alloc End Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
LS Pharma Call Products Detailed VBC - CE User Properties
The following information lists the user properties that apply to the LS Pharma Call Products Detailed VBC - CE.
Table User Properties for LS Pharma Call Products Detailed VBC - CE
| Name | Value | Description |
|---|---|---|
Template Fields |
Name, Priority, Indication |
Specify the list of fields in the VBC which needs to be updated when a smart call template is applied to the call |
Sort Spec:Pharma Call Products Detailed - CE |
Product Id |
Specify the sort specification to be applied on the Call Product BC. |
VBC Field Map:Pharma Personal Products - CE |
Name, Product|Allocation Id, Id|Product Id, Product Id|Indication, Indication Other|Order By, Order By |
Specify the mapping between the VBC fields and the Personal Allocation BC fields. The mapping syntax is <VBC Field Name>, <Personal Allocation BC Field Name> [|<VBC Field Name>, <Personal Allocation BC Field Name>]. |
VBC Field Map:Pharma Call Products Detailed - CE |
Name, Name|Product Id, Product Id|Allocation Id, Allocation Id|Priority, Priority|Indication, Indication |
Specify the mapping between the VBC fields and the Call Product BC fields. The mapping syntax is <VBC Field Name>, <Call Product BC Field Name> [|<VBC Field Name>, <Call Product BC Field Name>]. |
Search Spec: Pharma Personal Products - CE |
[Start Date] <= '$StartDate$' AND([End Date] IS NULL OR [End Date] >= '$StartDate$') |
Specify the search spec to be applied on the Personal Allocation BC. $StartDate$ is the key word which will be replaced at run time with the actual call date. |
Personal Allocation BC |
Pharma Personal Products - CE |
Specify the name of the BC that holds information about the products allocated to the sales rep for detailing. |
Call Product BC |
Pharma Call Products Detailed - CE |
Specify the name of the BC that holds information about the products detailed in the call. |
LS Pharma Call Promotional Items Dropped VBC - CE User Properties
The following information lists the user properties that apply to the LS Pharma Call Promotional Items Dropped VBC - CE.
Table User Properties for LS Pharma Call Promotional Items Dropped VBC - CE
| Name | Value | Description |
|---|---|---|
VBC Field Map:Pharma Promotional Items Dropped - CE |
Name, Name|Product Id, Product Id|Allocation Id, Allocation Id|Quantity, Quantity |
Specify the mapping between the VBC fields and the Personal Allocation BC fields. The mapping syntax is <VBC Field Name>, <Personal Allocation BC Field Name> [|<VBC Field Name>, <Personal Allocation BC Field Name>]. |
VBC Field Map:Pharma Personal Promotional Items - CE |
Name, Promotional Item|Allocation Id, Id|Product Id, Product Id|Order By, Order By |
Specify the mapping between the VBC fields and the Call Product BC fields. The mapping syntax is <VBC Field Name>, <Call Product BC Field Name> [|<VBC Field Name>, <Call Product BC Field Name>]. |
Search Spec: Pharma Personal Promotional Items - CE |
[Start Date] <= '$StartDate$' AND([End Date] IS NULL OR [End Date] >= '$StartDate$') |
Specify the search spec to be applied on the Personal Allocation BC. $StartDate$ is the key word which will be replaced at run time with the actual call date. |
Template Fields |
Name, Quantity |
Specify the list of fields in the VBC which needs to be updated when a smart call template is applied to the call. |
Call Product BC |
Pharma Promotional Items Dropped - CE |
Specify the name of the BC that holds information about the promotional items dropped in the call. |
Personal Allocation BC |
Pharma Personal Promotional Items - CE |
Specify the name of the BC that holds information about the promotional items allocated to the sales rep for use in the calls. |
Sort Spec:Pharma Promotional Items Dropped - CE |
Product Id |
Specify the sort spec to be applied on the Call Product BC. |
LS Pharma Call Samples Dropped Alloc VBC User Properties
The following information lists the user properties that apply to the LS Pharma Call Samples Dropped Alloc VBC.
Table User Properties for LS Pharma Call Samples Dropped Alloc VBC
| Name | Value | Description |
|---|---|---|
Copy Field 4 |
Lot Name |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 3 |
Name |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 2 |
Product Allocation Id |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 1 |
Quantity |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 6 |
Alloc End Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Default Best Lots |
TRUE |
Holds the name of the field to populate from BC to VBC. |
Copy Field 5 |
Alloc Start Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Source BusComp |
LS Pharma My Sample Lots List |
Holds the name of the parent Samples Dropped BC, which is used to get the values for the VBC. |
Query Field 2 |
Lot Name |
Holds the name of the field to populate from BC to VBC. |
Query Field 1 |
Product Allocation Id |
Holds the name of the field to populate from BC to VBC. |
Parent BusComp |
Pharma Call Sample Dropped |
Holds the name of the parent Samples BC name. |
Qty Field |
Quantity |
Holds the name of the field to save from VBC to BC when a value of the field is modified or added. |
LS Pharma Call Samples Dropped VBC - CE User Properties
The following information lists the user properties that apply to the LS Pharma Call Samples Dropped VBC - CE.
Table User Properties for LS Pharma Call Samples Dropped VBC - CE
| Name | Value | Description |
|---|---|---|
Call Product BC |
Pharma Call Sample Dropped - CE |
Specify the name of the BC that holds information about the samples dropped in a call. |
Enable Best Lot Mode |
Y |
Specify Y to display only the available best lot against each sample else N. Best Lot is determined by the cut off date on the lot the cut off date must be greater than or equal to call date and the lot should not be expired. |
Personal Allocation BC |
Pharma Personal Samples - CE |
Specify the name of the BC that holds information about the samples allocated to the sales rep for use in the calls. |
Personal Inventory BC |
LS Pharma Personal Inventory - CE |
Specify the name of the BC that holds information about the sales rep personal inventory. |
Search Spec:LS Pharma Personal Inventory - CE |
([End Date] > '$StartDate$' OR [End Date] IS NULL) AND [Audit Report Id] IS NULL AND [Close Date] IS NULL |
Specify the search specification to be applied on the Personal Inventory BC. $StartDate$ is the key word which will be replaced at run time with the actual call date. |
Search Spec:Pharma Personal Samples - CE |
[Start Date] <= '$StartDate$' AND ([End Date] IS NULL OR [End Date] >= '$StartDate$') |
Specify the search specification to be applied on the Personal Allocation BC. $StartDate$ is the key word which will be replaced at run time with the actual call date. |
Sort Spec:LS Pharma Personal Inventory - CE |
Parent Product IdCutoff Threshold (DESCENDING)End Date |
Specify the sort specification to be applied on the Personal Inventory BC. |
Sort Spec:Pharma Personal Samples - CE |
Product Id |
Specify the sort specification to be applied on the Call Product BC. |
Template Fields |
NameQuantity |
Specify the list of fields in the VBC which needs to be updated when a smart call template is applied to the call. |
VBC Field Map:LS Pharma Personal Inventory - CE |
Lot Name Lot NameProductId Parent Product Id Internal Product Id Cutoff Threshold |
Specify the mapping between the VBC fields and the Personal Inventory BC fields. The mapping syntax is <VBC Field Name><Personal Allocation BC Field Name> [VBC Field Name><Personal Inventory BC Field Name>]. |
VBC Field Map:Pharma Call Sample Dropped - CE |
Allocation Id Allocation Name Id Product Quantity |
Specify the mapping between the VBC fields and the Call Product BC fields. The mapping syntax is <VBC Field Name><Call Product BC Field Name> [VBC Field Name><Call Product BC Field Name>]. |
VBC Field Map:Pharma Personal Samples - CE |
NameSampleAllocation Product Id Order By |
Specify the mapping between the VBC fields and the Personal Allocation BC fields. The mapping syntax is <VBC Field Name><Personal Allocation BC Field Name> [VBC Field Name><Personal Allocation BC Field Name>]. |
VBC Key Fields |
Allocation Id Lot Id |
Specify the name of the field names that holds the Id value. |
LS Pharma Call Samples Requested VBC - CE User Properties
The following information lists the user properties that apply to the LS Pharma Call Samples Requested VBC - CE.
Table User Properties for LS Pharma Call Samples Requested VBC - CE
| Name | Value | Description |
|---|---|---|
VBC Field Map:LS Pharma Call Samples Requested - CE |
Allocation Id, Allocation Id|Name, Name|Product Id, Product Id|Quantity, Quantity |
Specify the mapping between the VBC fields and the Call Product BC fields. The mapping syntax is <VBC Field Name>, <Call Product BC Field Name> [|<VBC Field Name>, <Call Product BC Field Name>]. |
VBC Field Map:LS Pharma Personal Sample Requests - CE |
Allocation Id, Id|Name, Sample|Product Id, Product Id|Order By, Order By |
Specify the mapping between the VBC fields and the Personal Allocation BC fields. The mapping syntax is <VBC Field Name>, <Personal Allocation BC Field Name> [|<VBC Field Name>, <Personal Allocation BC Field Name>]. |
Personal Allocation BC |
LS Pharma Personal Sample Requests - CE |
Specify the name of the business component that holds information about the direct send samples allocated to the sales rep for use in the calls. |
Call Product BC |
LS Pharma Call Samples Requested - CE |
Specify the name of the business component that holds information about the samples requested in a call. |
Search Spec: LS Pharma Personal Sample Requests - CE |
[Start Date] <= '$StartDate$' AND([End Date] IS NULL OR [End Date] >= '$StartDate$') |
Specify the search specification to be applied on the Personal Allocation BC. $StartDate$ is the key word which will be replaced at run time with the actual call date. |
Sort Spec:Pharma Personal Sample Requests - CE |
Product Id |
Specify the sort specification to be applied on the Call Product BC. |
Template Fields |
Name, Quantity |
Specify the list of fields in the VBC which needs to be updated when a smart call template is applied to the call. |
LS Pharma Call Signature Audit BC User Properties
The following information lists the user properties that apply to the LS Pharma Call Signature Audit BC.
Table User Properties for LS Pharma Call Signature Audit BC
| Name | Value | Description |
|---|---|---|
Header Text Field: 1 |
Contact Full Name |
Field used in Signature header. |
Header Text Field: 2 |
Title |
Field used in Signature header. |
Header Text Field: 3 |
Address |
Field used in Signature header. |
Header Text Field: 4 |
Call License # |
Field used in Signature header. |
Header Text Field: 5 |
License Number |
Field used in Signature header. |
Header Text Field: 6 |
Call DEA # |
Field used in Signature header. |
Header Text Field: 7 |
DEA# |
Field used in Signature header. |
Header Text Field: 8 |
Call Date Text |
Field used in Signature header. |
Header Text Field: 9 |
Call Date |
Field used in Signature header. |
Checksum Field: 1 |
"Signature Header Text" |
Field used in Signature checksum. |
Checksum Field: 2 |
"Signature Body Text" |
Field used in Signature checksum. |
Checksum Field: 3 |
"Created By", "Created By" |
Field used in Signature checksum. |
Named Method 1 |
MakeMasterSignature", "INVOKESVC", "LS Pharma Call Signature Audit", "LS Pharma Signature Utility Service", "MakeMasterSignature", "'Signature Id'", "[Id]" |
Named Method used for Make Master button on the Signature Audit view. |
Named Method 3 |
"ClearAuditFlags", "INVOKESVC", "LS Pharma Call Signature Audit", "LS Pharma Signature Utility Service", "ClearAuditFlags" |
Named Method used for Clear Audit Flags button on the Signature Audit view. |
LS Pharma Contact Assessment Attribute - CE BC User Properties
The following information lists the user properties that apply to the LS Pharma Contact Assessment Attribute - CE BC.
Table User Properties for LS Pharma Contact Assessment Attribute - CE
| Name | Value | Description |
|---|---|---|
Deep Delete |
Sales Assessment Attribute Value |
Deletes the attribute values when the Assessment Values are deleted. |
Sequence Field |
Order |
Used in the Code for Usability feature. |
LS Pharma Contact Assessment Template - CE BC User Properties
The following information lists the user properties that apply to the LS Pharma Contact Assessment Template - CE BC.
Table User Properties for LS Pharma Contact Assessment Template - CE
| Name | Value | Description |
|---|---|---|
Deep Delete1 |
LS Pharma Contact Assessment Attribute - CE |
Deletes the attribute values when the Assessment Values are deleted. |
Deep Copy1 |
LS Pharma Contact Assessment Attribute - CE |
Copies the attribute values when the Assessment Values are copied. |
LS Pharma Disclaimer Rule Set BC User Properties
The following information lists the user properties that apply to the LS Pharma Disclaimer Rule Set BC.
Table User Properties for LS Pharma Disclaimer Rule Set BC
| Name | Value | Description |
|---|---|---|
Active Field |
Is Editable |
Field used to control whether you can edit a BC or not. |
BC Field Profile Attribute 1 |
Pharma Call, "LS Pharma.Call.BCFieldProfessionalType", "Pharma Professional Call", "Professional Type" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. |
BC Field Profile Attribute 2 |
Pharma Call, "LS Pharma.Call.BCFieldPrimarySpecialty", "Pharma Professional Call", "Primary Specialty" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. |
BC Field Profile Attribute 3 |
Pharma Call, "LS Pharma.Call.BCFieldState", "Pharma Professional Call", "State" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. |
BC Field Profile Attribute 4 |
Inventory Audit, "LS Pharma.Inventory Audit.BCFieldAuditReportCategory", "LS Pharma Audit Reports", "Category LIC" |
Profile Attribute defined for Inventory Audit type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. |
BC Field Profile Attribute 5 |
Pharma Call, "LS Pharma.Call.BCFieldRecreatedFlag", "Pharma Call Signature", "Recreated Flag" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. |
Child BC Field Profile Attribute 1 |
Pharma Call, "LS Pharma.Call.ChildBCFieldControlledSubstance", "Pharma Call Sample Dropped", "Controlled Substance" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. Usually the BusComp is the child BC of the entity that requires a Signature. |
Child BC Field Profile Attribute 2 |
Pharma Call, "LS Pharma.Call.ChildBCFieldProductName", "Pharma Call Sample Dropped", "Name" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part and fourth part are the BC name and Field name where the Profile Attribute Value comes from. Usually the BusComp is the child BC of the entity that requires a Signature. |
Child BC Row Profile Attribute 3 |
Pharma Call, "LS Pharma.Call.IsProductDetailed", "Pharma Call Products Detailed" |
Profile Attribute defined for Pharma Call type Dynamic Disclaimer. The first part of the Value is the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Profile Attribute. The third part is the name of the BC that is queried to decide if there is any record in it. |
Disclaimer Rule Set Type 1 |
Pharma Call, "LS Pharma Call Signature Form Applet" |
This user property defines the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Applet that will be used to capture the signature for the current type. |
Disclaimer Rule Set Type 2 |
Txn Adjustment, "LS Pharma Txn Adjustment Signature Form Applet" |
This user property defines the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Applet that will be used to capture the signature for the current type. |
Disclaimer Rule Set Type 3 |
Inventory Audit, "LS Pharma Signature Capture Form Applet" |
This user property defines the type of the Signature that the Dynamic Disclaimer will be applied to, corresponding to the Sub-Type of the Disclaimer. The second part is the name of the Applet that will be used to capture the signature for the current type. |
Field Read Only Field: Description |
Is Read Only |
Field used to control whether you can edit the field 'Description'. |
Field Read Only Field: Name |
Is Read Only |
Field used to control whether you can edit the field 'Name'. |
Field Read Only Field: Rule Set Type |
Is Read Only |
Field used to control whether you can edit the field 'Rule Set Type'. |
Named Method 1 |
ActivateDisclaimerRuleSet, "INVOKESVC", "LS Pharma Disclaimer Rule Set", "LS Pharma Signature Utility Service", "ActivateDisclaimerRuleSet", "'Rule Set Id'", "[Id]" |
Named Method used for Activate button on the Disclaimer Rule Set view. |
LS Pharma Inventory Audit Report BC User Properties
The following information lists the user properties that apply to the LS Pharma Inventory Audit Report BC.
Table User Properties for LS Pharma Inventory Audit Report BC
| Name | Value | Description |
|---|---|---|
Named Method 2 |
"Reject", "INVOKESVC", "LS Pharma Inventory Audit Report", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma Inventory Audit Rejection", "'RowId'", "[Id]" |
Call Business Service to reject report. |
Named Method 3 |
"Reject", "INVOKE", "LS Pharma Inventory Audit Report", "RefreshBusComp" |
Refresh Business Component. |
Named Method 1 |
"Approve", "INVOKE", "LS Pharma Inventory Audit Report", "RefreshBusComp" |
Refresh Business Component. |
LOY CanInvokeMethod 2 |
"Reject", "CanSubmit" |
Disable the Reject button after record is submitted. |
LS Pharma Inventory Period User Properties
The following information lists the user properties that apply to the LS Pharma Inventory Period BC.
Table User Properties for LS Pharma Inventory Period
| Name | Value | Description |
|---|---|---|
Acceptable Period to Complete Synchronization |
20 |
The mobile device must be successfully synchronized to the laptop with this time, unit is minutes. |
Inventory Closure Validation |
N |
Used to perform validation for Reconciliation. |
Named Method 3 |
"CloseoutCount", "INVOKE", "LS Pharma Inventory Period", "RefreshBusComp" |
Refresh Business Component. |
Named Method 5 |
"AckNewPeriod", "INVOKE", "LS Pharma Inventory Period", "RefreshBusComp" |
Refresh Business Component. |
Named Method 2 |
"CloseoutCount", "INVOKESVC", "LS Pharma Inventory Period", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma CloseOut Ineventory Count", "'Submit to Id'", "[Approved by Id]", "'RowId'", "[Id]", "'Owner Id'", "[Owned By Id]" |
Call Business Service to create closeout count report. |
Named Method 1 |
"InterimCount", "INVOKE", "LS Pharma Inventory Period", "RefreshBusComp" |
Refresh Business Component. |
Field Read Only Field: Approver Full Name |
ReadOnly Flag |
Reviewer field control flag. |
Maximum Periods |
2 |
Limits the number of unreconciled periods including active period. |
LOY CanInvokeMethod 3 |
"AckNewPeriod", "CanAck" |
Acknowledge control flag. |
LOY CanInvokeMethod 1 |
"InterimCount", "CanCount" |
Interim Count control flag. |
LOY CanInvokeMethod 2 |
"CloseoutCount", "CanCloseOutCount" |
Disable Closeout after record is submitted. |
Named Method 4 |
"AckNewPeriod", "INVOKESVC", "LS Pharma Inventory Period", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma Inventory Audit Acknowledgement", "'RowId'", "[Id]", "'Owner Id'", "[Owned By Id]" |
Call Business Service to acknowledge new inventory period. |
LS Pharma Inventory Period Reconciliation BC User Properties
The following information lists the user properties that apply to the LS Pharma Inventory Period Reconciliation BC.
Table User Properties for LS Pharma Inventory Period Reconciliation
| Name | Value | Description |
|---|---|---|
Maximum Periods |
2 |
Limits the number of unreconciled periods including active period. |
Inventory Closure Validation |
N |
Used in validation for Reconciliation. |
Field Read Only Field: Approver Full Name |
ReadOnly Flag |
Reviewer field control flag. |
LS Pharma Location Audit Report BC User Properties
The following information lists the user properties that apply to the LS Pharma Location Audit Report BC.
Table User Properties for LS Pharma Location Audit Report BC
| Name | Value | Description |
|---|---|---|
LOY CanInvokeMethod 3 |
"RejectLocationAudit", "CanApprove" |
Reject control flag. |
LOY CanInvokeMethod 1 |
"SubmitLocationAudit", "CanSubmit" |
Submit control flag. |
Named Method 4 |
"ApproveLocationAudit", "INVOKE", "LS Pharma Location Audit Report", "RefreshBusComp" |
Refresh Business Component. |
Named Method 3 |
"ApproveLocationAudit", "INVOKESVC", "LS Pharma Location Audit Report", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma Location Audit Approval", "'RowId'", "[Id]" |
Call Business Service to approve location audit report. |
Named Method 1 |
"SubmitLocationAudit", "INVOKESVC", "LS Pharma Location Audit Report", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma Location Audit Submit", "'Submit to Id'", "[Approved by Id]", "'RowId'", "[Id]", "'Owner Id'", "[Owned By Id]" |
Call Business Service to submit location audit report. |
Named Method |
"SubmitLocationAudit", "INVOKE", "LS Pharma Location Audit Report", "WriteRecord" |
Force write record. |
Named Method 6 |
"RejectLocationAudit", "INVOKE", "LS Pharma Location Audit Report", "RefreshBusComp" |
Refresh Business Component. |
LOY CanInvokeMethod 2 |
"ApproveLocationAudit", "CanApprove" |
Approve control flag. |
Field Read Only Field: Status |
ReadOnly Flag |
Set field read only according to the status. |
Field Read Only Field: Type |
ReadOnly Flag |
Set field read only according to the status. |
Field Read Only Field: Submitted to |
ReadOnly Flag |
Set field read only according to the status. |
Field Read Only Field: Owned By Id |
ReadOnly Flag |
Set field read only according to the status. |
Report Field Read Only Field: Owned By |
ReadOnly Flag |
Set field read only according to the status. |
Field Read Only Field: Completed Date |
ReadOnly Flag |
Set field read only according to the status. |
Field Read Only Field: Approved by Id |
ReadOnly Flag |
Set field read only according to the status. |
Aspect Child BC ReadOnly: APPROVAL |
ReadOnly Flag |
Set field read only according to the status. |
Named Method 5 |
"RejectLocationAudit", "INVOKESVC", "LS Pharma Location Audit Report", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Audit Reports", "'BC Name'", "LS Pharma Audit Reports", "'ProcessName'", "LS Pharma Location Audit Rejection", "'RowId'", "[Id]" |
Call Business Service to reject location audit report. |
LS Pharma Promotional Items Dropped Alloc VBC User Properties
The following information lists the user properties that apply to the LS Pharma Promotional Items Dropped Alloc VBC.
Table User Properties for LS Pharma Promotional Items Dropped Alloc VBC
| Name | Value | Description |
|---|---|---|
Copy Field 1 |
Quantity |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Source BusComp |
LS Pharma My Promotional Items List |
Holds the name of the parent Promotional Items BC, which is used to get the values for the VBC. |
Copy Field 5 |
Alloc End Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 2 |
Product Allocation Id |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Parent BusComp |
Pharma Promotional Items Dropped |
Holds the name of the parent Promotional Items BC name. |
Copy Field 4 |
Alloc Start Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Query Field 1 |
Product Allocation Id |
Holds the name of the field to Save from VBC to BC when the Value for this field is added or modified. |
LS Pharma Samples Request BC User Properties
The following information lists the user properties that apply to the LS Pharma Samples Request BC.
Table User Properties for LS Pharma Samples Request BC
| Name | Value | Description |
|---|---|---|
Signature Body Text Field: 2 |
Name |
Copied from Pharma Call Sample Dropped - CE for signature verification. |
Signature Body Text Field: 3 |
Vendor Name |
Copied from Pharma Call Sample Dropped - CE for signature verification. |
Signature Body Text Field: 1 |
Quantity |
Copied from Pharma Call Sample Dropped - CE for signature verification. |
Template Fields |
Name, Quantity |
Fields to copy from the visit template. |
Parent Read Only Field |
Pharma Template Call.Is Not Creator |
Disables the Add button when the Contact is not a valid Professional. |
Copy Field 3 |
Name |
Holds the name of the field to populate from BC to VBC. |
Copy Field 5 |
Alloc End Date |
Holds the name of the field to populate from BC to VBC. |
Copy Field 4 |
Alloc Start Date |
Holds the name of the field to populate from BC to VBC. |
Copy Field 2 |
Product Allocation Id |
Holds the name of the field to populate from BC to VBC. |
LS Pharma Samples Request VBC User Properties
The following information lists the user properties that apply to the LS Pharma Samples Request VBC.
Table User Properties for LS Pharma Samples Request VBC
| Name | Value | Description |
|---|---|---|
Query Field 1 |
Product Allocation Id |
Holds the name of the field to populate from BC to VBC. |
Source BusCom |
LS Pharma My Direct Send Samples List |
Holds the name of the parent Samples Requested BusComp, which is using to get the proper values for the VBC. |
Qty Field |
Quantity |
Holds the name of the field to save from VBC to BC when the value for this field is added or modified. |
Parent BusComp |
LS Pharma Samples Request BC |
Holds the name of the parent Sample Requested BusComp name. |
Copy Field 1 |
Quantity |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 3 |
Name |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 5 |
Alloc End Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 4 |
Alloc Start Date |
Holds the name of the field to populate from Source BusComp to this VBC and to copy from VBC to Parent BusComp. |
Copy Field 2 |
Product Allocation Id |
Holds the name of the field to populate from BC to VBC. |
LS Pharma Personal Inventory BC User Properties
The following information lists the user properties that apply to the LS Pharma Personal Inventory BC.
Table User Properties for LS Pharma Personal Inventory BC
| Name | Value | Description |
|---|---|---|
Field Read Only Field: Client Quantity |
Count ReadOnly |
Quantity read only field according to parent status. |
LS Pharma Sample Received History Item BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Received History Item BC.
Table User Properties for LS Pharma Sample Received History Item BC
| Name | Value | Description |
|---|---|---|
Field Read Only Field: Quantity |
[Reconciled Flag] |
Quantity field readonly if parent inventory period is reconciled. |
Named Method |
"RefreshParent", "INVOKE", "LS Pharma Sample Transactions", "RefreshBusComp" |
Refresh Parent Business Component. |
Parent Read Only Field |
LS Pharma Sample Transactions.ReadOnly Flag |
Read only field according to the parent status. |
On Field Update Set |
"Requested Quantity", "Quanitiy", "IIF([Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Disbursement') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Return') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Transfer Out') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Loss'), [Requested Quantity] * -1,[Requested Quantity] )" |
Correct quantity value according to the transaction type. |
LS Pharma Sample Transaction History Item BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Transaction History Item BC.
Table User Properties for LS Pharma Sample Transaction History Item BC
| Name | Value | Description |
|---|---|---|
Field Read Only Field: Quantity |
[Reconciled Flag] |
Quantity read only field if parent inventory period is reconciled. |
Named Method |
"RefreshParent", "INVOKE", "LS Pharma Sample Transactions", "RefreshBusComp" |
Refresh parent business component. |
Parent Read Only Field |
ReadOnly Flag |
Read only according to the parent status. |
Field Read Only Field: Lot Name |
Adjusted Flag |
Disable Product picklist if transaction is adjusted. |
Field Read Only Field: Product |
Adjusted Flag |
Disable Product picklist if transaction is adjusted. |
On Field Update Set |
"Requested Quantity", "Quanitiy", "IIF([Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Disbursement') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Return') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Transfer Out') OR [Txn Type] = LookupValue('SAMPLE_TXN_TYPE','Loss'), [Requested Quantity] * -1,[Requested Quantity] )" |
Correct quantity value according to the transaction type. |
LS Pharma Sample Transactions BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Transactions BC.
Table User Properties for LS Pharma Sample Transactions BC
| Name | Value | Description |
|---|---|---|
Named Method 2 |
"Reject", "INVOKESVC", "LS Pharma Sample Transactions", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Sample Transactions", "'BC Name'", "LS Pharma Sample Transactions", "'ProcessName'", "LS Pharma Reject Sample Transaction", "'RowId'", "[Id]" |
Readonly according to the parent status.Call Business Service to reject sample adjustment. |
Field Read Only Field: Due Date |
Lock Period Flag |
Transaction date control flag. |
Field Read Only Field: Owned By Full Name |
Is Owner Adjusted |
Disable field according to the control field. |
Field Read Only Field: Owned By Id |
Is Owner Adjusted |
Disable field according to the control field. |
Field Read Only Field: Quote Number |
Is Adjustment Flag |
Disable field according to the control field. |
Named Method 3 |
"Reject", "INVOKE", "LS Pharma Sample Transactions", "RefreshBusComp" |
Refresh business component. |
Named Method 1 |
"Approve", "INVOKE", "LS Pharma Sample Transactions", "RefreshBusComp" |
Refresh business component. |
Field Read Only Field: Transfer By Id |
Is Adjustment Flag |
Disable field according to the control field. |
Field Read Only Field: Transfer By Full Name |
Is Adjustment Flag |
Disable field according to the control field. |
Field Read Only Field: Submit to |
No Approval Flag |
Disable field according to the control field. |
Field Read Only Field: Stock Period |
Is Adjustment Flag |
Disable field according to the control field. |
Field Read Only Field: Stock Id |
Is Adjustment Flag |
Disable field according to the control field. |
Field Read Only Field: Arrival Date |
Transfer In ReadOnly Flag |
Disable field according to the control field. |
Field Read Only Field: Approved by Id |
Is Adjustment Flag |
Disable field according to the control field. |
Deep Delete 3 |
LS Pharma Sample Txn Signature |
Enable deep delete on child business component. |
Deep Delete 2 |
LS Pharma Sample Transactions Attachment |
Enable deep delete on child business component. |
Deep Delete 1 |
LS Pharma Sample Transaction History Item |
Enable deep delete on child business component. |
Deep Copy 2 |
LS Pharma Sample Transactions Attachment |
Enable deep copy on child business component. |
Deep Copy 1 |
LS Pharma Sample Transaction History Item |
Enable deep copy on child business component. |
Aspect BC NoInsert: Disbursement |
Disbursement Flag |
Disable insert for Sample Disbursement. |
Named Method |
"Approve", "INVOKESVC", "LS Pharma Sample Transactions", "LS Pharma Inventory Administration Service", "RunProcess", "'BO Name'", "LS Pharma Sample Transactions", "'BC Name'", "LS Pharma Sample Transactions", "'ProcessName'", "LS Pharma Approve Sample Transaction", "'RowId'", "[Id]" |
Call Business Service to approve sample adjustment. |
Aspect BC ReadOnly |
Aspect Child BC ReadOnly |
Used to control access in normal and admin view. |
Aspect BC NoInsert: Disbursement |
Disbursement Flag |
Used to control No Insert Disbursement in normal view. |
Aspect BC NoInsert: Disbursement Admin |
Disbursement Flag |
Used to control No Insert Disbursement in admin view. |
Aspect BC ReadOnly: Adjustment |
Admin Adjusted Flag |
Used to control Adjustment in normal view. |
Aspect BC ReadOnly: Adjustment Admin |
User Adjusted Flag |
Used to control Adjustment in admin view. |
Aspect BC ReadOnly: Disbursement |
Admin Adjusted Flag |
Used to control Disbursement in normal view. |
Aspect BC ReadOnly: Disbursement Admin |
User Adjusted Flag |
Used to control Disbursement in admin view. |
Aspect BC ReadOnly: Lost |
Admin Adjusted Flag |
Used to control Lost in normal view. |
Aspect BC ReadOnly: Lost Admin |
User Adjusted Flag |
Used to control Lost in admin view. |
Aspect BC ReadOnly: Return |
Admin Adjusted Flag |
Used to control Return in normal view. |
Aspect BC ReadOnly: Return Admin |
User Adjusted Flag |
Used to control Return in admin view. |
Aspect BC ReadOnly: Transfer In |
Admin Adjusted Flag |
Used to control Transfer In in normal view. |
Aspect BC ReadOnly: Transfer In Admin |
User Adjusted Flag |
Used to control Transfer In in admin view. |
Aspect BC ReadOnly: Transfer Out |
Admin Adjusted Flag |
Used to control Transfer Out in normal view. |
Aspect BC ReadOnly: Transfer Out Admin |
User Adjusted Flag |
Used to control Transfer Out in admin view. |
Aspect Child BC ReadOnly: Adjustment |
Admin Adjusted Flag |
Used to control child Adjustment in normal view. |
Aspect Child BC ReadOnly: Adjustment Admin |
User Adjusted Flag |
Used to control child Adjustment in admin view. |
Aspect Child BC ReadOnly: Disbursement |
Admin Adjusted Flag |
Used to control child Disbursement in normal view. |
Aspect Child BC ReadOnly: Disbursement Admin |
User Adjusted Flag |
Used to control child Disbursement in admin view. |
Aspect Child BC ReadOnly: Lost |
Admin Adjusted Flag |
Used to control child Lost in normal view. |
Aspect Child BC ReadOnly: Lost Admin |
User Adjusted Flag |
Used to control child Lost in admin view. |
Aspect Child BC ReadOnly: Return |
Admin Adjusted Flag |
Used to control child Return in normal view. |
Aspect Child BC ReadOnly: Return Admin |
User Adjusted Flag |
Used to control child Return in admin view. |
Aspect Child BC ReadOnly: Transfer In |
Admin Adjusted Flag |
Used to control child Transfer In in normal view. |
Aspect Child BC ReadOnly: Transfer In Admin |
User Adjusted Flag |
Used to control child Transfer In in admin view. |
Aspect Child BC ReadOnly: Transfer Out |
Admin Adjusted Flag |
Used to control child Transfer Out in normal view. |
Aspect Child BC ReadOnly: Transfer Out Admin |
User Adjusted Flag |
Used to control child Transfer Out in admin view. |
Copy Source Field |
[Source Txn Id] |
Used to copy source transactions. |
LS Pharma Sample Transactions Attachment BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Transactions Attachment BC.
Table User Properties for LS Pharma Sample Transactions Attachment BC
| Name | Value | Description |
|---|---|---|
Parent Read Only Field |
LS Pharma Sample Transactions.Adjusted Flag |
Read only according to the parent status. |
FileMustExist |
TRUE |
Validate file existence for attachments. |
DefaultPrefix |
SampTxn |
Attachment internal file prefix. |
LS Pharma Sample Transfer In Item BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Transfer In Item BC.
Table User Properties for LS Pharma Sample Transfer In Item BC
| Name | Value | Description |
|---|---|---|
Field Read Only Field: Product |
Updated Flag |
Disable product change after saved. |
Named Method |
"RefreshParent", "INVOKE", "LS Pharma Sample Transactions", "RefreshBusComp" |
Call Business Service to refresh sample transaction. |
Parent Read Only Field: LS Pharma Sample Transactions |
Transfer In ReadOnly Flag |
Read only according to the parent status. |
Field Read Only Field: Lot Name |
Updated Flag |
Disable lot change after saved. |
LS Pharma Samples Attachment BC User Properties
The following information lists the user properties that apply to the LS Pharma Samples Attachment BC.
Table User Properties for LS Pharma Samples Attachment BC
| Name | Value | Description |
|---|---|---|
DefaultPrefix |
Audit |
Attachment internal file prefix. |
FileMustExist |
TRUE |
Validate file existence for attachments. |
LS Pharma Sample Txn Signature BC User Properties
The following information lists the user properties that apply to the LS Pharma Sample Txn Signature BC.
Table User Properties for LS Pharma Sample Txn Signature BC
| Name | Value | Description |
|---|---|---|
Minimum Memory Required To Sign |
2500000 |
2.5 mega bytes. |
Header Text Field: 2 |
Audit Completed Date |
Field used by Signature header. |
Header Text Field: 1 |
Owner Full Name |
Field used by Signature header. |
Checksum Field: 1 |
"Signature Header Text" |
Field used by Signature checksum. |
Checksum Field: 3 |
"Created By", "Created By" |
Field used by Signature checksum. |
Checksum Field: 2 |
"Signature Body Text" |
Field used by Signature checksum. |
Display About Box |
Y |
Disables the About box in the Signature Capture Dialog on the mobile device. |
Signature Date |
Y |
Enable Signature date. |
Signature Time |
Y |
Enable Signature time. |
Pharma Account Call BC User Properties
The following information lists the user properties that apply to the Pharma Account Call BC.
Table User Properties for Pharma Account Call BC
| Name | Value | Description |
|---|---|---|
Named Method 1 |
"Sign","INVOKESVC", "Pharma Account Call", "LS Pharma Call Utility Service", "Sign" |
Invokes this method when the user clicks Sign. |
Named Method 4 |
"GotoDetails", "INVOKESVC", "Pharma Account Call", "LS Pharma Call Utility Service", "GotoDetails" |
Invokes this method when the user clicks New Call. |
Named Method 2 |
"Submit", "INVOKESVC", "Pharma Account Call", "LS Pharma Call Utility Service", "Submit" |
Invokes this method when the user clicks Submit. |
Named Method 3 |
"Validate", "INVOKESVC", "Pharma Account Call", "LS Pharma Validation Engine Service", "Validate" |
This method validates the call. |
Refresh BC List |
LS Pharma Call Products Detailed VBC - CE |
Holds the list of visual business component names that needs to be refreshed. |
Submit Call Copy From Field 1 |
Start Date |
Name of the Call Date field to copy back to the Position BC, when submitting the Call. |
Submit Call Copy From Field 2 |
Next Call Date |
Name of the Next Call Date field to copy back to the Position BC, when submitting the Call. |
Submit Call Parent Field Id |
Account Id |
Name of the field to set the Id for the Call. |
Submit Call Copy From Field 3 |
Next Call Objective |
Name of the Next Call Objective field to copy back to the Position BC,when submitting the Call. |
Submit Call Copy To Field 1 |
Pharma Last Account Call Date |
Name of the field setting in the Position BC, when submitting the Call. |
Submit Call Copy To Field 2 |
LS Pharma Account Next Call Date |
Name of the field setting in the Position BC, when submitting the Call. |
Submit Call Copy To Field 3 |
LS Pharma Account Next Call Obj |
Name of the field setting in the Position BC, when submitting the Call. |
Validation Results View |
LS Pharma Account Call Validation Results View - CE |
Holds the name of the view which displays the validation results. |
Pharma Call Products Detailed - CE BC User Properties
The following information lists the user properties that apply to the Pharma Call Detailed - CE BC.
Table User Properties for Pharma Call Detailed - CE
| Name | Value | Description |
|---|---|---|
CleanUp Search Spec |
[Priority] <= 0 |
Used to specify the condition on when the clean up on the search specification has to be done on the call product detail BC. |
Pharma Call Products Detailed - CE User Properties
The following information lists the user properties that apply to the Pharma Call Detailed - CE BC.
Table User Properties for Pharma Call Detailed - CE
| Name | Value | Description |
|---|---|---|
CleanUp Search Spec |
[Priority] <= 0 |
Specifies the condition when the clean up on the search specification needs to be done. |
Pharma Call Sample Dropped - CE User Properties
The following information lists the user properties that apply to the Pharma Call Detailed - CE BC.
Table User Properties for Pharma Call Detailed - CE
| Name | Value | Description |
|---|---|---|
CleanUp Search Spec |
[Priority] <= 0 |
Specifies the condition when the clean up on the search specification needs to be done. |
Pharma Call Samples Requested - CE User Properties
The following information lists the user properties that apply to the Pharma Call Samples Requested - CE.
Table User Properties for Pharma Call Samples Requested - CE
| Name | Value | Description |
|---|---|---|
Signature Body Text Field: 3 |
Vendor Name |
Holds the field name that is used in the signature body text. |
CleanUp Search Spec |
[Quantity] <= 0 |
Specify the condition when the clean up has to be done on the sample request BC. |
Parent PickList FieldName |
Name |
Holds the picklist field name to get field value. |
Skip Conflict Resolution For Duplicate Records |
Y |
Default value is set to Y. During synchronization, if the object manager encounters a duplicate record, it drops the record from the device and keep a record on the Siebel server. |
Update After Recreate Receipt |
Name, Quantity |
Holds the list of field names that has to be updated after the receipt has been recreated. |
Template Fields |
Name, Lot Name, Quantity |
Holds the list of field names that needs to be copied the visit template. |
Signature Body Text Field: 2 |
Name |
Holds the field name that is used in the signature body text. |
Validate PickMaps in Extended Pick Mode |
N |
Holds either Y or N. Value equals Y for turning on the PickMaps validation. |
Signature Body Text Field: 1 |
Quantity |
Holds the field name that is used in the signature body text. |
Pharma GA Call Products Detailed User Properties
The following information lists the user properties that apply to the class CSSBCProductDetailed.
Table 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. |
Pharma Professional Call BC User Properties
The following information lists the user properties that apply to the Pharma Professional Call BC.
Table User Properties for Pharma Professional Call BC
| Name | Value | Description |
|---|---|---|
SuppressSubmitConfirmation |
N |
Added to suppress confirmation dialog box when submitting a call. |
Deep Copy 2 |
LS Pharma Samples Request BC |
Copies the Sample Requests when the user clicks New Sample Drop. |
Named Method 3 |
"LSCopyFieldValue", "INVOKE", "Pharma Call Sample Dropped", "LSCopyFieldValue" |
Invoked the BS method on Promo Item BC. |
Named Method 4 |
"LSCopyFieldValue", "INVOKE", "Pharma Promotional Items Dropped", "LSCopyFieldValue" |
Invoked the BS method on Promo Item BC. |
Named Method 5 |
"LSCopyFieldValue", "INVOKE", "LS Pharma Samples Request BC", "LSCopyFieldValue" |
Invoked the BS method on Sample Request BC. |
Required Fields: Contact Call |
- |
Holds the list of call record fields required to be populated before submitting a Contact Call. |
Required Fields: Accounts Contact Call |
- |
Holds the list of call record fields required to be populated before submitting Accounts Contact Call. |
Submit Call Copy From Field 1 |
Call Date |
Name of the Call Date field to copy back to the Position BC when submitting the Call. |
Submit Call Copy From Field 2 |
Next Call Date |
Name of the Next Call Date field to copy back to the Position BC when submitting the Call. |
Submit Call Copy From Field 3 |
Next Call Objective |
Name of the Next Call Objective field to copy back to the Position BC when submitting the Call. |
Submit Call Copy To Field 1 |
Pharma Last Professional Call Date |
Name of the field setting in the Position BC, when submitting the Call. |
Submit Call Copy To Field 2 |
Pharma Last Professional Next Call Date |
Name of the field setting in the Position BC, when submitting the Call. |
Submit Call Copy To Field 3 |
Pharma Last Professional Next Call Obj |
Name of the field setting in the Position BC, when submitting the Call. |
Submit Call Parent Field Id |
Contact Id |
Name of the field to set the Id for the Call. |
Pharma Professional Call - CE BC User Properties
The following information lists the user properties that apply to the Pharma Professional Call - CE BC.
Table User Properties for Pharma Professional Call - CE
| Name | Value | Description |
|---|---|---|
Validation Results View |
LS Pharma Contact Call Validation Results View - CE |
Holds the name of the view which displays the validation results. |
Sampling Rules |
CONTACT SAMPLING RULE, EMPLOYEE SAMPLING RULE, SRE PROFESSIONAL RULE |
Each rule specified in the user property is evaluated using the validation engine. |
Refresh BC List |
LS Pharma Call Samples Dropped VBC - CE, LS Pharma Call Samples Requested VBC - CE, LS Pharma Call Promotional Items Dropped VBC - CE, LS Pharma Call Products Detailed VBC - CE |
Holds the list of visual business component names that needs to be refreshed. |
Template Components |
LS Pharma Call Samples Dropped VBC - CE, LS Pharma Call Samples Requested VBC - CE, LS Pharma Call Products Detailed VBC - CE, LS Pharma Call Promotional Items Dropped VBC - CE |
Holds the list of component names which has to be copied from call template. |
Pharma Promotional Items Dropped - CE User Properties
The following information lists the user properties that apply to the Pharma Promotional Items Dropped - CE BC.
Table User Properties for Pharma Promotional Items Dropped - CE
| Name | Value | Description |
|---|---|---|
CleanUp Search Spec |
[Priority] <= 0 |
Specifies the condition when the clean up on the search specification needs to be done. |
Action BC User Properties
The following information lists the user properties that apply to and are defined in the standard Action BC. These user properties are involved in the display of activities in home page calendar applets such as the eCalendar Daily Applet Home Page (which is based on the CSSSWEFrameCalGridLS class).
Table User Properties for Action BC
| Name | Value | Description |
|---|---|---|
LS Calendar Tooltip Field |
LS Calendar Tooltip
Note: This is a calculated field.
|
Specifies the field name used to display the tooltip in the calendar applet. |
LS Calendar Display Text Field |
LS Calendar Display Text
Note: This is a calculated field.
|
Specifies the field name used to display the text in the calendar applet. |
LS Calendar Icon Field |
LS Calendar Icon
Note: This is a calculated field.
|
Specifies the field name used to display the icon in the calendar applet. |