What's New in Vault CRM 25R2.0
The 25R2.0 release includes features for:
The 25R2.0 release includes features from the following Vault CRM minor releases:
Release Dates
- Sandbox Release - August 7, 2025
- Production Release - August 21, 2025
New Fields, New Objects, and Removed Fields are also included.
Core
Account Management
Creating and Managing Account Profiling Templates - Available on Browser
Business Admin Users can create and publish Account Profiling templates for End Users to update. They can also check the status of Account Profiling work. Account Profiling offers organizations a streamlined way to collect account profile data from the field.
Child Accounts in Vault CRM - Available on iPad and iPhone
Users can view and record interactions for Child Accounts. In some organizations or regions, the relationship between the person account and business account is an integral part of the business model. In Vault CRM, this relationship is modeled using Child Account records, which display person and location information together as one unique record so users can understand the HCP-HCO relationship.
Display Child Account TSF Information in My Accounts - Available on iPad
Users can view information from child account TSF records in My Accounts Views. This ensures users have visibility into key interactions, status updates, and relevant data within their designated territories.
Dynamic Attributes in My Accounts Views - Available on Browser
Users can specify Dynamic Attributes as criteria when defining My Accounts views. This enables users working with custom attributes to filter My Accounts to a tailored, actionable view that only includes accounts relevant to the user's current task. The specified Dynamic Attributes display as columns in the My Accounts view.
Enable Querying and Reporting of Dynamic Attributes - Available on Browser and iPad
By selecting the Enable Query & Reporting check box for a Dynamic Attribute, business admins can leverage the following benefits:
- Seamlessly include Dynamic Attributes in standard reports, filters, and My Accounts searches
- Improve the performance of searches and reports by storing attribute data in a structured, optimized format
- Enable advanced functionality instantly. No data migration is required.
Entering Information in Account Profiling Sheets - Available on iPad
End Users can use Account Profiling sheets to collect profiling data from the field and make mass updates using a familiar, spreadsheet-like interface.
View the Account Profiling video
My Accounts Redesign - Available on Browser
My Accounts on the Browser platform is updated with a new look and feel, a new way to quickly search for accounts, and improvements to viewing Lists and Views. From the My Accounts tab, users can access the Account Search and the Views and Lists tabs. The Account Search tab replaces the Global Account Search tab and offers similar functionality.
View the Creating Views in My Accounts video
Account Timeline
Viewing Events Management Events on the Account Timeline - Now available on Browser
Users can view Event Management (EM) events on the account timeline. This ensures users have a complete view of key milestones and engagements, for example speaker programs, directly alongside other customer interactions like calls or emails. This complete view provides users with the context needed to make more informed decisions and understand the impact of an event on subsequent interactions.
Call Planning
Enabling Call Booking Support - Available on Browser
To enable end users to focus fully on call execution, some organizations authorize designated users (booking agents) to handle call scheduling and planning. Call Booking Support enables booking agents to assign planned calls to other users, for centralized call planning.
Using Child Accounts in My Schedule - Available on Browser, iPad, and iPhone
Using child accounts in My Schedule enables users to schedule calls for a specific account-organization (HCP-HCO) combination rather than just the HCP’s account. This ensures calls are planned for an HCP at a specific institution, providing greater precision than planning a call for the individual alone.
Managing Call Cycles for Child Accounts - Available on Browser and iPad
To enable users to easily schedule recurring sets of calls against an account-organization (HCP-HCO) combination, rather than just the HCP’s account, users can create and apply call cycles for child accounts. This enables users to save time when scheduling calls for frequently visited child accounts.
Displaying Office Best Times for Child Accounts - Available on Browser and iPad
Since HCPs may practice at multiple institutions with varying schedules, tracking availability at the child account level ensures call planning aligns with the HCP’s hours at each facility. When scheduling calls for child accounts, Office Best Times for the HCP-HCO combination display in My Schedule, enabling users to quickly identify optimal time slots.
Call Reporting
Call Reporting with Child Accounts - Available on iPad and iPhone
In some organizations, the connection between individual professionals (HCPs) and the businesses they work with (HCOs) is a key aspect of call reporting. For these implementations, call reports must be linked to both the individual and the call location to ensure accurate representation of real-world interactions. To support this, call reporting automatically assigns the appropriate person and location based on the call entry point and the child/parent relationship between the HCP and HCO. Additionally, search functionality on the call report prioritizes relevant child accounts, making it easier for users to find and associate the correct records.
Using Medical Discussions on Unique Activities Child Calls - Now available on Browser
Medical Discussions on unique activities calls enable users to capture key information for scientific discussions with HCPs. By capturing this information on the child call, users can record separate information for each attendee on a unique activities group call.
Call Sampling
Generating Printable Acknowledgement of Content Receipts - Available on Browser
To quickly and easily produce compliant documentation for Acknowledgement of Content (AOC) disbursements, sample admin users and end users can generate printable AOC receipts.
View the Generating Printable Acknowledgement of Content Receipts video
Sampling Non-PDMA Regulated Products - Now available on Browser
For call reports on the Browser platform, users can disburse non-PDMA product samples without capturing a signature or sample card number. Products not included in PDMA (Prescription Drug Marketing Act) regulations, for example, over the counter products, have less stringent requirements for sampling and HCP licensure.
Viewing the Sample Status Indicator - Now available on Browser
To indicate to Browser users whether an HCP is eligible for sampling, a sample status indicator displays on the call report.
Viewing the Sample Send Status Indicator - Now available on Browser
To indicate to Browser users whether an address is eligible for sample requests (BRCs), a sample send status indicator displays in the Ship-to Address picklist on the call report.
Classic Cycle Plans
Managing Classic Cycle Plan Targets - Available on Browser
To keep plans relevant and impactful, users with the necessary permissions can quickly add or edit cycle plan targets. When adding targets, users define planned call goals and can also specify product detail goals. This flexibility helps adapt plans to changing market conditions, strategies, and priorities, ensuring plans are optimized for the right accounts and objectives.
Scheduling Calls for Classic Cycle Plan Targets - Available on Browser
To support cycle plan execution, end users can schedule calls directly from the Cycle Plan Targets table on Cycle Plan record detail pages. This table displays key metrics for each target account, making it easy to identify under-reached accounts.
Supporting Custom Pull-in Fields for Classic Cycle Plans - Available on Browser and iPad
Custom pull-in fields for cycle plan targets and products provide end users with enhanced visibility into key information. Pull-in values display as additional columns in the Cycle Plan Targets table, along with standard information about cycle plan goals for each target and product in the plan. This facilitates improved account identification, more informed outreach strategies, and streamlined call planning.
Monitoring Classic Cycle Plan Progress from the Account Detail Page - Now available on Browser
To provide quick access to performance insights specific to a particular account, cycle plan information displays on the Account Detail page in View mode. This enables users to readily see their progress toward goals for the specific target over a given time period, facilitating informed decisions regarding account engagement. Managers also benefit from this visibility, gaining insight into users’ progress for a specific target account.
Consent Capture
Displaying Externally Managed Consent in Vault CRM - Available on Browser, iPad, and iPhone
Customers with custom integrations between Vault CRM and their external consent system can configure the Consent Capture page to display in read-only mode for end users. This allows Vault CRM to enforce consent for email and messaging channels using data from the external system, while managing all consent changes remain in the external system.
View the Displaying Externally Managed Consent in Vault CRM video
Managing Consent for Messaging - Available on Browser
Business admin users must set up consent for the Messaging channel to allow end users to capture consent from HCPs before sending messages.
General
Using the Data Lakehouse for Vault CRM
Customers can access a Data Lakehouse containing a complete and up-to-date copy of their Vault CRM data. The Data Lakehouse retrieves all Vault CRM data using Vault Platform’s Direct Data API. Retrieved data publishes as Apache Iceberg™ tables on S3, enabling customers to easily query Vault CRM data in place, or copy out to an external data warehouse.
Parent-Child Security for Account Child Objects
Child objects of the account__v object now use the Vault standard parent-child security model for record access, instead of application-specific logic. This simplifies security management and ensures users have the correct level of record access from the moment records are created. The update was first available in the Vault CRM 25R1.3 release.
Medical
Using Medical Interaction - Available on Browser and iPad
Medical Interaction provides medical users with a comprehensive method of planning and tracking their interactions with medical professionals, leading to stronger relationships and better communication of product information. The Medical Interaction user interface (UI) is designed to be dynamic, allowing users to easily take notes and only add the sections they need. To provide continuity of account medical-related information, users can also create Discussions, Medical Inquiries, Key Medical Insights, and Documented Interests directly from the Medical Interaction report.
Viewing Medical Interactions on the Account Timeline - Available on Browser and iPad
Medical users can view Medical Interactions on the Account Timeline. This provides a more comprehensive and chronological overview of engagement with an account. By viewing these related activities in one place, users can quickly understand the full context of the relationship with an account, saving time and improving preparation for future engagements.
Displaying Medical Interactions on My Schedule - Available on Browser and iPad
Medical users can view Medical Interactions from My Schedule, alongside other scheduled events such as Time Off Territory and Medical Events, streamlining their planning and execution process. Users can quickly assess their upcoming Medical engagements using color-coded calendar entries that display key information such as the interaction's title, location, address, channel, and attendee count.
Medical Events
Recording a Call with Medical Events - Now available on Browser
To accurately and efficiently capture activities from medical events, users can associate an event to a call, or create a call directly from a medical event. This streamlines call reporting by automatically populating call fields with event information linking the event to the call report, and enables end users to avoid reentering this information and only enter call information specific to individual attendees.
Medical Inquiry
Using Vault MedInquiry to Fulfill Medical Inquiries - Available on Browser and iPad
Medical Inquiries created and submitted in Vault CRM by sales and field medical teams can automatically be shared with medical information teams for fulfillment using a connection with Vault MedInquiry. This automated process provides the medical inquiry submitter with status updates as the medical inquiry is worked on, including Submitted, In Progress, and Closed, at which point the submitter knows the medical inquiry is fulfilled.
Generating Printable Medical Inquiry Receipts - Available on Browser
To provide receipts for signature audits or other internal needs, business admin users can generate printable, compliant Medical Inquiry signature receipts as PDFs. These receipts can be used to verify a Medical Inquiry was fulfilled as described.
View the Generating Printable Medical Inquiry Receipts video
Adding a Disclaimer to a Medical Inquiry - Available on Browser and iPad
Business admin users can add default disclaimer text that displays on the Medical Inquiry page. This text is often recommended or required by a medical or pharmaceutical provider's legal department. Additionally, instead of the default disclaimer text, customers with multi-country operations can automatically display disclaimer text on the Medical Inquiry page based on the country of an account.
Multichannel Cycle Plans
Supporting Child Accounts for Multichannel Cycle Plans - Available on Browser and iPad
In organizations using child accounts, Multichannel Cycle Plan (MCCP) goals and activity tracking can be managed separately for each child account. This enables personalized engagement and tailored goal setting, based on the unique needs of each location.
Sample Management
Overriding Locked Sample Management Records - Available on Browser
To ensure seamless updates while maintaining data security and compliance with regulatory requirements, integration users or sample admins can update fields on submitted or locked Sample Management records. This eliminates the need for an admin user to manually unlock the record, or for the integration user to have Modify All permission.
Surveys
Supporting Child Accounts in Surveys - Available on Browser, iPad, iPhone
Survey designers can add child accounts as survey targets when creating surveys, and end users can select child accounts as survey targets when creating new survey targets. Surveys for child accounts allow organizations to collect information that is specific to a person at a particular location because HCPs often work at multiple locations.
Sync
Supporting List Layouts on Mobile Devices - Available on iPad and iPhone
Business admin users can define list layouts for objects to customize the columns displayed in search modals. This allows end users to view relevant information when searching for records to populate reference fields, providing better context for their selections.
X-Pages Studio
Data Box Data Element - Available on Browser
The CRM Data Engine data element is renamed Data Box and is now available for use in X-Pages Studio. Data for this element is obtained by using the queryDataEngine method. When content creators add the Data Box data element to an X-Page, users can view large data sets queried from Data Box, for example Compass data. Results from this query can be viewed on the X-Pages Studio preview page.
Mean and Median Data Expressions - Available on Browser
Content creators can now calculate mean and median values for queried data in X-Pages Studio using data expressions. Mean and median values can help condense large data sets into easily understandable insights. The mean helps users understand overall performance, average sales, or average call frequency. The median is helpful when data is skewed or contains outliers, as it's less affected by extreme values than the mean.
X-Pages Studio Content Types - Available on Browser
The following content types are now available for use in X-Pages Studio to create and deploy content:
- Inventory Monitoring
- Order Management
- Patient Center
- Speaker (Events Management)
The following topics are updated with new content type and object type information:
- Configuring X-Pages Studio
- Adding Data to Pages in X-Pages Studio
- Deploying Pages to Vault CRM Using X-Pages Studio
Approved Email
Auto-Publishing for Email Fragments - Available on Browser, iPad, and iPhone
Content Creators can upload content directly to Vault CRM so that end users can add the content as a fragment when they create Approved Email messages. Some content may not require medical, regulatory, or legal review in PromoMats or MedComms; for example, a holiday greeting, a logistical document, or an agenda.
Campaign Manager
Using the Target List Builder - Available on Browser
Marketing users can create filters on various fields and objects to create target lists for their campaigns. Creating target lists in this manner saves time during the campaign planning process, reduces errors associated with manually selecting large numbers of targets, and increases campaign engagement by ensuring only the appropriate accounts are targeted by the campaign.
View the Using the Target List Builder video
Creating Multi-Action Campaigns - Available on Browser (Available August 21, 2025)
Multi-Action Campaigns enable marketers to execute more complex campaigns by supporting target list groups and automated follow-up actions. This feature streamlines the process of engaging different target segments with tailored content and sequences of messages, enhancing the effectiveness and efficiency of marketing efforts.
Creating Follow-up Actions - Available on Browser (Available August 21, 2025)
Users can define follow-up actions for their Multi-Action Campaigns that automatically send to certain targets based on how they interacted with the initial email sent from the campaign or the email from a different follow-up action.
Managing Target Groups - Available on Browser (Available August 21, 2025)
Marketing users planning Multi-Action Campaigns can organize their campaign's target list into groups of differing levels based on the level_cda__v field on the account__v object. This enables marketing users to select different email templates and follow-up actions for each group of the target list, enhancing the personalization and relevance of campaign emails.
Engage
Scheduling and Starting Zoom® Meetings - Available on iPad
Meeting hosts can schedule Zoom® meetings, send invites, update meeting details, and initiate meetings directly from the call report in Vault CRM, allowing users to accommodate HCPs who prefer Zoom. The meeting is hosted by Zoom and the meeting experience is controlled by the user’s Zoom Enterprise account.
Sending Zoom® Meeting Invites via Approved Email - Available on iPad
With Approved Email, meeting hosts can send meeting invites to up to 100 Zoom® meeting attendees at once. The Approved Email template can contain tokens to ensure all of the meeting details, for example, the date and time, meeting URL, and password are included in the email.
WhatsApp Business Messaging in Vault CRM
Customers can integrate WhatsApp Business with Vault CRM to allow their end users to have compliant conversations with HCPs. WhatsApp Business Messaging is built on Meta’s Cloud API, which allows approved businesses to send messages using verified phone numbers. This is separate from the WhatsApp mobile app or the WhatsApp Business app, and is designed for enterprise messaging.
- Managing WhatsApp Business Accounts and Phone Numbers in Vault CRM - Available on Browser - Business admin users can manage WhatsApp Business Account connections in the WhatsApp Business Administration page. This includes connecting WhatsApp Business Accounts to Vault CRM, connecting phone numbers, and assigning end users to the connected phone numbers.
- Managing Message Templates in Vault CRM - Available on Browser - Business admin users must data load Meta and Veeva message templates into Vault CRM for end users to sync to their devices.
Events Management
Adding Speaker Photos to Approved Emails for Events Management - Available on iPad
Business admin users can upload photos for each speaker, which can then be referenced in Approved Email content using the Event Speaker token. This personalizes and improves the visual appeal of email invitations to connect recipients to speakers.
Filtering Event Budgets - Available on Browser and iPad
Business admin users can configure filters for the list of budgets that display as available for an event. Reducing the number of budgets displayed to end users enables end users to quickly select the appropriate budget to add to their event, which in turn reduces any potential errors that need to be corrected during event approval.
Creating Expense Limit Rules - Available on Browser and iPad
Event Expense Limit rules enable admins to set up guidelines and policies surrounding expense limits. Automating this process results in greater compliance by preventing event organizers from adding estimated and actual expenses to an event based on these restrictions.
Service Center
Creating Call Reports from Target Activities - Available on Browser
Service Center Representatives (SCRs) can start a call report directly from the Target Activity Guide during outbound call activities. While the report still displays in a separate window, this effectively integrates call reporting into the standard outbound workflow, eliminating the need for users to navigate to a separate area to record call details. This feature provides a streamlined, efficient process for capturing required information and ensures call reports are directly associated with the corresponding target attempt.
Transferring Calls Using OmniConnect - Available on Browser
Service Center Representatives (SCRs) can transfer calls to another department or system, or to an external number, if needed. This helps users efficiently resolve customer issues and improve customer experience. Quickly transferring customer calls to the right resource, agent, or department allows SCRs to support calls from other users, queues, or external numbers.
Using My Cases for Service Center Inbound - Available on Browser
Service Center Representatives (SCRs) can access My Cases, a launch point for an SCR’s work throughout the day, from the Inbound tab to view a centralized hub of their assigned cases. When SCRs select My Cases, a time-sorted list of case cards displays, providing a visual representation of the cases assigned. This allows SCRs to better prioritize their work and drive cases toward resolution more effectively.
Using the Service Center Inbound Tab - Available on Browser
The Inbound tab on the Service Center console provides a centralized workspace for handling incoming emails, viewing assigned cases, and creating new cases from inbound communications. Work is organized as a two-pane layout so users can browse and take action on emails from shared inboxes, ensuring timely responses and effective case management.
Flightpath
Flightpath is an educational tool where you'll find overviews and examples to walk you through how to leverage Vault CRM features and functionality:
User Visible and Behavior Changes (UVCs)
Most new functionality requires some configuration, however users are able to use the following functionality immediately. Select the thumbnail to view a larger image.
Account Management
|
Platform |
Description |
Before |
After |
|---|---|---|---|
| Browser |
The My Accounts tab is updated to include subtabs for Account Search and Account Views and Lists. |
n/a | 
|
|
Browser |
An Account Type selector/filter is added to My Accounts. The "All Territories" option is removed from the Territory selector. |
n/a | 
|
Call Reporting
|
Platform |
Description |
Before |
After |
|---|---|---|---|
| iPad, iPhone |
On unique activities group calls, Attendee-Specific Fields display in the section with the account__v field, typically the call header. |
 of iPadUVCASF-UA-Before.PNG)
|
|
Consent Capture
|
Platform |
Description |
Before |
After |
|---|---|---|---|
|
Browser, iPad, iPhone |
When viewing the Consent Capture screen, each toggle is now labeled with Explicit Opt In or Implicit Opt In. |
|
|
Events Management
|
Platform |
Description |
Before |
After |
|---|---|---|---|
|
iPad |
The updated Event Materials widget now displays on em_event__v records. The widget displays, as well as the most recent materials with attachments. |
n/a | 
|
General
|
Platform |
Description |
Before |
After |
|---|---|---|---|
|
iPad, iPhone |
For lookup fields referencing picklist values, the picklist value label now displays in the lookup field instead of the API name. |
n/a | n/a |
|
CRM Desktop (Windows) |
End users using the Data Grid Loader can select the Exclude Blank Values on Upload check box to avoid updating existing data with blank values. |
|
|
Multichannel Cycle Plans
|
Platform |
Description |
Before |
After |
|---|---|---|---|
|
Browser |
When the Integration User has the correct permissions, MCCP channel activities are accurately reflected. Channel activities are counted towards users' actual goals based on the user timezone, not the UTC timezone. |
n/a | n/a |
25R2.0 Feature Enablement and Availability
The following table provides an explanation of feature enablement and user impact.
*Parity items do not typically require configuration if you are using this functionality on another platform. In some cases, VMOCs must be enabled for the added platform.
New Objects
Objects were not added in Vault CRM 25R2.0.
|
Object Name |
Object Label |
Description |
|---|---|---|
| campaign_group__v | Campaign Group | Enables grouping Campaign Manager campaign targets based on target level. |
| campaign_group_action__v | Campaign Group Action | Defines follow-up actions for campaign target groups. |
| medx__v | Medical Interaction | Stores the details of a medical interaction. |
| medx_attendee__v | MedX Attendee | Stores the details of an attendee of a medical interaction. |
| medx_component__v | MedX Component | Connects a component of a medical interaction to an attendee and/or a medical interaction. |
| medx_discussion__v | MedX Discussion | Stores the discussion that occurred during the medical interaction. |
| medx_discussion_material__v | MedX Discussion Material | Stores discussion material of a medical interaction. |
| medx_key_message__v | MedX Key Message | Stores the details of a key message on a medical interaction. |
| medx_meeting_material__v | MedX Meeting Material | Stores the meeting materials of a medical interaction. |
| message_template__v | Message Template | Stores header data for Message Templates. |
| message_template_business_account__v | Message Template Business Account | Stores details of Message Templates that are managed for specific Messaging Business Accounts. |
|
messaging_business_account__v |
Messaging Business Account |
Stores details of messaging business accounts. |
|
messaging_phone_number__v |
Messaging Phone Number |
Stores phone numbers used for messaging. |
|
pal_int_context__v |
PAL Integration Context |
n/a |
| profiling_attribute__v |
Profiling Attribute |
Stores the attributes that will be part of the profiling template. |
|
profiling_sheet__v |
Profiling Sheet |
Stores the individual profiling sheet based on the profiling template. |
|
profiling_template__v |
Profiling Template |
Stores templates for profiling sheets. |
New Fields
The table below contains all fields added in Vault CRM 25R2.0. The fields are organized by object.
|
Object |
Field Name |
Field Label |
Description |
Type |
|---|---|---|---|---|
| call2__v | zoom_remote_meeting__v | Zoom Remote Meeting | When populated, designates the Call has a Zoom meeting scheduled. | Object |
| campaign__v | campaign_template_type__v | Campaign Template Type | Represents the type of campaign template that the campaign is using. | Picklist |
| campaign_group__v | assigned_levels__v | Assigned Levels | n/a | Picklist |
| campaign_group__v | campaign__v | Campaign | n/a | Object |
| campaign_group__v | campaign__v | Campaign Groups | n/a | Object |
| campaign_group__v | description__v | Description | Description of the profiling template | Text |
| campaign_group__v | link__sys | Link | n/a | Text |
| campaign_group__v | name__v | Group Name | n/a | Text |
| campaign_group__v | selected_territory__v | Selected Territory | n/a | Object |
| campaign_group__v | status__v | Status | n/a | Picklist |
| campaign_group_action__v | campaign__v | Campaign | n/a | Object |
| campaign_group_action__v | campaign_activity__v | Campaign Activity | n/a | Object |
| campaign_group_action__v | campaign_group__v | Campaign Group | n/a | Object |
| campaign_group_action__v | channel__v | Channel | The channel of communication of the medical interaction. | Picklist |
| campaign_group_action__v | condition_url__v | Condition Url | n/a | Text |
| campaign_group_action__v | dependent_action__v | Dependent Action | n/a | Object |
| campaign_group_action__v | hour_offset__v | Hour Offset | n/a | Number |
| campaign_group_action__v | link__sys | Link | n/a | Text |
| campaign_group_action__v | name__v | Campaign Group Action Name | n/a | Text |
| campaign_group_action__v | status__v | Status | n/a | Picklist |
| campaign_group_action__v | targets_who__v | Targets Who | n/a | Picklist |
| case_conversation__v | external_resource_id__v | External Resource ID | n/a | Text |
| case_conversation__v | initiating_user__v | Initiating User | User who initiated the transfer action. | Object |
| case_conversation__v | initiating_user__v | n/a | Object | |
| case_conversation__v | transfer_target__v | Transfer Target | n/a | Picklist |
| case_conversation__v | transfer_type__v | Transfer Type | n/a | Picklist |
| channel_assignment__v | email_subdomain__v | Email Subdomain | Defines the Email Subdomain to be used for sending emails. If not configured the application will use the domain of the configured Mailbox. | Text |
| childaccount_tsf__v | territory__v | Child Account TSF | n/a | Object |
| childaccount_tsf__v | territory__v | Territory | n/a | Object |
| consent_header__v | consent_managed_externally__v | Consent Managed Externally | When enabled, this field prevent users from updating consent while keeping consent validation when sending emails | Yes/No |
| consent_header__v | external_consent_link_browser__v | External Consent Link (Browser) | Contains the external consent tool link, where tokens can be used to generate the link | Text |
| consent_header__v | external_consent_link_ios__v | External Consent Link (iOS) | Contains the external consent tool link, where tokens can be used to generate the link | Text |
| consent_header__v | external_consent_link_windows__v | External Consent Link (Windows) | Contains the external consent tool link, where tokens can be used to generate the link | Text |
| consent_type__v | legacy_consent_channel__v | Legacy Consent Channel | Used to reference consent collected from a legacy custom channel and reused for Veeva channel. | Text |
| consent_type__v | subscribe_keyword__v | Subscribe Keyword | Keyword (e.g., YES) that, when received from the HCP, triggers an opt-in consent record creation for the channel. | Text |
| consent_type__v | unsubscribe_keyword__v | Unsubscribe Keyword | Keyword (e.g., STOP) that, when received from the HCP, triggers an opt-out consent record update for the channel. | Text |
| dynamic_attribute_query__v | account__v | Account | n/a | Object |
| dynamic_attribute_query__v | link__sys | Link | n/a | Text |
| dynamic_attribute_query__v | name__v | Name | n/a | Text |
| dynamic_attribute_query__v | status__v | Status | n/a | Picklist |
| em_speaker__v | photo_cdn_status__v | Photo CDN Status | Indicates whether the content is published to the CDN | Picklist |
| em_speaker__v | photo_file__v | Photo | File of the speaker photo uploaded. | Attachment |
| em_speaker__v | photo_processing_status__v | Photo Processing Status | Status of the publish to CDN process | Picklist |
| em_speaker__v | photo_url__v | Photo URL | URL of the uploaded photo that will be displayed in the Event Speaker Table token in Approved Email. | URL |
| inventory_order__v | override_lock__v | Override Lock | This enables a non-Admin User to make changes to a Submitted Sample Inventory Order and lines without requiring the User to unlock the record. | Yes/No |
| inventory_order_line__v | override_lock__v | Override Lock | This enables a non-Admin User to make changes to a Submitted Sample Inventory Order and lines without requiring the User to unlock the record. | Yes/No |
| medx__v | address__v | Address | The address of the medical interaction. | Text |
| medx__v | agenda__v | Agenda | The agenda of the medical interaction. | Text |
| medx__v | attendee_count__v | Attendee Count | Number of attendees on the medical interaction. | Number |
| medx__v | attendee_list__v | Attendee List | List of attendees on the medical interaction. | Text |
| medx__v | cancelation_reason__v | Cancelation Reason | The reason the medical interaction was canceled. | Picklist |
| medx__v | channel__v | Channel | The channel of communication of the medical interaction. | Picklist |
| medx__v | created_by_device__v | Created By Device | The device used to create the medical interaction. | Picklist |
| medx__v | duration__v | Duration | Duration of the visit to the CLM Presentation Slide in seconds | Number |
| medx__v | end_datetime__v | End Time | The end date and time of the medical interaction. | DateTime |
| medx__v | last_modified_by_device__v | Last Modified By Device | The last device used to modify the medical interaction. | Picklist |
| medx__v | latitude__v | Latitude | The latitude of the address of the medical interaction. | Number |
| medx__v | link__sys | Link | n/a | Text |
| medx__v | location__v | Location | The location of the medical interaction. | Object |
| medx__v | longitude__v | Longitude | The longitude of the address of the medical interaction. | Number |
| medx__v | medx_status__v | Medical Interaction Status | Status of the Medical Interaction | Picklist |
| medx__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx__v | name__v | Name | n/a | Text |
| medx__v | ownerid__v | Owner | The user the medical interaction belongs to. | Object |
| medx__v | stage__sys | Lifecycle Stage | n/a | Object |
| medx__v | start_datetime__v | Start Time | The start data and time of the medical interaction. | DateTime |
| medx__v | state_stage_id__sys | Lifecycle State Stage ID | n/a | Object |
| medx__v | state_stage_id__sys | Objects in Stage | n/a | Object |
| medx__v | status__v | Status | n/a | Picklist |
| medx__v | title__v | Title | The title of the medical interaction. | Text |
| medx_attendee__v | account__v | Account | n/a | Object |
| medx_attendee__v | audio_recording_consent_datetime__v | Audio Recording Consent Datetime | The datetime the audio recording consent was provided. | DateTime |
| medx_attendee__v | audio_recording_consent_signature__v | Audio Recording Consent Signature | The audio consent signature, encoded using base64. | Text |
| medx_attendee__v | link__sys | Link | n/a | Text |
| medx_attendee__v | medx__v | Medical Interaction | Reference to the Medical Interaction | Object |
| medx_attendee__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_attendee__v | name__v | Name | n/a | Text |
| medx_attendee__v | status__v | Status | n/a | Picklist |
| medx_component__v | documented_interest__v | Documented Interest | The documented interest record connected to the attendee and/or the medical interaction. | Object |
| medx_component__v | link__sys | Link | n/a | Text |
| medx_component__v | medical_inquiry__v | Medical Inquiry | The medical inquiry record connected to the attendee and/or the medical interaction. | Object |
| medx_component__v | medical_insight__v | Medical Insight | The medical insight record connected to the attendee and/or the medical interaction. | Object |
| medx_component__v | medx__v | Medical Interaction | Reference to the Medical Interaction | Object |
| medx_component__v | medx_attendee__v | MedX Attendee | Reference to the Medical Interaction Attendee | Object |
| medx_component__v | medx_discussion__v | MedX Discussion | n/a | Object |
| medx_component__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_component__v | name__v | Name | n/a | Text |
| medx_component__v | sequence__v | Sequence | The sequence of the component on the medical interaction. | Number |
| medx_component__v | status__v | Status | n/a | Picklist |
| medx_discussion__v | discussion_text__v | Discussion Text | The details of the discussion. | Text |
| medx_discussion__v | link__sys | Link | n/a | Text |
| medx_discussion__v | medx_discussion_status__v | Discussion Status | Status of the Medical Interaction Discussion | Picklist |
| medx_discussion__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_discussion__v | name__v | Name | n/a | Text |
| medx_discussion__v | response_type__v | Response Type | The response type of the discussion. | Picklist |
| medx_discussion__v | status__v | Status | n/a | Picklist |
| medx_discussion_material__v | link__sys | Link | n/a | Text |
| medx_discussion_material__v | medx_discussion__v | MedX Discussion | n/a | Object |
| medx_discussion_material__v | medx_meeting_material__v | MedX Meeting Material | n/a | Object |
| medx_discussion_material__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_discussion_material__v | name__v | Name | n/a | Text |
| medx_discussion_material__v | status__v | Status | n/a | Picklist |
| medx_key_message__v | account__v | Account | n/a | Object |
| medx_key_message__v | category__v | Category | Stamped category of the Key Message of the CLM Presentation Slide | Picklist |
| medx_key_message__v | clm_id__v | CLM ID | Media File Name of the Key Message of the CLM Presentation Slide | Text |
| medx_key_message__v | clm_presentation__v | CLM Presentation | n/a | Object |
| medx_key_message__v | clm_presentation__v | Reference to the CLM Presentation | n/a | Object |
| medx_key_message__v | clm_presentation_id__v | CLM Presentation ID | Stamped ID of the CLM Presentation | Text |
| medx_key_message__v | clm_presentation_name__v | CLM Presentation Name | Stamped name of the CLM Presentation | Text |
| medx_key_message__v | clm_presentation_version__v | CLM Presentation Version | Version of the CLM Presentation | Text |
| medx_key_message__v | date__v | Date | The date of the Medical Interaction | Date |
| medx_key_message__v | detail_group__v | Detail Group | Reference to the Detail Group of the Key Message of the CLM Presentation Slide | Object |
| medx_key_message__v | display_order__v | Display Order | The display order of CLM Presentation Slides presented on the Medical Interaction | Number |
| medx_key_message__v | duration__v | Duration | Duration of the visit to the CLM Presentation Slide in seconds | Number |
| medx_key_message__v | key_message__v | Key Message | Reference to the Key Message of the CLM Presentation Slide | Object |
| medx_key_message__v | key_message_name__v | Key Message Name | Stamped name of the Key Message of the CLM Presentation Slide | Text |
| medx_key_message__v | link__sys | Link | n/a | Text |
| medx_key_message__v | medx__v | Medical Interaction | Reference to the Medical Interaction | Object |
| medx_key_message__v | medx_attendee__v | MedX Attendee | Reference to the Medical Interaction Attendee | Object |
| medx_key_message__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_key_message__v | name__v | Name | n/a | Text |
| medx_key_message__v | product__v | Product | Reference to the Product of the Key Message of the CLM Presentation Slide | Object |
| medx_key_message__v | reaction__v | Reaction | Reaction to the Key Message | Picklist |
| medx_key_message__v | segment__v | Segment | Stamped segment of the Key Message of the CLM Presentation Slide | Text |
| medx_key_message__v | share_method__v | Share Method | The method through which the Key Message was shared | Picklist |
| medx_key_message__v | slide_version__v | Slide Version | Version of the CLM Presentation Slide | Text |
| medx_key_message__v | start_time__v | Start Time | Start Time when the CLM Presentation Slide was visited | DateTime |
| medx_key_message__v | status__v | Status | n/a | Picklist |
| medx_meeting_material__v | clm_presentation__v | CLM Presentation | n/a | Object |
| medx_meeting_material__v | document_unbound__v | Document (unbound) | n/a | Number |
| medx_meeting_material__v | link__sys | Link | n/a | Text |
| medx_meeting_material__v | medx__v | Medical Interaction | Reference to the Medical Interaction | Object |
| medx_meeting_material__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| medx_meeting_material__v | name__v | Name | n/a | Text |
| medx_meeting_material__v | status__v | Status | n/a | Picklist |
| message_template__v | category__v | Category | Stamped category of the Key Message of the CLM Presentation Slide | Picklist |
| message_template__v | detail_group__v | Detail Group | Reference to the Detail Group of the Key Message of the CLM Presentation Slide | Object |
| message_template__v | hidden__v | Hidden? | Flag to indicate if the template should be hidden from the chat UI for manual selection. | Yes/No |
| message_template__v | product__v | Product | Reference to the Product of the Key Message of the CLM Presentation Slide | Object |
| message_template__v | template_type__v | Template Type | Template type is defined based on the intended usage of the Message Template. | Picklist |
| message_template__v | whatsapp_body_placeholder__v | WhatsApp Body Placeholder | Details of what the placeholder in the body should be replaced with. | Text |
| message_template__v | whatsapp_body_text__v | WhatsApp Body Text | Main message body shown to the HCP in WhatsApp. | Text |
| message_template__v | whatsapp_button_1_placeholder__v | WhatsApp Button 1 Placeholder | Details of what the placeholder in the first button should be replaced with. | Text |
| message_template__v | whatsapp_button_1_text__v | WhatsApp Button 1 Text | Label shown for the first button. | Text |
| message_template__v | whatsapp_button_1_type__v | WhatsApp Button 1 Type | Type of the first button displayed at the bottom of the message. | Picklist |
| message_template__v | whatsapp_button_1_value__v | WhatsApp Button 1 Value | The actionable value (eg. URL, phone number, etc) for the first button. | Text |
| message_template__v | whatsapp_button_2_placeholder__v | WhatsApp Button 2 Placeholder | Details of what the placeholder in the second button should be replaced with. | Text |
| message_template__v | whatsapp_button_2_text__v | WhatsApp Button 2 Text | Label shown for the second button. | Text |
| message_template__v | whatsapp_button_2_type__v | WhatsApp Button 2 Type | Type of the second button displayed at the bottom of the message. | Picklist |
| message_template__v | whatsapp_button_2_value__v | WhatsApp Button 2 Value | The actionable value (eg. URL, phone number, etc) for the second button. | Text |
| message_template__v | whatsapp_button_3_placeholder__v | WhatsApp Button 3 Placeholder | Details of what the placeholder in the third button should be replaced with. | Text |
| message_template__v | whatsapp_button_3_text__v | WhatsApp Button 3 Text | Label shown for the third button. | Text |
| message_template__v | whatsapp_button_3_type__v | WhatsApp Button 3 Type | Type of the third button displayed at the bottom of the message. | Picklist |
| message_template__v | whatsapp_button_3_value__v | WhatsApp Button 3 Value | The actionable value (eg. URL, phone number etc) for the third button. | Text |
| message_template__v | whatsapp_footer_text__v | WhatsApp Footer Text | Footer text displayed at the bottom of the message. | Text |
| message_template__v | whatsapp_header_placeholder__v | WhatsApp Header Placeholder | Details of what the placeholder in the header should be replaced with. | Text |
| message_template__v | whatsapp_header_text__v | WhatsApp Header Text | Text content of the header if 'Text' is selected as the header type. | Text |
| message_template__v | whatsapp_header_type__v | WhatsApp Header Type | Defines the type of content in the header. | Picklist |
| message_template_business_account__v | link__sys | Link | n/a | Text |
| message_template_business_account__v | message_template__v | Message Template | Determines which Message Template to use. | Object |
| message_template_business_account__v | messaging_business_account__v | Messaging Business Account | The Messaging Business Account that the template is associated with. | Object |
| message_template_business_account__v | name__v | Name | n/a | Text |
| message_template_business_account__v | status__v | Status | n/a | Picklist |
| message_template_business_account__v | vexternal_id__v | Veeva External Id | n/a | Text |
| messaging_business_account__v | connection_datetime__v | Connection Datetime | The datetime at which the Messaging Business Account was successfully connected to Vault. | DateTime |
| messaging_business_account__v | connection_status__v | Connection Status | Connection status of the Messaging Business Account. | Picklist |
| messaging_business_account__v | country__v | Country | The country of the Messaging Business Account. | Object |
| messaging_business_account__v | country__v | The country of the Messaging Business Account. | The country of the Messaging Business Account. | Object |
| messaging_business_account__v | external_id__v | External Id | n/a | Text |
| messaging_business_account__v | link__sys | Link | n/a | Text |
| messaging_business_account__v | name__v | Name | n/a | Text |
| messaging_business_account__v | primary_asgnee_for_new_inbound_chat__v | Primary Assignee for New Inbound Chat | User who will be assigned new inbound messages when received on this Messaging Business Account. | Object |
| messaging_business_account__v | secondary_asgnee_for_new_inbound_chat__v | Secondary Assignee for New Inbound Chat | Fallback user who receives the message if the primary assignee is inactive. | Object |
| messaging_business_account__v | status__v | Status | n/a | Picklist |
| messaging_phone_number__v | data_storage_geolocation__v | Data Storage Geolocation | Indicates where the data related to the WhatsApp Business Account is stored. | Picklist |
| messaging_phone_number__v | display_name__v | Display Name | The name shown to HCPs in the messaging app when messaging with the phone number. | Text |
| messaging_phone_number__v | external_id__v | External Id | n/a | Text |
| messaging_phone_number__v | link__sys | Link | n/a | Text |
| messaging_phone_number__v | name__v | Name | n/a | Text |
| messaging_phone_number__v | number__v | Number | The actual phone number used for messaging, linked to the Messaging Business Account. | Text |
| messaging_phone_number__v | status__v | Status | n/a | Picklist |
| messaging_phone_number__v | whatsapp_business_account__v | WhatsApp Business Account | The WhatsApp Business Account to which the phone number is linked. | Object |
| messaging_phone_number__v | whatsapp_business_phone_number_id__v | WhatsApp Business Phone Number Id | The unique identifier assigned by Meta to the WhatsApp phone number. | Text |
| multichannel_consent__v | legacy_consent_channel__v | Legacy Consent Channel | Used to reference consent collected from a legacy custom channel and reused for Veeva channel. | Text |
| multichannel_consent__v | opt_method__v | Opt Method | Details of how the consent was captured. | Text |
| multichannel_route__v | event__v | Event | The event that triggers sending of the Message Template. | Picklist |
| multichannel_route__v | message_template__v | Message Template | Determines which Message Template to use. | Object |
| pal_int_context__v | feature_key__v | Feature Key | n/a | Text |
| pal_int_context__v | feature_tag__v | Feature Tag | n/a | Text |
| pal_int_context__v | link__sys | Link | n/a | Text |
| pal_int_context__v | name__v | Name | n/a | Text |
| pal_int_context__v | pal_expiration_date__sys | Public Access Link Expiration Date | n/a | DateTime |
| pal_int_context__v | pal_last_accessed_date__sys | Public Access Link Last Accessed Date | n/a | DateTime |
| pal_int_context__v | pal_status__sys | Public Access Link Status | n/a | Picklist |
| pal_int_context__v | pal_type__sys | Public Access Link Type | n/a | Text |
| pal_int_context__v | source_context__v | Source Context | n/a | Object |
| pal_int_context__v | status__v | Status | n/a | Picklist |
| pal_int_context__v | system_owned_user__v | System Owned User | n/a | Text |
| preferences__v | last_account_type__v | Last Account Type | n/a | Picklist |
| profiling_attribute__v | color__v | Color | The color of the profile attribute. | Picklist |
| profiling_attribute__v | detail_group__v | Detail Group | Reference to the Detail Group of the Key Message of the CLM Presentation Slide | Object |
| profiling_attribute__v | detail_group__v | Profiling Attributes (Detail Group) | Reference to the Detail Group of the Key Message of the CLM Presentation Slide | Object |
| profiling_attribute__v | field__v | Field | n/a | Text |
| profiling_attribute__v | link__sys | Link | n/a | Text |
| profiling_attribute__v | name__v | Name | n/a | Text |
| profiling_attribute__v | object__v | Object | n/a | Picklist |
| profiling_attribute__v | product__v | Product | Reference to the Product of the Key Message of the CLM Presentation Slide | Object |
| profiling_attribute__v | profiling_template__v | Profiling Template | n/a | Object |
| profiling_attribute__v | sequence__v | Sequence | The sequence of the component on the medical interaction. | Number |
| profiling_attribute__v | status__v | Status | n/a | Picklist |
| profiling_attribute__v | type__v | Column Type | n/a | Picklist |
| profiling_sheet__v | comment__v | Comment | n/a | Text |
| profiling_sheet__v | link__sys | Link | n/a | Text |
| profiling_sheet__v | mobile_id__v | Mobile ID | System field used by mobile products. | Text |
| profiling_sheet__v | name__v | Name | n/a | Text |
| profiling_sheet__v | number_of_changes__v | Number of Changes | n/a | Number |
| profiling_sheet__v | ownerid__v | Owner | The user the medical interaction belongs to. | Object |
| profiling_sheet__v | profiling_sheet_status__v | Profiling Sheet Status | n/a | Picklist |
| profiling_sheet__v | profiling_template__v | Profiling Template | n/a | Object |
| profiling_sheet__v | stage__sys | Lifecycle Stage | n/a | Object |
| profiling_sheet__v | state_stage_id__sys | Lifecycle State Stage ID | n/a | Object |
| profiling_sheet__v | state_stage_id__sys | Objects in Stage | n/a | Object |
| profiling_sheet__v | status__v | Status | n/a | Picklist |
| profiling_template__v | account_types__v | Account Types | Filters which account types will be visible on the profiling sheet | Text |
| profiling_template__v | country__v | Country | The country of the Messaging Business Account. | Object |
| profiling_template__v | description__v | Description | Description of the profiling template | Text |
| profiling_template__v | detail_group__v | Detail Group | Reference to the Detail Group of the Key Message of the CLM Presentation Slide | Object |
| profiling_template__v | due_date__v | Due Date | Due date for the profiling template | Date |
| profiling_template__v | instructions__v | Instructions | User instructions of the profiling template | Text |
| profiling_template__v | link__sys | Link | n/a | Text |
| profiling_template__v | name__v | Name | n/a | Text |
| profiling_template__v | product__v | Product | Reference to the Product of the Key Message of the CLM Presentation Slide | Object |
| profiling_template__v | stage__sys | Lifecycle Stage | n/a | Object |
| profiling_template__v | state_stage_id__sys | Lifecycle State Stage ID | n/a | Object |
| profiling_template__v | state_stage_id__sys | Objects in Stage | n/a | Object |
| profiling_template__v | status__v | Status | n/a | Picklist |
| profiling_template__v | user_type__v | User Type | Filters which users types will have access to this profiling template | Picklist |
| remote_meeting__v | zoom_meeting_external_id__v | Zoom Meeting External Id | This field stores the Zoom meeting external Id. | Text |
| remote_meeting__v | zoom_meeting_join_link__v | Zoom Meeting Join Link | This is the meeting link that can be used to start or join the Zoom meetings. | Text |
| remote_meeting__v | zoom_meeting_start_link__v | Zoom Meeting Start Link | This is the meeting link used by the system to enable hosts to start Zoom meetings. This should not be shared with attendees. | Text |
| sent_message__v | mc_capture_datetime__v | MC Capture Datetime | The capture datetime of the Multichannel Consent record which enableed this message to be sent. | DateTime |
| user__sys | enable_zoom__v | Enable Zoom | Setting this to true enables the Zoom integration for this user. | Yes/No |
| user__sys | whatsapp_phone_number__v | WhatsApp Phone Number | The WhatsApp phone number assigned to the user for sending and receiving WhatsApp messages. | Object |
| veeva_settings__v | medx_audio_and_transcript__v | MedX Audio and Transcript | Determines medical interaction audio and transcript setting. | Picklist |
| veeva_settings__v | medx_audio_and_transcript_consent__v | MedX Audio and Transcript Consent | Determines the method of consent capture for medical interaction audio and transcript. | Picklist |
