About the 24R3 Release
Pre-Release Date: November 11, 2024 | CDB Pre-Release Date: November 18, 2024 | Release Date: November 22 & December 6, 2024This page can help you understand the schedule for the coming release and the list of features included. Dates are subject to change.
Important Dates
24R3 Pre-Release Begins
- Pre-release vaults available: Your Veeva Project Manager will contact you with login credentials.
- Validation documents available:
- Validation Project Plan
- IOQ Protocol
- Business Requirements Documents
- Validation Impact Assessment
24R3 Pre-release for CDB Begins
Pre-release environments available for Vault CDB. Contact your Veeva Project Manager for details.
24R3 Release, Part A
- 24R3 released to pre-release (VV1-37) and limited release (VV1-17) vaults
24R3 Release, Part B
- 24R3 released to all general release vaults.
- Updated training available on Veeva Learning
24R3 Pre-Release Ends
We recommend that you no longer use your 24R3 pre-release vaults after this date. Even though your pre-release vault is still active, we advise waiting for the next pre-release period (24R3) to begin. Contact your Veeva Project Manager for details.
Feature Information
- What’s New in 24R3 (Updated November 14) provides detailed explanations of each feature.
- 24R3 Feature Enablement Details (Updated November 14) includes information on how new features are enabled.
Pre-Release Information
- Pre-Release FAQ answers common questions about “pre-release”.
- Known Issues in 24R3 Pre-Release (Updated November 18) lists known issues in the 24R3 pre-release. This page also lists the release notes for any maintenance releases applied to pre-release.
Release Information
- 24R3 Release Impact Assessment (Updated November 15) analyzes the impact of new features.
- 24R3 Migration Vault Release Impact Assessment (Published October 14) analyzes the impact of new features.
- 24R3 Supplemental Vault Release Impact Assessment (Updated November 14) lists Vault Platform features in the 24R3 release that can impact CDMS vaults.
- 24R3 Fixed Issues (Available November 22) documents issues that affected previous versions or pre-release and are fixed in 24R3.
- 24R3 Known Issues (Available November 22) documents issues introduced in 24R3 which are not yet fixed.
- 24R3 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 24R3, see the Vault Release Notes .
Notifications Opt-In
As a valued member of our community, providing you with control over the communications you receive from Veeva is important to us. Please allow us to send you pre-release environment notifications and other industry related information. Contact your vault’s administrator to verify that the Product Announcements checkbox is selected for your user profile.
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.
Announcements
RIA Format Update
Beginning with 24R3, the Release Impact Assessment (RIA) for EDC and CDB will be available in Excel™ format only. Previously, the document was provided in both Excel™ and PDF formats.
This change is consistent with other Vault RIAs, and provides us with greater flexibility in the spreadsheet format of the document that is exclusively used by the vast majority of users of the system.
Vault Domain Move Support
In this release, we’ve made updates to Vault EDC to support domain reparenting, which include:
- The ability to move DEV, TST, and PROD vaults from one domain to another
- Support for moving users from one domain to another through automating the creation of new users accounts (referencing the new domain) and locking/inactivating old accounts (referencing the previous domain).
- Ability to reassociate Vault functional records to the new user reference, including Enrollment Completion, Learning System users, Role associations, and Email group assignments. Other user references are left untouched by the process.
- CDMS Vaults can be moved to a different Vault domain to support various business needs such as Organizational rename or rebranding, business acquisitions, vendor or partnership changes, and others.
Contact your Veeva Services representative to ask about reparenting.
25R1: CDB Pre-Release Extension
With the 25R1 release, we will extend CDB pre-release to four weeks from the current three. This extension will align the pre-release timing with Vault CDMS.
25R1: Retirement of CDB SDTM Export Type
With the 25R1 release, we will retire the SDTM export type in CDB. Please refrain from creating any new exports in CDB Workbench or Clinical Reporting with the SDTM type.
25R1: Prevent Users from Editing Export Definition Listing CQL
In the 25R1 release, CDB will prevent users from modifying the Export Listing CQL directly in the Export Definition to prevent errors when reconciling listings upstream. Going forward, users will need to make any modifications to the parent listing before including them in the Export Definition.
25R1: Review Information in CDB Exports
With the 25R1 release, CDB Export Definitions that include Review Listings will include new columns that contain the review data associated with the Review Listing. This change will impact both new and existing Export Definitions.
25R1: Planned Data Infrastructure Upgrade
With the 25R1 release, CDB will be upgrading some of its data infrastructure.
With this upgrade, the following behavior changes will apply:
- We will no longer allow the comparison of a string value to a date or datetime without converting the string to a date or datetime.
- Casting a number as decimal will require passing an additional argument for precision. Not doing so will result in a loss of decimal precision.
- We will no longer automatically strip trailing or leading spaces found in string literals.
- If a string that includes timezone offset is passed to the
date_format
function, then timezone conversion will be honored.