To configure this feature:

1. Ensure Call Reporting is configured.
2. Grant the following permissions for each permission set that requires access:

   Object	Object Type Permissions	Object Types	Fields	Field Permissions
   medical_discussion__v	CRED	medical_discussion__v	All Object Fields	Edit
   call2__v	n/a	n/a	medical_discussions__v	Edit

3. Remove privileges to the call2_detail__v and call2_discussion__v objects for the same permission sets. This step is optional, however best practice is to provide users access only to the medical_discussion__v field.
4. Place the medical_discussion_section__v app section on the appropriate call2__v object type layout.
5. Grant each permission set that requires it access to the medical_discussion_section__v app section on the call2__v object.
6. Activate the appropriate VMOCs for mobile devices.

Admins can add one or more Medical Discussion sections of differing types by creating multiple object types for the medical_discussion__v object and granting permission sets access to these object types. The layout of each Medical Discussion section displays based on the medical_discussion__v object type. For each medical_discussion__v object type the user has access to, an Add Discussion action displays.

Configuring Additional Features

For Account Plans and Tactics (Browser, iPad only):

1. Place the account_plan__v field on the appropriate call2__v object layout.
2. Place the account_tactic__v field on the appropriate medical_discussion__v object layout.

For Product Plans, Strategies, and Tactics:

1. Grant read permission to the active__v field on the product_strategy__v and product_plan__v objects.
2. Place the product_strategy__v and product_tactic__v fields on the appropriate medical_discussion__v object type layout.

For Medical Events, place the medical_event__v field on the appropriate medical_discussion__v object type layout.

For Product Dependent Picklists:

1. Ensure the picklist values in the product_map__v field on the medical_discussion__v object match all potential Detail Products and Detail Topics.
2. Create a custom picklist field on the medical_discussion__v object. Ensure the "Restrict picklist to the values defined in the value set" check box is not selected.
3. Create a field dependency for the new custom picklist field and set the product_map__v field as the controlling field and the new custom picklist as the dependent field.
4. Select the values to display in the new custom picklist field based on each Product value.
5. Place the new custom picklist field on the appropriate medical_discussion__v object type layout.

Users can create Medical Discussions to capture key components based on the discussion type. Selecting the Add Discussion action creates a Medical Discussion record based on the layout of the selected object type.

More than one Medical Discussion section displays if more than one Discussion Type is configured. Sections display by medical_discussion__v object type label name.

End users can copy, edit and delete existing medical discussions.

Validation rules can be created based on object type to provide added flexibility when creating different Medical Discussion types.

Product Selection

Products displayed in the product__v field are based on the user’s My Setup Products, including Detail and Detail Topic product types. If Detail Groups are configured, the Detail Group of the Product or Topic is appended to the Product Name, and the Detail Group field is updated with the corresponding Detail Group when the Product/Topic is selected.

For users aligned to multiple products, a search field provides the ability to filter the list based on Product name.

Account Plans and Tactics (Browser, iPad only)

End users can relate an Account Tactic to a Medical Discussion record. When an end user selects an Account Plan on a call report, any associated Account Tactics become available in the Account Tactics field on the Medical Discussion.

If a selected Account Tactic is associated with any Call Objectives, and the Date of the Interaction is within the date range of the Call Objective, the Call Objective automatically displays.

Product Plans, Strategies, and Tactics

Product Strategies and Tactics can be associated to a Medical Discussion record. The values available for selection in the product_strategy__v field are dependent on the value selected in the product__v field and are organized by Product Plan. The values available in the product_tactic__v field are dependent on the value selected in the product_strategy__v field.

Medical Events

End users can associate a Medical Event to a Medical Discussion using the medical_event__v lookup field in the Medical Discussion section. If the medical_event__v field on the Call record is populated, the medical_event__v field on the Medical Discussion record defaults to that record. If the medical_event__v lookup field on the Call Header is not populated, the medical_event__v field displays a default list of all active Medical Events where at least one of the Accounts associated to the Call is an Event Attendee. If the desired Medical Event is not defaulted, a search field provides the ability to search across all Medical Events.

Product Dependent Picklists

Custom picklist fields can be configured to be dependent on the product selected in a Medical Discussion. The product_map__v field serves as the controlling field for all custom dependent relationships. This field does not display on the layout, and does not need to be placed on the layout for this feature to function. The picklist values of the product_map__v field must match the API names of all potential Detail Products and Detail Topics.

When a value is selected in the product__v field, the product_map__v field is set to the same value, and all dependent picklists display based on the selected product.