To configure Engage attendance tracking for business admin users:

1. Ensure Configuring Engage Meeting is complete.
2. Enable the Process Scheduler.

3. Grant the following permissions:

   Object	OLS	Object Types	Fields	FLS
   remote_meeting_attendee__v	R	call__v	attendee_type__v network_type__v	Read
   			All Other Fields	Edit
   remote_meeting__v	R	call__v	meeting_outcome_status__v	Read
   			attendance_report_process_status__v latest_meeting_start_datetime__v	Edit

4. Grant View permission to the Engage Platform Process Administration (engage_meeting_process_admin_page__v Page.
5. Grant View permission to the CRM PL3 Generic Page.
6. Ensure a layout is assigned to the call__v record type on the remote_meeting_attendee__v and remote_meeting__v objects.
7. Enable the retry__v and success__v picklist values for the attendance_report_process_status__v field on the remote_meeting__vobject for the call__v object type.
8. Set None as the default picklist value for the attendance_report_process_status__v field on the remote_meeting__v object for the call__v object type.

To configure Engage attendance tracking for integration users:

1. Ensure Configuring Engage Meeting is complete.
2. Grant the following permissions:

   Object	OLS	Object Types	Fields	FLS
   account_merge_history__v	R	n/a	All Fields	Read
   call2__v	R	n/a	account__v parent_call__v remote_meeting__v status__v veeva_remote_meeting_id__v	Read
   remote_meeting_attendee__v	CRED	call__v	meeting_duration__v	Read
   			account__v attendee_type__v created_by__v created_date__v device__v display_name__v ip_address__v join_time__v modified_by__v modified_date__v leave_time__v meeting_end_time__v meeting_start_time__v network_type__v participant_id__v object_type__v remote_meeting__v name__v user__v veeva_remote_meeting_id__v vexternal_id__v	Edit
   remote_meeting__v	CRE	call__v	meeting_id__v	Read
   			attendance_report_process_status__v engagement_minutes__v (optional) ip_address__v (optional) latest_meeting_start_datetime__v meeting_outcome_status__v vexternal_id__v	Edit

To configure Engage attendance tracking for meeting hosts:

1. Ensure Configuring Engage Meeting is complete.
2. Grant the following permissions:

   Object	OLS	Object Types	Fields	FLS
   remote_meeting__v	n/a	n/a	attendance_report_process_status__v latest_meeting_start_datetime__v vexternal_id__v	Edit

The Engage Reporting Processes process can be scheduled at certain intervals or can be performed immediately by selecting the Run button. Business admin users can configure email alerts if an error occurs during the process.

Business admin users can review process history as well as manage the integration user credentials on the Engage Platform Process Administration tab.

The Attendance Report Process History section displays the following information from the 10 most recent runs:

• Start and Stop Timestamp
• Status
• Success – Number of records successfully processed. The displayed value serves as a download link for the run’s Success Log.
• Error – Number of records that encountered an error during processing. The displayed value serves as a download link for the run’s Error log.
• Message – States successes and failures that occurred during the run

Attendance Information

Attendance information is available in Vault CRM as it becomes available from Zoom. Attendance information is loaded into remote_meeting_attendee__v records.

It may take up to 24 hours after the meeting ends for attendance information to be available for loading into Vault CRM. On the next process run, all available attendance data is populated.

Information Stored in the remote_meeting__v Record

The remote_meeting__v record tracks its Processing Status (attendance_report_process_status__v) and the Meeting Outcome Status (meeting_outcome_status__v). The Processing Status indicates the status of receiving data from Zoom. The Meeting Outcome Status summarizes the attendance of the meeting.

The Processing Status picklist on the remote_meeting__v object displays on of the following values:

• Empty - Vault CRM is waiting for data from Zoom
• retry__v (Retry) – Manually set by business admins to retry the process. The system automatically retries getting attendance data for meetings with this status.
• success__v (Complete) – There is high confidence Vault CRM has collected all the attendance data from Zoom for this meeting.

  If business admins suspect there is missing data, they can set the attendance_report_process_status__v field to retry__v and the remote meeting will be reprocessed the next time the process runs.

The meeting_outcome_status__v picklist populates as soon as enough data is available to determine the business outcome. For example, as soon as Zoom reports that an external attendee has joined a meeting, the corresponding remote_meeting__v record's meeting outcome updates to Meeting Started with Attendees when the processing job next runs, regardless of if the call has been submitted or not.

The Meeting Outcome Status displays one of the following values for successfully processed Engage meetings:

• Meeting Not Scheduled - An error occurred when scheduling the Engage meeting
• Meeting Not Started – The Engage meeting on the corresponding call2__v record was never started
• Meeting Started with Attendees – The Engage meeting was started and at least one attendee joined
• Meeting With Internal Attendees Only – The Engage meeting was started with only user attendees
• Meeting Started Without Attendees – The Engage meeting was started and no attendees joined
• Meetings Started, Details Not Available - Information is not available for the Engage meeting

Even after the meeting outcome populates, the attendance_report_process_status__v field remains empty for two days after the related call is submitted. This is to ensure all relevant data is available in Vault CRM before the attendance_report_process_status__v field is updated to success__v.

After the Engage meeting is processed, the engagement_minutes__v field populates with the amount of time, in minutes, that the host or user attendee and at least one external attendee was present in the meeting.

Information Stored in remote_meeting_attendee__v Records

When remote_meeting_attendee__v records are generated and associated with the corresponding remote_meeting__v record, the following fields populate:

• account__v – Populates for all records corresponding to attendees who joined via an Engage link. References the account corresponding to the attendee. This field is left blank if the attendee is the host or is a user attendee.
• attendee_type__v - Identifies the type of attendee, including hosts, external attendees, and user attendees
• device__v - The type of device the attendee used to join the meeting
• display_name__v - The name that the attendee entered when joining the meeting
• ip_address__v – References the IP address of the device the attendee used to join the meeting

  This field is left blank if the integration user does not have FLS edit permission to the field at the time the process runs.

• join_time__v - The date and time of when the attendee joined the meeting
• leave_time__v - The date and time of when the attendee left the meeting
• meeting_duration__v - The amount of time elapsed during the meeting, in minutes
• meeting_end_time__v - The date and time of when the meeting ended
• meeting_start_time__v - The date and time of when the meeting started
• network_type__v - The type of network the attendee used to join the meeting
• participant_id__v - The ID for the attendee when joining the meeting
• object_type__v - The type of remote meeting
• remote_meeting__v - References the remote meeting in which the attendee participated
• user__v - References the user record of the internal attendee who joined the meeting
• veeva_remote_meeting_id__v - The ID of the remote meeting that the attendee entered when joining the meeting

Zoom Attendee Information in remote_meeting_attendee__v Records

When remote_meeting_attendee__v connection records are created for attendees who join an Engage meeting via Zoom, some fields are not populated. The table below illustrates the difference between attendees and Zoom attendees:

Remote Meeting Attendee Fields	Attendee Joining via HCP Apps	Zoom Attendee
remote_meeting__v	a3on00000011aaA	a3on00000011aaA
participant_id__v	55137
attendee_type__v	external_attendee__v	external_attendee__v
account__v	00161000004vuUfAAI
veeva_remote_meeting_id__v	1386983226
meeting_start_time__v	4/15/21 8:00	4/15/21 8:00
meeting_end_time__v	4/15/21 8:22	4/15/21 8:22
meeting_duration__v	22	22
join_time__v	4/15/21 8:01	4/15/21 8:01
leave_time__v	4/15/21 8:20	4/15/21 8:19