Setting Up Structured Product Messaging Dynamic Page Layouts
The Messaging Plan, Messaging Plan Item, Messaging Plan Item Relation, and Message Response record types are collectively referred to as the personal content delivery (PCD) record types. Your company can repurpose the PCD record types to support structured product messaging (SPM), which allows users to manage their sales call objectives. You repurpose the PCD record types by defining dynamic page layouts for these records. By appropriately selecting the Type picklist field for a PCD record, an end user can dynamically change the page layout corresponding to the PCD record that is in place. For example, selecting Type with a value of Call Objective changes the page layout for a Messaging Plan Item to a Call Objective page layout.
The SPM page layouts that correspond to the PCD record types are: Call Objective Plan (for Messaging Plan), Call Objective (for Messaging Plan Item), Next Call Objective (for Messaging Plan Item Relations), and Outcome (for Message Response). Typically, a sales representative uses a call objective plan to record call objectives, next call objectives, and call outcomes for sales calls associated with a product (for example, a drug).
To set up Structured Product Messaging dynamic page layouts
Create the PCD page layouts for Messaging Plan, Messaging Plan Item, Messaging Plan Item Relation, and Message Response as described in the table in Field Setup and Layout for the LS Field Sales Rep Role Page Layouts.
For related information on creating page layouts, see Setting Up Page Layouts for Oracle CRM On Demand Life Sciences Edition.
Create the SPM page layouts (Call Objective Plan page layout, Call Objective page layout, Outcome page layout, and Next Call Objective page layout) as described in the following table.
For related information on creating page layouts, see Setting Up Page Layouts for Oracle CRM On Demand Life Sciences Edition.
Record Type Page Layout Page Section Layout Required, Read-Only, or Optional Messaging Plan
LS Messaging Plan Call Objective Plan Page Layout
Key Messaging Plan Information
Name
Required
Type
Note: Include Call Objective Plan as a choice for the Type picklist.Required
Product
Required
Status
Required
Verify
Read-Only
Code
Optional
Segment
Optional
Start Date
Optional
Expiration Date
Optional
Release Date
Optional
Disclosure Mandatory
Required
Enable Followup
Required
Lock Sequence
Required
Additional Messaging Plan Information
Audience
Optional
Comment
Optional
Description
Optional
Messaging Plan Item
LS Messaging Plan Item Call Objective Page Layout
Key Messaging Plan Item Information
Sequence Number
Required
Plan Item Name
Optional
Display Name
Optional
Currency
Read-Only
Disclosure Message
Required
Type
Note: Include Call Objective as a choice for the Type picklist.Required
Send Type
Required
Parent Messaging Plan
Required
Status
Optional
Description
Optional
Note: If Solution is not a required field in your page layout, then the Messaging Plan Item name defaults to the parent Messaging Plan name plus the Messaging Plan Item sequence number. For example, if you have a parent Messaging Plan called DrugABC Product Launch with four related Messaging Plan Items, then the names of the Messaging Plan Items are DrugABC Product Launch 1, DrugABC Product Launch 2, and so on. That is, the Messaging Plan Item name is a concatenation of the parent Messaging Plan name and the sequence number for the Messaging Plan Item.Messaging Plan Item Relations
LS Messaging Plan Item Relations Next Call Objective Page Layout
Key Messaging Plan Item Relations Information
Created
Optional
Created By
Optional
Created By: Email
Optional
Created By: External Unique ID
Optional
Created By: First Name
Optional
Type
Note: Include Next Call Objective as a choice for the Type picklist.Required
Solution Name
Optional
Synopsis
Optional
Name
Required
Display Name
Required
Parent MP Item
Required
Message Response
LS Message Response Outcome Page Layout
Key Message Response Information
Message Plan
Optional
Sequence
Required
Type
Note: Include Outcome as a choice for the Type picklist.Required
Message Plan Item
Optional
Solution
Optional
Response
Optional
Notes
Optional
Section
Optional
Start Time
Optional
End Time
Optional
Duration
Read-Only
Followup
Optional
Account
Optional
Account: External Unique ID
Read-Only
Account: Integration ID
Read-Only
Profile Information
Id
Read-Only
Name
Required
Contact
Optional
Contact: External Unique ID
Optional
Contact: First Name
Optional
Contact: Integration ID
Optional
Contact: Last Name
Optional
Note: Message Response records that are repurposed as Outcomes for Structured Product Messaging can only be created by the administrator using Web services and not through the user interface. A user with the LS Field Sales Rep role can select an Outcome within the context of the Product Detail Related Information section. However, the administrative task of creating the Outcome values must be completed through Web services and not in the UI screen navigation.Set up the Type field to drive the dynamic page layout used by the field sales representative for each PCD record type:
Note: Make sure you have set up the Type field on both PCD and SPM page layouts.In the upper right corner of any page, click the Admin global link.
In the Application Customization section, click the Application Customization link.
In the Record Type Setup section, click the link for one of the PCD record types:
Messaging Plan
Messaging Plan Item
Messaging Plan Item Relations
Message Response
- In the Dynamic Layout Management section, click the <PCD record type> Dynamic Layout link.
- In the Dynamic Page Layout list, click the New Layout button to create a new dynamic link layout.
In Step 1 Specify Name:
Enter a name for the Dynamic Layout for the PCD record type you are setting up, for example:
Messaging Plan Dynamic Layout
Messaging Plan Item Dynamic Layout
Messaging Plan Item Relations Dynamic Page Layout
Message Response Dynamic Page Layout
- Select a Default Layout. This layout is presented as the default layout in the next step.
- Set the Driving Picklist field to Type if required. The values of the Type picklist determine which layout the users can see.
In Step 2 Assign Layouts, associate the Type picklist values with a layout name as follows:
For Messaging Plan records:
For a Type value of Call Objective Plan, associate the type value with the LS Messaging Plan Call Objective Plan Page Layout.
For all other Type values, associate the type value with the LS Messaging Plan Page Layout.
For Messaging Plan Item records:
For a Type value of Call Objective, associate the type value with the LS Messaging Plan Item Call Objective Page Layout.
For all other Type values, associate the type value with the LS Messaging Plan Item Page Layout.
For Messaging Plan Item Relations records:
For a Type value of Next Call Objective, associate the type value with the LS Messaging Plan Item Relations Next Call Objective Page Layout.
For all other Type values, associate the type value with the LS Messaging Plan Item Relations Page Layout.
For Message Response records:
For a Type value of Outcome, associate the type value with the LS Message Response Outcome Page Layout.
For all other Type values, associate the type value with the LS Message Response Page Layout.
Note: For each dynamic page layout, there is a limit of 200 associations between driving picklist values and page layouts.The layout you select is displayed when a record has the corresponding picklist value.
- Click Finish
Assign the dynamic layouts you have created to the user roles that will use these layouts, for example, the Administrator or the LS Field Sales Rep role in the Role Management wizard:
From the Admin Homepage, click User Management and Access Controls, then Role Management.
Edit the role of the user who will use the dynamic page layouts, for example, the Administrator or the LS Field Sales Rep role.
In Step 6 Page Layout Assignment, for each PCD record type:
For the Page View Type, choose Dynamic
For the Page Layout Name, select the dynamic page layout you created in Step f corresponding to that record type.