New in 26R2 Limited Release | Veeva Vault Release Notes

Limited Release Dates: May 1, 2026 (26R1.2); June 12, 2026 (26R1.3); June 26, 2026 (26R1.4) | General Release Date: August 7, 2026

We are pleased to bring you new functionality with each limited release. These release notes are updated with upcoming new features one week before the limited release date. See the following explanations for enablement options:

Auto-on: Automatically activated and no configuration is required before using the feature; in some cases, a new feature is dependent on another feature that must be enabled or configured.
Admin Checkbox: Admins must turn on the feature with an Admin checkbox. Some “Auto-On” features have a checkbox setting that hides the feature; these will show “Auto-On.”
Configuration: Admins must configure the feature (separately from an Admin checkbox) before it is available to use or is active; for example, an Admin must add document templates before users can create documents from templates.
Available for Use: Used only by the eConsent, eCOA, and SiteVault applications. Sponsors must make a study-specific configuration change to implement new capabilities.

Platform

Highlights

Fast SearchAuto-on26R1.3

When users click into the search bar on a document tab, the suggested documents shown in the dropdown for quick access will now load faster and provide more relevant documents to users, making it easier for users to access necessary content.

Prior to 26R2, this list showed documents based on the most recently viewed documents. With 26R2, the documents shown are based on all interactions a user might have with a document, such as edits and annotations.

The performance of loading the list of documents is also improved, both when users initially click into the search box:

As well as when users begin typing text into the search box:

Additionally, this feature supports the Improved Document Viewer by providing users options to open documents in a mini-browser window or in a new split-screen view when hovering over a document:

Learn more about Searching Vault.

Improved Document ViewerAuto-on26R1.3

The document viewer now provides a simpler user experience, focused on displaying the most common document actions to users.

This includes a new vertical toolbar that includes actions like Full Screen, Zoom, and Find in Document:

Zoom controls have also been improved by introducing a new zoom slider and allowing users to enter an explicit zoom percentage:

For standard document sizes (letter, legal, A4), the zoom defaults to 100%.

Actions that open additional panels are now included on the Doc Info pane toolbar with other panel options. This includes Bookmarks, Destinations, Glossary, Thumbnail View, and Annotations:

Users can also now easily view multiple documents at once by opening documents in a mini-browser window or in a side-by-side viewer experience through Fast Search, relationships, attachments, and document versions:

Additionally, for customers with Vault AI enabled, clicking the new Version Comparison button includes a generated AI summary of changes in Vault AI Chat that shows whether there were material changes since the last major version and summarizes important changes to review.

These changes are also reflected in the external viewer used when using Send as Link to Non-Vault Users and other application-specific areas.

If Lifecycle Stages are configured, they will now only be shown on non-steady state versions.

Responsive UIAuto-on26R1.2

The Vault user interface now automatically scales to a user’s browser width, collapsing sidebars to maximize space and adjusting field layouts to reduce horizontal scrolling.

Even without adjusting browser width, users can manually collapse and expand sidebars, allowing them to focus on content over navigation, if desired.

If a sidebar is manually collapsed, Vault remembers that as a user preference across tabs.

Also, Vault now respects font size changes made within a user’s browser preferences, ensuring a consistent experience across different sites and web applications users may leverage.

Learn more about Supported Browsers.

Copy Link for RecordsAuto-on26R1.2

Vault supports a new Copy Link action for object records, allowing users to copy a clean and shortened URL to share with others. The copied link automatically redirects users to the record detail page when pasted into a browser web address bar. This new action supports new shortcut keys.

Report UsageConfiguration26R1.3

Vault now supports analyzing report runs and usage, making it easier to perform regular report maintenance activities, such as removing unused reports.

To support this enhancement, a new Report Usage (report_usage__sys) object is introduced. Admins can create a report type based on this new object:

The following data is available for analysis:

Report Name
Report API Name
Report ID
Report Run Type, including:
- Ad Hoc
- Click and Run
- Flash Report
- Run-in-Background
- Dashboard
Last Ran By
Last Ran Date
Rows Returned
View Count

This enhancement also allows Admins to report on the Report (report__sys) object itself, allowing reports to be included along with Report Usage:

As part of this change, the existing Last Ran field on reports has been deprecated and is no longer an available column when viewing reports in a list view. Last Ran is still displayed when viewing flash reports or dashboards.

Learn more about Configuring Report Types in Vault Help and Managing Reports - Best Practice Series in Veeva Connect.

Enhanced Create Report PageAuto-on26R1.3

The Create Report page has been improved to allow users to more easily identify the right report type when building reports. These improvements include the ability to search report types and their underlying objects, easily access recently viewed report types, and expand or collapse the report type list:

When a report type is selected, users can see existing reports using that report type:

Users can also view the report type definition to see the structure of the report type and its entities:

Once a report type is selected, users are prompted with an Update Report Configuration dialog, where they can name the report, add tags, and adjust the report format. For reports that include documents, this also allows users to filter by Type, Subtype, and Classification, as well as choose whether to include all versions.

This same dialog can be reopened and updated when clicking the Edit icon by the report name.

Learn more about Creating Reports.

Process Monitor: Drill DownAuto-on26R1.3

Process Monitor now provides an option to explore specific records or documents that are included in a process directly in the Process View itself. This enhancement makes it easy for users to view details of what records are contributing to cycle times across process variants.

This can be accessed as a new tab within the Process View:

Within this tab, users can edit columns, apply filters, or export details to CSV:

Users can also easily navigate to prefiltered lists of records from states or transitions in the Process Graph tab.

Learn more about Process Monitor.

Managing Documents

Document Inbox Enhancements: Edit Document TypeAuto-on26R1.3

Users can now classify Incomplete documents in the Document Inbox without providing all the required document field information. This allows users to still be able to make progress on documents even if not all required information is known yet.

Documents remain Incomplete in the Document Inbox until all required fields are completed. Vault displays a banner to make sure the user is aware that the document is not fully complete yet:

As part of this feature, labels related to the Document Inbox have been updated:

Unclassified is now Incomplete: The Unclassified lifecycle state label has been updated to Incomplete to better reflect the document’s status.
Complete is now Edit: The action to finalize a document in your Document Inbox has been renamed from Complete to Edit.

Learn more about Unclassified Documents.

Collaborative Authoring: Increase Participant Limit for Automatic MentioningAuto-on26R1.3

When using the option to automatically check out documents to collaborative authoring as part of a workflow, Vault now supports granting up to 100 workflow participants access to the document on SharePoint. This is an increase from the prior limit of 15 workflow participants.

Granting this access on check out enables these users to be @mentioned in the document before they have joined the collaboration session.

If more than 100 participants are chosen when the workflow begins, no participants are added to the document on SharePoint until they have clicked Edit in Microsoft Office.

Learn more about Collaborative Authoring Workflows.

Collaborative Authoring Logs for OAuth ErrorsAuto-on26R1.3

The Microsoft Request ID is now included when an Integration Status error exists in Admin > Settings > Checkout Settings > Collaborative Authoring with Microsoft Office. Previously, the Request ID was only included in the Collaborative Authoring Error Logs, but this would not capture errors in setting up the configuration itself. In cases where the issue may not be related to Vault functionality, Admins can provide the Request ID when raising support tickets with Microsoft to streamline issue identification and resolution.

Token refresh errors are now also included in Admin > Logs > Collaborative Authoring Error Log.

Learn more about Configuring Collaborative Authoring.

Launch Collaborative Authoring from LinkConfiguration26R1.2

For Document Notification Templates for single document workflows, Admins can now configure templates to include links to join collaborative authoring sessions directly from email notifications. This enhancement can streamline the user experience by allowing authors to more quickly work on documents that they need to author.

To enable this feature, Admins can use a new token, ${docCollaborativeAuthoringSessionLink}, in HTML link syntax.

For instance, the following notification would show the Document Name as a hyperlink that launches collaborative authoring:

<a href="${docCollaborativeAuthoringSessionLink}">${docNameNoLink}</a>

When recipients click one of these links from an email, they are required to authenticate (unless they are already authenticated in that Vault), and are then routed to a new landing page that automatically opens the document in collaborative authoring.

This enhancement applies to workflows run on single documents only (where Use workflow for single document is enabled) that are configured to use Document Notification Templates. With the HTML syntax, if including a different token to display as the link (such as ${docNameNoLink} above), the token must not resolve to its own hyperlink.

Learn more about Email & Messages Administration and Collaborative Authoring.

Dynamic Styling for Claim-Based Link AnnotationsAuto-on26R1.2

Reviewers can now quickly gauge how a Claim-based link annotation was created, as well as the current lifecycle state of the associated Claim record.

Vault now displays distinct annotation banner colors based on the method of creation. In addition, for Auto Link annotations only, when the related Claim is withdrawn, the annotation banner color changes to silver.

Vault also now displays a colored circle indicator to better highlight the related Claim’s lifecycle state.

Banner colors:

Dark blue for Claim Link, Approved Link, Document Link, and Permalink Link
Blue for Auto Link
Light blue for pending Suggested Link
Silver for Auto Link when the Claim record is withdrawn

Circle indicator colors:

Green for Approved
Red for Withdrawn
Orange for all other states

Learn more about Claim Link Annotations.

Make a Copy: Exclude Inactive Record ValuesAuto-on26R1.3

When using Make a Copy to copy a document, inactive object record values in object reference fields are no longer copied to the new document. This ensures consistency with how picklist fields behave, and ensures that inactive values are handled the same for copies as they are for new documents.

Learn more about Copying Documents.

Managing Data

Document Fields in Object Formula FieldsConfiguration26R1.2

Admins can configure formula fields on objects to use document fields if the object references one or more documents. This feature allows Admins to use or display data from a document selected in a document reference field, such as Major Version, Minor Version, Document Number, and other supported document field types.

Learn more about Configuring Formula Fields in Objects.

Control Binding for Object FieldsAuto-on26R1.2

This feature allows Admins to bind object fields to a control. In the past, Admins could only configure controls on a layout. An object field with control binding is always displayed using that control in record detail views, list views, and related object sections.

Learn more about Configuring Vault Objects.

Checklists: Dynamic QuestionsConfiguration26R1.3

Admins can now create a pool of dynamic questions for each section in a Checklist Design. From this question pool, only a random subset of these dynamic questions are created in the instantiated checklist.

To leverage this feature, the Checklist Type must include:

Dynamic Questions in Checklist Section and Contains Dynamic Questions in Section Design Optional Fields
Dynamic in Question Design Optional Fields

Once enabled, when configuring Checklist Designs, Admins can determine per Section if dynamic questions are included and how many to include in the instantiated checklist:

Then questions can be added to the dynamic question pool using the Dynamic checkbox:

A Section must contain more available dynamic questions than are expected to be displayed to users.

This feature is not supported for Quiz functionality in QualityOne Vaults.

Learn more about Configuring Checklists.

Where Used Object ActionAuto-on26R1.3

Admins can now use the Where Used action available on the object record Actions menu. When executed, this action generates a CSV report listing all references to the target record, including both blocking and non-blocking references.

Word Formatted Output: Support for GetRelatedRecords FormulaConfiguration26R1.2

When configuring Word Formatted Output templates, Admins can now leverage the GetRelatedRecords() formula in HideRowIf() and HideTableIf() syntax.

This feature allows scenarios where an Admin may need to hide a row or table based on whether or not a particular related record exists. For example, the following formula hides the Impact Assessment Summary row if no Impact Assessment records are associated to the Change Control object by combining CountA() and GetRelatedRecords():

${HideRowIf(CountA(GetRelatedRecords($impact_assessments__vr))=0)}

Learn more about Managing Word Formatted Output Templates.

User Experience

Copy Link Keyboard ShortcutAuto-on26R1.3

Users can now copy the link to a document or record using a keyboard shortcut, in addition to using the Copy Link option in the All Actions menu. This makes it fast and easy for users to copy a link to use elsewhere.

The keyboard shortcut is Shift + Ctrl + L (Windows) or Shift + Cmd + L (Mac).

Additionally, Vault displays this shortcut next to the Copy Link action:

For Vaults that don’t have Copy Link enabled on documents, this shortcut copies the URL as it currently shows in the browser.

Learn more about Vault Keyboard Shortcuts.

Timeout ImprovementsAuto-on26R1.3

When a user re-authenticates to Vault after a log out due to inactivity, they will now do so in a new window, maintaining the page they were actively working on. This makes it easier for users to immediately pick back up on their work, without having to re-navigate to the right place.

Additionally, when a user is working in multiple Vaults on the same domain in different browser tabs or windows, activity in any Vault will prevent timeout in all tabs and/or windows.

Note: This feature will be completed as part of the 26R2 general release, though it will not be available as part of the initial 26R2 release deployment. The feature will be enabled in all Vaults during the week of September 23. The feature will be available in pre-release.

Improved Localization for Number FieldsAuto-on26R1.3

This feature leverages ICU (International Components for Unicode) formatting to ensure that numbers, currencies, and percentages are displayed and edited using the appropriate format of a user’s locale. By adopting these global standards for decimal and grouping separators, Vault now provides a more consistent and intuitive experience for viewing and editing numbers across the platform.

Prior to 26R2, Number fields were displayed to users based on their locale, but data entry did not respect their locale.

For instance, some locales use a comma as a decimal separator, while others use a period. Prior to 26R2, all users, regardless of locale, had to use a decimal. If a comma was entered, Vault would identify it as an invalid character.

Going forward, if a user’s locale uses a comma (based on ICU) as a decimal separator, Vault expects that character when entering numbers, not just when viewing numbers.

For example, a user with a France (French) locale would enter a number using a comma separator:

A user with a United States locale would enter the same number using a period separator:

Additionally, this feature ensures that digit grouping characters are displayed consistently based on all locales. For example, in the United States, one million is entered as “1,000,000”, while in Germany, it is entered as “1.000.000”.

This applies to Number fields across objects, documents, workflows, reporting, and Process Monitor.

Learn more about Language & Region Settings.

Process Optimization

Layout Profiles Supported in Action TriggersConfiguration26R1.2

Admins can evaluate Layout Profiles in a condition and use Update Records and Update Current Record Action Triggers to set a Layout Profile.

Relative Date Filters in JobsAuto-on26R1.3

Admins can now configure job definitions with dynamic date-based expressions on DateTime fields using Additional Conditions, enabling automated execution based on relative date filters in addition to manual, fixed-date updates.

Analytics

Open Chart in New TabAuto-on26R1.3

When viewing a dashboard, users can now right-click on charts to open the underlying report in a new browser tab:

This enhancement makes it easier for users to view the details of dashboard data while maintaining a browser tab with the full dashboard.

Learn more about Viewing and Sharing Dashboards.

Process Monitor: Saved ResultsAuto-on26R1.3

Process Views now run in the background and save your results, allowing users to navigate away from the page while data is retrieved. Prior to 26R2, if a user navigated away before a Process View finished running, they would need to rerun the view.

Process Views can often pull a large amount of data, and this enhancement ensures that users can move on to other work while the data is retrieved. Vault sends a notification once the Process View is ready to view.

The data is saved on a Process View for 24 hours. When users return to a Process View that has previously run in the last 24 hours, the Process View displays when the data was last updated:

When exporting data, if there have been no changes to the included columns since the last time the view ran, the export occurs synchronously. If changes have been made to the included columns, the export reruns the Process View and a notification is sent once the run is complete and the export is available for download.

Learn more about Process Monitor.

Enhanced Aggregate FormulasAuto-on26R1.3

A number of enhancements are introduced to the aggregate functions in report formulas functionality that was released in 26R1. These include:

Aggregate functions are now supported in Matrix reports
A new Display aggregate at option is available to determine which grouping an aggregate formula field should display on

ParentGroupVal() is added as a new function to support calculations across two levels of grouping. It is useful to calculate percentages within a group.

Aggregate functions now support an optional filter parameter. This allows you to conditionally include or exclude records from calculations based on a boolean expression. For example: SumRows(field, field>1) or CountRows(field, if(text(state__v)=Effective, true, false)).

MinRows() and MaxRows() now support Date and DateTime fields. Previously, only Number fields were supported.
Up to 15 aggregate functions can be used in a single formula field, with an overall limit of 30 aggregate functions across all formula fields. Previously, this limit was 3 per formula field.
CountRows() now supports all field types. Previously, only the Name field was supported.

These changes provide even more flexibility to report creators and editors in performing calculations on aggregated data.

Learn more about Aggregate Formula Fields.

Add Description to Report Formula FieldsAuto-on26R1.3

Report creators and editors can now add descriptions to formula fields, making it easy for other report users to understand these fields and their purpose within a given report.

The description is visible to report viewers by hovering over the formula field column name:

Learn more about Report Formula Fields.

Show Report Formula Fields as a PercentageAuto-on26R1.3

When creating formula fields with a Return Type of Number, users can now choose whether to display results as a number or a percentage:

Learn more about Report Formula Fields.

Exclude Inactive Users in Report FiltersConfiguration26R1.2

Reports can now exclude inactive users from being available in report filters and prompt dropdowns. This can be controlled for all reports with the Allow inactive users to be used in reports Admin checkbox in Admin > Settings > General Settings:

If enabled at the Vault level, users can still choose to exclude inactive users on a case-by-case basis using a new Show inactive users checkbox in Advanced Options when creating and editing reports:

Both checkboxes are selected by default to maintain current behavior.

Learn more about Creating Reports.

Permissions & Access

VeevaID Contextual Help for Personal Detail UpdatesAuto-on26R1.3

When VeevaID users update their personal details in the My Account tab, Vault now requires them to provide acknowledgement that the changes they are making are correct. This enhancement helps increase user awareness around potential downstream impacts of incorrect updates.

If the user is updating their email, they will acknowledge that they are providing their official business email, and it is not a shared email address:

When users update their other personal details, they will acknowledge the changes, and specifically that they are providing legal name information that matches official identification documentation:

Learn more about About VeevaID.

Enforce Atomic Security in Audit LogsAuto-on26R1.2

When a user is restricted from seeing certain fields via Atomic Security, any updates to these fields are hidden when the user views an individual object record audit trail. Prior to 26R2, users could still see information through the audit trail about fields that were restricted elsewhere via Atomic Security, which often meant that Admins would need to remove permissions to the audit trail altogether for these users.

This enhancement ensures users can have the ability to see record audit trails while respecting any applicable field-level Atomic Security. This enhancement does not apply to the Object Record Audit History in Admin > Logs, and applies specifically to object records (as field-level Atomic Security is not available for documents).

Learn more about Configuring Atomic Security on Fields and Viewing Audit Trails.

Admin Experience

API Access TokensAuto-on26R1.3

This feature allows users to use a long-lived API token to authenticate to the Vault API. This enables integration with tools including MS Entra Id SCIM as well as allowing authentication sub-processes in integrations to be replaced.

Tokens do not provide Vault UI access, are valid for one specific Vault, and grant the same permissions of the user who generated the API token. Each user can have up to 25 active API tokens.

Only users who have API permission can create tokens. Maximum API token expiry duration is set in Security Policy.

Query ProfilerAuto-on26R1.2

This feature allows Admins and Developers to monitor VQL query performance with the new query profiling tool. Analysing the profile of queries is a key part in monitoring their performance and overall health, but this process has been challenging in the past.

With Query Profiler, the results make it easy to analyze the queries running in Vault by looking at the data obtained during a profiling session. Users must start a profiling session where they are also able to set filters on what kind of VQL queries should be included in the results. These filters include:

Origin: Filters where the VQL query originated from (API, SDK, or ALL).
Targets: Filters the specific Query Targets of the VQL query (for example, restricting to queries on user__sys).
Result Count: Filters queries to only be included if their result count is in a minimum or maximum range.
Query Time: Filters queries to only be included if their execution time is in a minimum or maximum range.
Response Status: Filters whether the query was a SUCCESS, FAILURE or if it received a WARNING.

Learn more about Viewing Admin Logs.

Record Migration Mode InheritanceAuto-on26R1.3

When records are created, updated, or deleted in Record Migration Mode, it can cause Vault to create, update, or delete other records within the same process. Vault treats these related record activities as part of the migration transaction, and thus the related records will inherit many of the same migration mode behaviors. In Object Record Audit History, Vaults displays “in migration mode” in the description for related records which inherited the migration mode.

Record Migration Mode for Delete OperationsAuto-on26R1.3

Vault now supports Record Migration Mode for delete operations and the No Triggers option. This feature allows users to delete migrated records without executing record triggers and Action Triggers. Blocking references will still prevent record delete operations even in migration mode.

This feature is supported for both API and Loader.

Layout Profile: Summary Dialog for Adding & Removing UsersAuto-on26R1.2

When adding or removing users from a Layout Profile, Vault now displays a summary dialog if any users were skipped due to an error. If all users were successfully added or removed, Vault continues to display a success banner instead.

Direct Data API: Additional Document Metadata in Workflow ExtractsAuto-on26R1.2

Workflow Item and Workflow Task Item extracts will include additional document metadata information. The field additions will be captured in the incremental metadata.csv (and correspondingly in the metadata_full.csv).

Workflow Item extract includes additional document fields to maintain the stamped document metadata for expired workflows:

document__sys
document_version__sys

Workflow Task Item extract will include additional document fields to maintain the stamped document metadata for expired workflows:

document_id__sys
verdict_document_major_version_number__sys
verdict_document_minor_version_number__sys
verdict_document_version_id__sys

Notifications: Remove Multiple Email Addresses from Suppression ListAuto-on26R1.3

Admins can now remove multiple email addresses from the Email Suppression List, rather than initiating the action on each individual record.

While this makes the experience more efficient for Admins, it is important to note that removing an email address from the Email Suppression List does not prevent it from returning to the list if there are future email failures for that address.

Learn more About the Email Suppression List.

Document Archive JobAuto-on26R1.3

Admins can now configure jobs that automatically archive documents, supporting use cases where archival of documents should be automated based on document metadata.

When configuring a Date Based Document Operation job, a new Archive action is available:

This option is available on document jobs for Vaults where Document Archiving is enabled.

Learn more about How to Define Document Operation Jobs.

Packages Support for Record Attachments & Attachment FieldsAuto-on26R1.3

Vault configuration migration packages now support exporting and importing record attachments and attachment field files when exporting data.

After adding the Data Step (Dataset), you can edit the Dataset Item to enable Include Object Record Attachments to export record attachments. In the Columns sections of the Dataset Item, you can add attachment fields to include their attachments in the extract.

There is a 10MB per record attachment, and 100MB overall limit when exporting VPK.

Learn more about Using Configuration Migration Packages.

Connection Authorization EnhancementsAuto-on26R1.3

This feature enhances the Connection Authorization workflow, specifically focusing on the input methods for the API Key and Client Secret Auth Types.

API Key Input Field Type and Length: The api_key__sys field is now a Long Text field with a 3600-character limit.
Single Input for API Key and Client Secret: This feature moves to a single-input model. Previously, Admins were forced to repeatedly input these encrypted fields while storing them in Vault.
Updated visibility while providing input: A Vault Admin should be able to temporarily view the inputted value for all encrypted fields before saving. This is true for api_key__sys, client_secret__sys, and password__sys.

Migration Package Validation EnhancementsAuto-on26R1.3

Migration Package Validation improves the reliability of configuration deployments by enforcing SDK code compilation checks and detecting missing sub-component dependencies during the validation phase.

Vault now compiles and validates SDK source code included in a Vault Package (VPK) during the validation step. If the code contains compilation errors, the validation process marks the specific code step with a Blocked status. This prevents the package from being deployed until the code issues are resolved.

Vault now performs enhanced dependency validation checks for missing sub-components. Even if a parent component (for example, an object) exists in the target Vault, the engine verifies that all referenced sub-components (for example, fields) are also present.

Performance & Availability

Bitmask FieldsAuto-on26R1.3

This feature introduces a Bitmask field type for objects, enabling Vault Applications to securely filter records efficiently without performance degradations at high volumes. This new field type will be used primarily for raw objects. Only Veeva can create Bitmask fields which also support a new bitwise operator in VQL for raw object records.

Vault Loader Performance EnhancementsAuto-on26R1.3

Vault Loader jobs now leverage the distributed job framework, which leads to faster load times for Vault datasets.

This behavior means there could be a change in the order in which the datasets are loaded as a later batch (for example, batch 3) may process faster than an earlier batch (for example, batch 1).

Processes leveraging the sequential loading of records via Vault Loader will need to process the batches of 500 records manually.

Minor Enhancements

Preview for Overlay & Signature Page TemplatesAuto-on26R1.3

When editing overlays and signature page templates, Admins can now download a preview before saving their changes. This makes it easier for Admins to iterate on templates without committing those changes until all updates are generated as desired.

Learn more about Managing Overlays and Managing Signature Page Templates.

Enhanced Expand AllAuto-on26R1.3

The Expand all option is now available for users to expand all groups in reports with more than 2,000 records.

Support Workflow & Task Owner in Report Formula FieldsAuto-on26R1.3

When using formula fields on Multi-Pass reports that include Workflow with Document or Workflow with Object report views, users can now use Task Owner and Workflow Owner in formula fields:

This enhancement provides greater flexibility and ensures that report creators can use all workflow fields in formulas.

Learn more about Report Formula Fields.

Support Multi-Object Reference Fields in Document Report FormulasAuto-on26R1.3

In Document reports, multi-object reference fields can now be used in formula fields with the Text() function. This converts the values in that field into a comma-separated list. This provides greater flexibility and reduces user confusion when creating and editing formula fields. Previously, only single-value object reference fields were available for selection in the formula editor.

Learn more about Report Formula Fields.

EDLs: Consistent Hierarchy ViewerAuto-on26R1.3

The EDL Hierarchy Viewer now provides a consistent user experience across Expected Document Lists (EDLs), EDL Items, EDL Templates, and EDL Item Templates. In many cases, a more modern viewer is already in use based on application-specific EDL functionality. This change ensures that the experience is consistent everywhere.

In Clinical Operations Vaults and RIM Vaults, this is applicable to the viewer when working with EDL Templates:

The changes include freezing columns and changes to the coloring.

When working with EDLs and EDL Items directly, there are no changes to the experience in Clinical Operations Vaults and RIM Vaults as these applications have already implemented the more modern viewer (such as the Content Plan Viewer in RIM Vaults).

Learn more about EDL Administration.

Download as PDF: Deduplicated Records in Related Join Object SectionsAuto-on26R1.2

When using the object record Download as PDF functionality, the generated PDF now consolidates duplicate records in the same manner as the Vault user interface.

This functionality applies when duplicate records are associated via simple join relationships or complex join relationships configured to display as simple.

Learn more about Download as PDF and About Object Relationships.

File Count Validation for Record AttachmentsAuto-on26R1.2

Vault now informs users that they cannot drag and drop more than 100 files in a record detail page. Attempts to do so triggers an error and cancels upload for all files.

Add API Name to Document Type Details ObjectAuto-on26R1.2

A new Document Type Name (document_type_name__v) field is added to the Document Type Details (doc_type_detail__v) object. This provides the public API name of the mapped document type, whereas previously only the document type’s label was available in the object record.

Vault AI

Bring Your Own Model: Google Gemini SupportAuto-on26R1.3

Starting in 26R1.3, Admins can configure custom Large Language Model (LLM) connections using Gemini 2.5 Flash and Gemini 2.5 Pro models hosted on Google Cloud. These connections can power custom agents in Vault AI.

To ensure safe Vault AI interactions, this integration fully supports Google Model Armor. Admins can define specific Model Armor templates for both prompt and response screening within Vault AI Settings.

Agent Configuration Enhancements 26R1.3

Vault 26R1.3 introduces several enhancements to agent configuration, providing Admins with greater control over agent accessibility and document context retrieval:

API Access Control for Agent Actions: Admins can now use the new API Access setting to control access via REST APIs.
Viewable Rendition Selection for Document Context: When configuring Document Data and Content or Related Document Data and Content agent context types, Admins can include the Viewable Rendition as part of the agent action’s context.
Document Version Selection in Standard Agent Contexts: Admins now have more precise control over which document version is retrieved when executing an agent action. The Document Version and Source Document Version settings allow agent context configurations to specifically target either the selected document version, or a previous major version of the document.

Learn more about Configuring Custom Agents.

Vault AI MetadataAuto-on26R1.3

Vault AI Metadata is a new configuration layer that provides agents a semantic understanding of a Vault’s data model. Previously, agents reasoned primarily over physical component names, such as product__v and start_date__v, which lack the business context, synonyms, and descriptive detail needed for accurate query generation and natural-language interpretation.

Subject matter experts can now describe the meaning of objects, document types, fields, relationships, metrics, and picklists in business terms through a new set of MDL components: Vsmentity, Vsmfield, Vsmrelationship, Vsmmetric, Vsmpicklist, and Vsmvalue. Active components are automatically synchronized to a vector store and made available to agents.

An Admin can view and manage these component records in the new Vault AI Metadata section in Admin > Configuration > Vault AI Metadata. Customers can configure custom component records in addition to the standard records.

Document Version Compare AgentConfiguration26R1.3

The Document Version Compare Agent is a platform-level agent that helps users quickly grasp key changes between two document versions at a high level, and the overall significance of those changes. By comparing the selected version against the previous major version, it surfaces a concise, high-level summary of what has changed - providing users the context needed to make informed decisions about version updates. Users can execute this agent as a standalone agent via Vault AI Chat or directly from the document viewer when comparing versions.

Veeva Connections

Clinical Operations-EDC Connection

Clinical Operations-EDC Connection: Improved Error Handling for Protocol DeviationsAuto-on26R1.2

The Clinical Operations-EDC Connection now introduces granular error isolation for Protocol Deviations. Previously, a single Protocol Deviation containing an unmapped value could generate a Message Processing Error (MPE), causing the entire batch to fail across studies. Now, If an EDC Protocol Deviation contains a Category or Subcategory value that is not mapped in CTMS, Vault processes all other valid records in the batch successfully. Vault also generates a detailed User Exception Item (UEI) specifically for the affected record, allowing you to quickly identify and resolve mapping gaps.

Learn more about other new Clinical Operations features below.

Clinical Operations-EDC Connection: Restricted Subject Visit CreationAuto-on26R1.2

Previously, Clinical Operations users faced data gaps because Unblinded Subject Visit records in Clinical Operations Vailts were only created in case of discrepancies between the Restricted and the Unrestricted details of the Event in EDC (such as status, SDV, etc.), potentially missing key restricted events.

To resolve this, Vault now automatically creates Unblinded Subject Visit data every time a restricted event occurs in EDC, regardless of data differences.

By simplifying the logic, this feature improves data completeness and increases efficiency reducing the need for manual verification.

Learn more about other new Clinical Operations features below.

Clinical Operations-EDC Connection: Additive SDVAuto-on26R1.3

Clinical Research Associates (CRAs) often perform Source Data Verification (SDV) on additional data points beyond those identified in the Review Plan for a given subject, due to emerging risks, such as site staff attrition or frequent errors.

Previously, there was no automated way to report on this additional effort in Veeva CTMS, requiring manual tracking and leaving Study Managers without visibility into how often these reviews occurred.

To streamline this process, the Clinical Operations-EDC Connection now automatically transfers a summary of Additive Source Data Verification information at the Subject Visit level, specifically indicating whether the review was performed, the latest reason, and the date.

By eliminating the need for manual tracking or double-entry, this solution significantly increases data quality and consistency and operational efficiency for CRAs and ensures proper recognition for monitoring work while providing Study Managers with the transparency needed to easily identify site risks and monitoring trends.

Learn more about other new Clinical Operations features below.

Clinical Operations-Vault CRM Connection

New Clinical Operations-Vault CRM ConnectionConfiguration26R1.3

The new Clinical Operations-Vault CRM Connection bridges the gap between clinical study and commercial teams by automatically sharing Healthcare Professional (HCP) interactions between Veeva Clinical Operations and Vault CRM. This cross-functional transparency ensures a coordinated site experience, improves communication, and eliminates data silos.

The Clinical Operations-Vault CRM Connection includes the following features:

Bi-Directional Data Sharing

Clinical Operations to Vault CRM:

Core study data (Study, Study Countries, and Study Sites) in Veeva Clinical are auto-created in Vault CRM, synchronizing data and eliminating manual entry.
Vault CRM users can monitor high-level study statuses or follow hyperlinks to view study information (such as enrollment details or milestone dates) directly in Veeva Clinical.
When clinical activities, discussions, and attendees are logged in Veeva Clinical by study team members, they automatically flow into Vault CRM as read-only Calls and Discussions. This gives MSLs immediate visibility into clinical interactions.

Vault CRM to Clinical Operations:

When users log interactions or medical discussions in Vault CRM, this data is transferred to Clinical Operations as read-only Medical Activities, Discussions, and Attendees. This ensures study teams can view relevant field communications with their study site staff.

Intelligent Matching

The system uses customer-designated unique identifiers (such as VeevaID or OpenDataID) to accurately match Account records in Vault CRM with Person records in Veeva Clinical. Data flows only when a valid match is identified.

We’ve also included regional country mapping. To prevent spamming of region-specific CRM instances with irrelevant data, the connection uses a country connection mapping framework where interactions are filtered based on the HCP’s primary country.

Multiple CRM Instance Support

Since Vault CRMs are often country or region specific while Veeva Clinical is global, customers can configure and manage concurrent active connections between a single Clinical Operations Vault and multiple Vault CRM instances. Connection details can be easily copied to set up a new connection with another Vault CRM instance, reducing administrative burden.

Error Handling and User Exception Messages (UEMs)

To simplify troubleshooting, the system surfaces UEMs on the integration points in Clinical Operations and Vault CRM when an item fails to process. These UEMs include details specific to the error type, allowing administrators to identify more easily why a record failed. Any records that fail are automatically queued to retry during the next scheduled connection run.

Learn more about other new Clinical Operations features below.

Medical-CRM Connection

Medical-CRM Connection: CLM Content MetricsAuto-on26R1.3

This feature leverages the standard Vault to Vault connection to automatically pull CLM statistics from the CRM-connected Vaults into the source Medical Vault. By bringing this data full circle, Content Managers can view content performance directly alongside the medical content.

Learn more about other new Medical features below.

Medical-CRM Connection: Approved EmailConfiguration26R1.3

This feature automates the flow of Approved Email content from Medical Vaults to Vault CRM over a near real-time Vault to Vault connection. By utilizing Vault CRM’s document model, organizations can seamlessly synchronize Email Templates, Email Fragments, Template Fragments, and all supporting assets with their associated renditions and relationships left intact.

This feature removes the version lag and administrative overhead associated with legacy synchronization processes, ensuring that field teams always have immediate, compliant access to the latest materials for HCP engagement.

Learn more about other new Medical features below.

Medical-CRM Connection: Document TransferConfiguration26R1.3

This feature introduces the automated transfer of documents from Vault Medical to Vault CRM over the standard Vault to Vault connection. When a document in the Medical Vault is created or modified, the Document Transfer integration automatically creates or updates a corresponding CrossLink document in the connected Vault CRM. This near real-time integration ensures that Vault CRM always maintains immediate, seamless access to up-to-date, compliant content.

By replacing manual file management with an automated handoff, this feature significantly reduces administrative overhead and eliminates the risk of version lag for your field teams. It streamlines content management by automatically syncing your critical reference documents, templates, and medical content across platforms.

Learn more about other new Medical features below.

Medical-CRM Connection: Populate Inquiry's Preferred Contact Information on CaseConfiguration26R1.3

The Medical-CRM connection now automatically populates a new Preferred Contact Information field on Medical Vault Cases with the specific Person Information record mapped from the corresponding Vault CRM Medical Inquiry.

This integration eliminates manual guesswork, ensuring that Medical Information agents instantly know exactly which communication method to use for fulfillment even when a contact has multiple addresses or emails associated with it.

Learn more about other new Medical features below.

PromoMats-CRM Connection

PromoMats-CRM Connection: CLM Content MetricsAuto-on26R1.3

This feature leverages the standard Vault to Vault connection to automatically pull CLM statistics from the CRM-connected Vaults into the source PromoMats Vault. By bringing this data full circle, Content Managers and Marketers can view content performance directly alongside the creative assets.

Learn more about other new Commercial features below.

PromoMats-CRM Connection: Approved EmailConfiguration26R1.3

This feature automates the flow of Approved Email content from PromoMats Vaults to Vault CRM over a near real-time Vault to Vault connection. By utilizing Vault CRM’s document model, organizations can seamlessly synchronize Email Templates, Email Fragments, Template Fragments, and all supporting assets with their associated renditions and relationships left intact.

Learn more about other new Commercial features below.

PromoMats-CRM Connection: Document TransferConfiguration26R1.3

This feature introduces the automated transfer of documents from PromoMats Vault to Vault CRM over the standard Vault to Vault connection. When a document in a PromoMats Vault is created or modified, the Document Transfer integration automatically creates or updates a corresponding CrossLink document in the connected Vault CRM. This near real-time integration ensures that Vault CRM always maintains immediate, seamless access to up-to-date, compliant content.

Learn more about other new Commercial features below.

Safety-EDC Connection

Safety-EDC Connection: Retain Primary Designation for Multi-Event CasesAuto-on26R1.2

Within the Safety-EDC Connection, the Safety Case Follow-Ups Honor Safety Decision feature is critical for reducing noise and sharing and tracking Safety decisions. However, Veeva EDC relies on a primary event to define its top-level structure, while Safety maintains a case-centric view. Previously, adding a new Adverse Event (AE) during a merge or follow-up triggered a change to the primary event. This automation often overrode the deliberate decisions of medical reviewers and caused EDC to inadvertently drop events in follow-up transmissions.

With this release, the Safety-EDC Connection introduces more stable logic for EDC-sourced Cases to ensure that primary event designations remain unchanged unless manually adjusted. By preventing automatic primary event updates, the connection maintains higher data integrity and respects the decisions of case processors.

Key updates include:

Stable Merges: When merging an Inbox Item containing a new AE into an existing Case using the Merge to Current action, the new AE is no longer automatically set to primary. Instead, the Rank value is left blank.
Consistent Follow-ups: When creating a new Case version using the Create Follow-up action, net-new AEs default to a non-primary status. This ensures the preservation of the existing case structure across versions.
Explicit Safety Decisions: For both merge and follow-up actions, the resulting Safety decisions explicitly include an “add” decision for the new event to inform EDC of the update without disrupting the primary event hierarchy.
Rank Requirement Cleanup: To eliminate data assumptions, any time an AE is received and not designated as primary (Rank value of 1), the Rank field remains blank.