X-Pages consists of the following objects and components.

Entry Points

Users can view X-Pages content from different areas of Vault CRM. Each area is an entry point, defined by a specific object type for the html_report__v object.

The following table maps the entry points to their corresponding object type:

Entry Point	Object Type
Account	account_reports__v
Account Plan	account_plan__v*
Call Report	call2__v
Default Account Profile	account_profile_override__v
Default Home Page	territory_insights_default__v
Default KOL Profile	kol_profile__v
Opportunity Management	opportunity_management__v
Service Center	service_center__v
Territory	territory_insights__v
Territory Feedback	territory_feedback__v

*Users can view html_report__v records of this object type without object type access.

Certain entry points require additional configuration to display to end users.

Content Zip File

X-Pages content must be packaged into a zipped folder containing the index.html file and the appropriate CSS and JavaScript files.

X-Page (html_report__v)

Once a content zip file is attached to an html_report__v page, users can sync their devices and view the content in Vault CRM. See Creating X-Pages Records for more information about how to create X-Pages.

To configure this module:

1. Navigate to Admin > Users & Groups > Permission Sets.
2. Select the appropriate permission set.
3. Select Objects.
4. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   html_report__v	CRED	account_profile_override__v account_reports__v kol_profile__v account_plan__v territory_insights_default__v territory_insights__v territory_feedback__v service_center__v opportunity_management__v	name__v object_type__v platform__v	Edit
   vmobile_object_configuration__v	CRU	n/a	include_attachments__v	Read

5. Grant execute permission to the Publish action on the html_report__v object for the appropriate object type(s).

6. Create a tab for the html_report__v object.
7. Grant content creators access to the tab you just created.
8. Create a layout for each object type content creators have access to.
9. Ensure the name__v, object_type__v, and platform__v fields are on each layout.
10. Navigate to Business Admin > Objects> veeva_settings__v and enter 1 for the KAM_ENABLE Veeva Setting if using the account_plan__v entry point.
11. Enable the locale__sys object VMOC for the appropriate mobile devices.

To configure this module:

1. Grant the following permissions:

Object	Object Permission	Object Types	Fields	Field Permission
html_report__v	R	account_profile_override__v account_reports__v kol_profile__v account_plan__v territory_insights_default__v territory_insights__v service_center__v opportunity_management__v	name__v object_type__v platform__v	Read
vmobile_object_configuration__v	R	n/a	include_attachments__v	Read

2. Populate the Sync Configuration Mode Veeva Setting with a value of 1. This setting adds support for multiple VMOCs per object.
3. Select the Include Attachments check box for VMOCs on the html_report__v object. This ensures all Attachments and Files related to html_report__v records sync.
4. Disable any VMOCs for the Attachment object created specifically for the html_report__v object and/or remove any logic related to the html_report__v object in the WHERE clauses.