To configure this feature:

1. Ensure the following features are configured:

   • Configuring Call Reporting
   • Configuring Medical Events

2. Grant end users the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   call2__v	CRE	event__v	medical_event__v	Edit
   call_discussion__v	CRE	n/a	medical_event__v	Read
   medical_event__v	CRE	n/a	account__v address__v	Read

3. Add the medical_event__v field to the appropriate layouts of the following objects:

   • call2__v
   • call_discussion__v

4. Add the following fields to the appropriate medical_event__v layouts:

   • account__v
   • address__v

Users can create a call from a medical event by selecting the Record a Call button. The call date, event name, and call object type automatically populate based on the medical event.

Calls created from a medical event have the following properties:

• The medical_event__v field on the call references the originating medical event and is read only

• Event attendees display as the default suggested attendees in the Attendees section of the call report

  The parent HCO account of an HCP account must be in the same territory for child accounts to display.

• The call_date__v field defaults to the value of start_date__v for the medical event

Associating Existing Calls with Medical Events

Existing calls can be associated with existing medical events by populating the medical_event__v lookup field with the appropriate medical event. A filtered list of active events displays. If the desired event is not visible in the list, users can search across all events from the field.

Associating Product Discussions with Medical Events

Like the medical_event__v field on the call2__v object, the medical_event__v field in the Product Discussions section displays a filtered list of active events sorted by start_date__v in descending order.

To associate a product discussion with a medical event, select the appropriate medical event from the medical_event__v field. Users can search across all medical events from the field.

Associating Accounts and Addresses to Medical Events

Users can associate an account and address to a medical event that automatically populates in call reports created from the event. This streamlines call reporting for scenarios where users interact with several different accounts and discuss different products at the same event.

When the account__v and address__v fields are placed on the medical_event__v page layout, the following fields are populated on call reports created from medical events:

• The account__v and address__v fields on the call report are copied from the corresponding fields on the medical event

• The medical_event__v lookup field on the call report references the originating event and is read only
• If the account__v and address__v fields are populated on a medical event record, the default call object type for the account is used for new calls. If the account does not have a default, the user's default call object type is used.
• If the account__v and address__v fields are not populated on the medical event record, the event__v object type is used for new calls

The defaulting behavior for suggested attendees and call location varies depending on the type of account.

When a business account is associated to a medical event:

• The Attendees section of the call report displays the attendees from the medical event as default suggestions
• The location is set to the preferred location on the user's TSF record for the account