About the 26R2 Release

This page can help you understand the schedule for the coming release and the list of features included. Dates are subject to change.

Release Waves

For the general release, Wave 1 and Wave 2 releases occur 1-2 weeks apart (2 weeks for the R3 release). We release the 26R2 to the Wave 1 general release POD (VLT-1216) during the Wave 1 general release (July 31). We release the 26R2 to the Wave 2 general release PODs during the Wave 2 general release (August 7).

Admin users can confirm which POD their vaults are on from Admin > Settings > General Settings.

If you have further questions about the Wave 1 and Wave 2 process, contact your Veeva Services representative.

Feature Information

• What’s New in 26R2 (Published July 2) provides detailed explanations of each feature.
• 26R2 Feature Enablement Details (Published July 2) includes information on how new features are enabled.

Pre-Release Information

• Pre-Release FAQ answers common questions about “pre-release”.
• Known Issues in 26R2 Pre-Release (Published July 2) lists known issues in the 26R2 pre-release. This page also lists the release notes for any maintenance releases applied to pre-release.

Release Information

• 26R2 Release Impact Assessment (Updated June 30) analyzes the impact of new features. New versions will be published on Tuesdays and Thursdays if changes to the previous version have occurred.
• 26R2 Migration Vault Release Impact Assessment (Published June 15) analyzes the impact of new features.
• 26R2 Supplemental Vault Release Impact Assessment (Published June 19) lists Vault Platform features in the 26R2 release that can impact EDC or DQS (formerly CDB) customers.
• 26R2 Fixed Issues (Available July 31) documents issues that affected previous versions or pre-release and are fixed in 26R2.
• 26R2 Known Issues (Available July 31) documents issues introduced in 26R2 which are not yet fixed.
• 26R2 Maintenance Releases (Available with first maintenance release) documents fixes for issues that are affecting customers in production environments.

For details about new features in the Vault Platform in 26R2, see the Vault Release Notes .

Announcements

RIA Enablement & Configuration Field Updates

The Enablement field options have been updated and a separate Configuration column has been added to the 26R2 Clinical Data Release Impact Assessment (RIA). The Enablement field will have one of the following four values: Auto-on, Available for Use, Phased Release, and Early Adopter. The Configuration column indicates where configuration for the feature occurs (Studio, EDC Tools, etc.) if configuration is required. We’ve also added links to the About the Release page, What’s New in 26R2 page, and Vault Platform release notes on the RIA title and info page.

Veeva CDB Rebranding to Veeva DQS

With the 26R2 release, Veeva CDB is rebranding to Veeva DQS.

The growing complexity of clinical trials requires a dedicated system to manage data quality. Since its creation, Veeva CDB has evolved significantly, now delivering a new category of capabilities built specifically to help data managers ensure complete, accurate, and reliable trial data. This category is a Data Quality System. The name Veeva DQS reflects what the product has become and where it is heading.

The application functionality, user workflows, and the upcoming product roadmap remain the same.

Customers who want to suppress this change for a release cycle can contact their services manager for assistance.

Prospective Review Plan Assignment Backfill

The 26R2 feature Prospective Review Plan Assignment requires the preparation of system data in order for the feature to be available for existing studies. This preparation will occur during the weekend of the 26R2 release. During this time, actions that have the potential to assign review plans to multiple subjects at a time will be disabled. The following actions will be affected: the Reevaluate Plan Assignment Job button on the Review Plan Assignment Criteria page and the Assign Review Plans button on the Review Plan Manual Assignment page, both of which are located in EDC Tools. While these actions are disabled, assignment criteria will continue to automatically assign review plans to subjects and users can still manually assign review plans for one subject at a time. All actions will be re-enabled when the system data preparation is complete.

EDC API Changes for Audit 2.0

The introduction of the Live Capture Audit 2.0 feature brings important changes to the EDC API’s error handling structure.

Previously, many bulk endpoints followed an “all or nothing” or batched failure model. When EDC Audit 2.0 Live Capture is active, affected endpoints will transition to a Partial Success & Failure model. Under this new behavior, data processing is managed at the subject level. If all records associated with a specific subject are processed successfully, the system will commit those records to the database. Conversely, if a processing error occurs for any single record within a subject, the system will roll back all records for that specific subject, while allowing other successful subjects in the bulk request to persist.

Because of this shift, integrations can no longer rely solely on a top-level HTTP response status. API responses will now require a more granular approach to parsing individual entry statuses to avoid blindly retrying and re-executing already-persisted data.

To ensure your integrations continue to run smoothly, please review the Best Practices for Audit 2.0 Live Capture section in our API documentation for complete details on which endpoints are affected and how to update your retry logic.

Retirement of the Data Export Job

As part of the 26R2 release, the Data Export Job will be retired from both EDC Tools and the Review UI and will no longer be able to be run or scheduled.

Full Rollout of Centralized PI Management and Just in Time VeevaID User Management

As part of the 26R2 release, the Person_SYS object will be automatically enabled for all remaining Vaults, completing the phased rollout that began in 26R1. This update supports both Just In Time VeevaID Registration and Centralized Principal Investigator Management.

If you would like to enable these features ahead of the 26R2 release, please reach out to your Services contact to discuss early activation.

For complete details on these features, please review the 26R1 Release Notes for Just in Time VeevaID Registration and Centralized Principal Investigator Management.

User Import Updates to Support Restricted Data Changes

Starting in 27R1, restricted data access will no longer be managed at the role level. Instead, it will be managed at the individual user level. This means that the Restricted Data Access permission will be removed and a user’s role will no longer determine their restricted data access in a study.

To support this change, the user CSV import will include a new column that will be used to grant a user restricted data access. In order to avoid disrupting existing customer integrations for creating and updating users, this column will be optional upon initial release.

If the new column is not included, the import will set the user’s restricted data access setting based on the user’s role. This action can only be done for roles created prior to 27R1, as the permission will not be available for new roles created after the fact. This behavior will be supported up until 27R3, at which time the new column for granting restricted data access will be required.

The intent of this announcement is to provide customers with ample time to plan for these changes and update their integrations. There are no changes to restricted data access being released in 26R2.

Note that release timelines are subject to change.

Process Update for Destructive Study Amendment Changes

After a few years of providing reviews of destructive deployment changes, it is clear that customers have a good handle on this process. To help users complete amendments more quickly, we are moving to an opt-in model for amendment reviews. Beginning with the 26R2 release, Veeva will no longer require customers to obtain Veeva review and approval before deploying destructive study amendments. This update removes the vault-level block, giving teams greater flexibility and full control over deployment schedules.

To protect against unintended destructive changes, Vault Owners can continue to manage these controls via the study-level setting in Admin.

• Recommended Practice: Keep the Disable Retro Amendment errors setting set to False to maintain standard protections.
• Deploying Changes: Vault Owners can toggle this setting to True to complete a deployment after the team has verified the impact of the changes. We recommend returning the setting to False after deployment.

If your team prefers additional review to verify planned destructive changes before deployment, the Veeva CDMS Services team is available to assist. This review can now be requested as an optional managed service by contacting your Services consultant.

Veeva Connect Communities

Release-related updates will be posted to Veeva Connect, a central hub for product information and a place to ask questions and share knowledge about Veeva products. Product information provided on Veeva Connect includes general release communications, release highlights, and key feature demos.

The links in the list of Vault product communities below will take you to the community and automatically add you to it. If you are not already a member of Veeva Connect, you can register using your company email address. Once registered, in addition to browsing the communities relevant to your role below, click Releases at the top-right of Veeva Connect to view all release-related content.

• Veeva Clinical Data: EDC & Coder
• Veeva CDB