Announcements

The announcements below are applicable with the current general release and future releases. Announcements applicable to previous general releases are available in the archives.

User Group Membership Limits in 26R3 & 27R1 Platform

Published: October 5, 2026

In the 27R1 release, Vault will enforce a maximum limit of 20,000 group memberships per user. This enforcement prevents search timeouts to preserve overall system performance. When the 27R1 limit goes into effect, Vault will block any new group assignments that push a user over the 20,000 threshold. This restriction applies across all manual and programmatic assignment paths, including the Admin UI, Public API, Vault User Detail page, and User Role Setup (URS) record creation. Existing group memberships above the threshold remain intact, but Vault will reject new additions.

To help Admins prepare, the 26R3 release introduces a warning triangle icon and an informative tooltip on the User Profile page and the Vault User Detail page. Vault displays this warning for any user currently assigned to more than 20,000 groups, allowing Admins to identify and consolidate affected accounts before the maximum limit is enforced.

Note: System-managed group assignments driven by Security Profile changes remain exempt from this limit to ensure essential access controls continue without interruption.

Entry Criteria Validation User Experience Changes in 27R1 Platform

Published: October 5, 2026

The upcoming 27R1 release includes improvements to the Vault user experience and interface for users working with documents and objects with a lifecycle.

The new Entry Criteria Validation UI streamlines resolving entry criteria validation errors when users initiate workflow and lifecycle actions. Instead of halting the process with a system error, Vault presents entry criteria validation errors in a dedicated user interface, enabling users to resolve issues and complete their actions more efficiently.

This new UI is planned to release in 27R1 and will be enabled automatically. Users can preview the changes in Limited Release and Prerelease Vaults before the changes are applied to General Release Vaults.

Checklist Fields Inactivated & Duplicate Available Answer Records Deleted in 27R1 Platform

Published: October 5, 2026

With the Available Answer and Comment checklist enhancements for Vault Platform released in 25R2, the below fields are no longer used by checklists but remained Active to preserve existing Vault configurations and customer integrations. These fields will be set to Inactive in 27R1.

  • The Translation Versions field on the [Target Object] Checklist object
  • The Comment field on the [Target Object] Response object
  • The Answer field on the [Target Object] Dependency object
  • The following fields on the [Target Object] Available Answer object:
    • Response
    • Selected
    • Order

Duplicate [Target Object] Available Answer records will also be deleted in 27R1.

The Hash Code field on the [Target Object] Available Answer object may also be set to Inactive, pending additional investigation, and this Announcement will be updated in the future with more information.

New Learner Homepage in 27R1 Quality

Published: October 5, 2026

Coming in 27R1 will be the new Learner Homepage. You will see significant UI changes that reflect the needs expressed by customers. This feature will be Auto-on, so it will automatically update for your Learners.

This revamped page will show two tabs within My Learning: The My Plan tab shows both complete and incomplete training in the context of Learner Roles and Curricula, and the To Do tab shows a pared-down view of only training to be completed, organized by assignment due date.

The My Plan tab is ideal for newcomers or newly-assigned employees to understand the context of their training. The To Do tab helps the Learner easily maintain their ongoing training.

These improvements shown in the screenshots below are subject to change upon release.

New Learner Homepage in 27R1

New Learner Homepage in 27R1

Auto Enablement of Copy Enhancements for Activities & Protocols in 27R1 Quality

Published: October 5, 2026

In the 27R1 general release, the Copy Enhancements for Activities & Protocols feature will be enabled in all Vaults, and the related Application Setting will be removed. This feature improves the deep copy engine for Validation Activities and Test Protocols to performantly handle high-volume copies, doubling the previous capacity from 5,000 to 10,000 records.

Next Steps

Admins should enable the Copy Enhancements for Activities & Protocols feature in Admin > Settings > Application Settings.

Enforced Enablement of Additional Prompts in 27R1 Quality

Published: October 5, 2026

Test Step Additional Prompts was released as a configuration enabled feature for Validation Management in 23R3. The feature allows Test Steps to be extended beyond the standard Procedure, Expected Result, and Actual Result elements, providing additional instructional capabilities (Text Instruction or Reference Instructions added in 25R3) or response capture (Text, Number, or Date/Time). Currently, Validation Management App Pages (Author Test, Execute Test) check if a user has the necessary permissions for Additional Prompts only if the Test Script or Test Protocol contains Additional Prompt records.

With the 27R1 release, users will be required to have permissions to read Additional Prompts at all times to access Validation Management App pages. Customers who have not yet updated their permission sets will be required to complete the necessary configuration. Impacted customers have been identified and will be contacted and supported through this configuration change.

Milestone Autocompletion Excludes Pending Decision in 27R1 Clinical Operations

Published: October 5, 2026

Starting in 27R1, Milestones will no longer autocomplete if they have any Expected Documents set to a Requiredness value of Pending Decision or Optional. This reduces the risk of prematurely advancing study timelines based on incomplete documentation.

Additionally, the Total EDL Items field will now include the count of Pending Decision and Optional Expected Documents in addition to Required Expected Documents. This ensures that a Milestone’s % Complete field reflects the total amount of work remaining on a Milestone. A new Total Pending Decision EDL Items field will also be available to reflect the number of Expected Documents that are still Pending Decision or Optional.

These changes will be Auto-On in Vaults with Milestone Autocompletion configured.

To prepare for this change, Admins should consider the following actions:

  • Review Template EDLs to ensure Expected Documents are appropriately set to Pending Decision or Optional for the specific Milestone where they expect users to make a decision between Not Required and Required
  • Consider implementing the “EDL items are not Pending Decision” entry criteria for all Milestone completion, or continue to allow users to manually complete milestones without this criteria.

See How to Set Up Milestone Autocompletion and Milestone Gating to learn more.

Clinical Operations License Enforcement in 27R1 Clinical Operations

Published: October 5, 2026

Effective 27R1, Vault will begin enforcing limits on active Study Site licenses to help Vault Owners and Admins better manage site allocations and remain within the licenses threshold. Additional details regarding the warnings and restrictions will be shared closer to the release date.

To prepare for this update ahead of the 27R1 release, Admins should review their organization’s current license usage by navigating to Admin > About > Vault Information or Business Admin > Study Site Licenses, and contact their Veeva Account Partner if license adjustments are needed.

Person Name Standardization & Migration in 26R3 Clinical Operations

Published: September 17, 2026

In 26R3, new system fields for Prefix, Middle Name, and Suffix (__sys) will be provisioned across the User, Person, and Prior Person objects. On release night, all Clinical Operations Vaults will migrate existing values from the legacy (__v) Person fields to these new system fields. This will apply for all Person records except Cross Domain Persons and VeevaID Persons (for which the VeevaID portal is the source of truth). After the release, any subsequent updates to the legacy fields will continuously sync to the new system fields to help maintain consistency.

Admins should transition all relevant configurations and integrations to the new system fields and inactivate the legacy fields. For more details, please review the 26R3 Announcement: Person Name Standardization & Migration Veeva Connect Post.

Document Intake Highlighter Panel Enabled in All Vaults in 26R2 Safety

Published: September 9, 2026

To allow all customers easy access to the Document Intake Highlighter panel, the Enable Intake Document Highlighter intake setting checkbox is automatically selected in all Vaults.

Deprecation of Grouping of Change Items Feature in 26R3 Regulatory

Published: July 30, 2026

Following the roll-out of RIM’s Assess Local Activities feature, the Grouping of Change Items feature will be deprecated in 26R3.

After the 26R3 release, customers will no longer see the Enable Grouping of Change Items by Product Family Application Setting or its related functionality in their Vaults, even if it was previously enabled.

To prepare for this change, do not enable this setting in your production Vault.

Reach out via Veeva Connect if you have any questions.

Literature Support Added in 26R2 Safety

Published: July 13, 2026

With the 26R2 release, Veeva Safety Suite introduces literature support to the Veeva Safety application, allowing Safety users to access literature functionality. To configure literature functionality for your Safety application users, enable literature features as applicable to your business processes.

Scheduled Data Export Deprecation in 26R3 Platform

Published: June 15, 2026

As a reminder, the Scheduled Data Export functionality will be removed from all Vaults in 26R3. Customers should leverage implementations using Vault Loader APIs or Direct Data API. This deprecation has been preceded by limitations introduced to Scheduled Data Exports in releases over the last year.

End of Support for EU MIR 7.2.1 in 26R3 Quality

Published: June 15, 2026

In the 26R3 general release, Vault will not support the EU MIR 7.2.1 form.

Transition Timeline

In 26R2, users can still generate XML and PDF for the old EU MIR 7.2.1 version. However, not all functionality supported by the EU MIR 7.3.1 may work for older forms. In 26R3, the support for EU MIR 7.2.1 will be completely removed.

Next Steps

Admins should enable EU MIR 7.3.1 from Admin > Settings > Application Settings > Product Surveillance in 26R2.

End of Support for MedTech Complaint Details Object in 26R3 Quality

Published: June 15, 2026

In the 26R3 general release, the standard data mapping for Adverse Event Reports will stop using the MedTech Complaint Details object.

Transition Timeline

In the 26R2 release, Vault may still generate the submission documents successfully if you are using the MedTech Complaint Details object, but some data mapping may not fully be available. The ability to generate documents will be completely removed in 26R3.

Next Steps

Users should stop using the MedTech Complaint Details object and transition to the fields on the Adverse Event Report or Complaint object in 26R2.

Future Scalable APIs in 26R2 Regulatory

Published: June 15, 2026

With 26R2, RIM Submissions Archive has introduced several new API endpoints that will be the standard API to use moving into the future.

In 26R3, Submissions Archive will no longer generate Vault Binder substructures, and instead only create the top-level Vault Binder (Submissions Archive > Structure).

End of Support for RIM Submissions Archive: Bulk Export from Vault Report in 26R3 Regulatory

Published: October 7, 2026

As part of the phased Submissions Archive Scalability Improvements that started in 26R2, Vault is sunsetting the Bulk Export via Vault Report from Submissions Archive in the 26R3 general release. As of 26R3, you can no longer use reports with the Application Product Country Indication or Submission Application Regulatory Objective report types to access the Export Submissions Archive Applications bulk action from the All Actions menu.

If you use custom object types on the Application and Submission objects, and you import or publish submissions into the Submissions Archive on those objects, you must plan to update your configuration and security configuration.

Next Steps

To ensure business continuity for your bulk exports from Submissions Archive, Vault Admins must complete the following steps:

  • Assess the Submission and Application object types currently in use.
  • Enable the Bulk Export from Submissions Archive (bulk_export_from_submissions_archive__v) object action on the applicable object types.
  • Assess permission sets. In 26R3, users require the File Staging: Access permission to:
    • Initiate the Bulk Export from Submissions Archive record action.
    • Initiate single submission export for a submission that is larger than 5 GB. When submissions are 5 GB or larger, they are automatically exported to Vault’s file staging.

Vault AI General Availability in 26R2 Platform

Published: June 15, 2026 | Last Updated: July 30, 2026

Functionality Description
Vault AI Tab ChatGPT-style home tab where users can ask questions based on the data in Vault. This feature is only available to early adopters in 26R2.
Query Agent Allows Vault to convert natural language into Vault Query Language (VQL) to return the right information to users.
Document Chat Agent When viewing a document, users can ask questions, have AI summarize or translate the document, and get a summary of changes since the last major version.
Object Chat Agent When viewing an object record, users can ask questions, and have AI summarize or translate the record.
Document Version Compare Agent Provides a summary of changes in a document compared to the last major version, including links to highlighted changes and the ability for users to ask for more detailed information on changes.

Vault AI General Availability in 26R2

Vault AI General Availability in 26R2

Standard application agents may also be available depending on the Vault application. Refer to your application family’s Vault Help for more info on standard agents.

Improvements to existing agents are planned bi-weekly between 26R2 and 26R3, with additional agents planned in 26R3.

With Vault AI enabled, you will also be able to configure custom agents. We recommend taking the relevant Education Services courses and working with the Veeva Services team for these use cases.

To enable Vault AI, there is a process which requires an agreement (a zero-dollar order form). Reach out to your Account Partner if interested.

Deprecation of Auto-Linking Icon in Document Viewer Toolbar in PromoMats and MedComms Vaults in 26R2 CommercialMedical

Published: June 15, 2026

With the 26R2 release, an improved document viewer will be available to customers, including a streamlined document viewer toolbar. With this update, the Auto-Linking () icon is moved from the toolbar into a Suggest Links user action located in the Annotate section of the All Actions menu.

We recommend using the Text Asset Auto-Linking Settings page (PromoMats) or the Scientific Statement Auto-Linking Settings page (MedComms) where you can configure Auto-Linking to run automatically when a document is uploaded or moved to a new state based on selected document lifecycles and lifecycle states.

To learn more about the Text Asset Auto-Linking Settings, see 26R1 Feature Spotlight: Text Assets (Claims and Reusable Text) - Auto-Linking Settings on Veeva Connect.

Agentic Case Management in MedInquiry in 26R2 Quality

Published: June 15, 2026

A new dedicated Case Management UI is available in the 26R2 general release for MedInquiry. This allows users to handle a medical inquiry throughout the lifecycle of the Case, from intake to constructing an answer and sending a response to the HCP. All information about the Case is displayed in one place, including the Case Contact, each Case Request and its associated Response, and any Adverse Events and Product Quality Complaints. To the left of the UI is a timeline panel, which shows a chronological list of the interactions with the HCP, such as Emails, Phone Calls, and Chats.

The Case Management UI supports an AI-enabled user experience. For inquiries ingested via email, the Case Processing Agent analyses the email and creates the relevant Case Requests, Adverse Events, and Product Quality Complaints, with structured fields populated. This removes manual tasks for the user, enhancing accuracy and efficiency.

Improved Document Viewer in 26R2 Platform

Published: April 6, 2026 | Last Updated: June 15, 2026

In 26R2, we will release a new and improved document viewer. These features will be auto-on in the 26R2 release. The improvements focus on the following functionality:

  • Simplified user experience with a streamlined document viewer toolbar
  • Improved full-screen viewing mode to maximize content display
  • Quick access to a personalized set of documents via the search bar
  • Improved side-by-side document viewing options
  • One-click version compare with an AI Summary (available for customers with Veeva AI enabled)
  • Expanded zoom control capabilities

Here is a preview of the new design:

Improved Document Viewer in 26R2

See 26R2 Feature Spotlight: Improved Document Viewer on Veeva Connect for additional information.

More Responsive User Experience in 26R2 Platform

Published: April 6, 2026

In 26R2, we will improve the experience when using Vault with different browser sizes. Responsive design principles will be used to adjust the layout according to the available display width. This provides subtle but valuable enhancements including reduced scrolling, better multi-tasking, and reduction of unnecessary whitespace.

Increased Flexibility for Document Inbox Processing in 26R2 Platform

Published: April 6, 2026

In 26R2, we will be introducing updates to the Document Inbox experience so that users can classify documents without fully completing them. When a user edits an incomplete document, they will be able to select and save a new document type, even if they do not complete all the remaining document fields.

Additionally, the Unclassified lifecycle state label will be relabeled to Incomplete, and the Complete action in the Document Inbox will be renamed to Edit.

Documents will continue to remain in the Document Inbox until all required document fields are provided. While these changes should not have much impact on current users or business processes, this new capability may be a consideration for future business process changes in your organization.

Published: April 2, 2026 | Last Updated: June 15, 2026

With the 26R2 release, the legacy Auto-Link on Initial Upload Admin checkbox has been fully removed. Admins should use the Text Asset Auto-Linking Settings page that was introduced in 26R1 to define the specific document lifecycle states in which Auto-Linking runs. This capability simplifies the user experience by automatically running the process when new document versions are uploaded in controlled states or when documents move to those states.

As the legacy checkbox is no longer available, we recommend that customers transition to the new settings page to maintain their desired Auto-Linking behavior.

To learn more about the Text Asset Auto-Linking Settings, see 26R1 Feature Spotlight: Text Assets (Claims and Reusable Text) - Auto-Linking Settings on Veeva Connect.

Deprecation of Legacy Site Capabilities in 27R3 Clinical Operations

Published: March 27, 2026

In 27R3, Veeva is decommissioning several legacy site-related capabilities. This applies strictly to the features listed below.

Scope of Deprecation

After the 27R3 release, these capabilities will not be accessible by Veeva Clinical Operations customers or their sites.

Deprecation of these features does not impact Site Connect, as these capabilities have all been replaced by Veeva Site Connect.

Changes to Document Set Data Model in 26R2 Regulatory

Published: March 19, 2026

In 25R3, a new Document Set object data model was introduced to replace the previous picklist model. As part of these capabilities, Document Set assignment was made available at the Content Plan section level within Global Content Plans (GCPs). However, this specific capability will be deprecated in the upcoming 26R2 release. For Vaults with the Enable Improved Document Set Management Application setting enabled, this change will be applied automatically in 26R2; consequently, users will only assign Document Sets to Content Plan Items.

For Vaults where this setting is still disabled, enablement will be required for all RIM Vaults in the 26R3 release. See 26R3 Announcement: Enforcing the Document Set Object Model for Global Content Plans (GCP) on Veeva Connect for more information.

Report Usage and Last Ran Date in 26R2 Platform

Published: March 17, 2026

In 26R2, more detail will be available to customers around how their reports are used with a new Report Usage object. As part of this change, the existing Last Ran field on reports will be deprecated and no longer an available column when viewing reports in a list view. Last Ran will still show when viewing flash reports or dashboards. Users can create Report Usage reports to get more details across all reports, including the Last Ran Date.

eCTD Redline Annotations Enabled in PromoMats Vaults in 26R2 Commercial

Published: March 16, 2026

In 26R2, the Add Annotations from Vault Links Application setting will be enabled in all PromoMats Vaults. After the 26R2 release, all eCTD Compliance Packages generated with the Include Linked References setting = Yes will be generated with the new redline annotations rather than the legacy blue links. We recommend that all customers generating eCTD Compliance Packages enable this setting before the 26R2 release.

For more information about eCTD redline annotations, see Redline Annotations Feature Spotlight on Veeva Connect.

Scientific Communication Platform UI Enabled in MedComms Vaults in 26R2 Medical

Published: March 13, 2026

In 26R2, the Enable Communication Platform UI Application setting will be enabled in all MedComms Vaults. After the 26R2 release, all Communication Platform records will use the new application-specific user interface. This Scientific Communication Platform (SCP) UI displays Communication Platform records and related records on one page. We recommend all customers using Communication Platforms enable this setting before the 26R2 release.

For more information about the new SCP UI, see 25R3 Feature Spotlight: New User Interface for the Scientific Communications Platform on Veeva Connect.

Upcoming Discontinuation of Milestone Field Auto-Population in 27R1 Clinical Operations

Published: February 23, 2026 | Last Updated: June 15, 2026

The 26R1 release introduced a new Milestones document panel, which provides users with a comprehensive view of all milestones related to document versions, effectively replacing the Milestone (milestone__v) document field. The Milestone document field is now considered deprecated, and the Milestone Document (milestone_document__v) object will be used to track all milestone-document relationships going forward.

Following the 26R1 release, customers should work to transition all relevant logic to the Milestone Document object. This includes, but is not limited to, updating any reports, dashboards, web actions, merge field templates, formatted output templates, external integrations, SDKs, lookup fields or formulas that currently draw data from the Milestone document field to instead utilize the Milestone Document object. A separate data migration effort is not needed for the transition from the Milestone document field to the Milestone Document object; the 25R3 Milestone Document Version Backfill job proactively generated the necessary Milestone Document records for all document versions, ensuring that the panel is fully populated upon transition.

In the 27R1 release, we plan to stop auto-populating the Milestone document field entirely. At that time, the Manage Milestone field value by Expected Documents setting will be removed and the Milestone field will stop updating based on Expected Documents. This also means the Generate Missing Milestone Documents action, the Generate Milestone Documents API endpoint, and the Recalculate Milestone Document Field API endpoint will no longer be supported because these relied on the Milestone document field.

With these impacts in mind, it is critical that all functionality relying on the Milestone document field is transitioned to the object before the 27R1 release.

Archived Announcements

Announcements applicable to previous general releases are available in the archives.