New Features in 26R2 Limited Releases
26R2 Planned General Availability: July 31 & August 7, 2026
26R1.4 Release Date: June 26, 2026
26R1.3 Release Date: June 12, 2026
26R1.2 Release Date: May 1, 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.
Enablement Changes: The enablement of each feature is subject to change from release to release. For limited releases in the same general release, we will update this page. Enablement may also change before the general release. Refer to the Release Impact Assessment for the most up to date enablement for a general release.
Data Entry
Features in this section are changes to the Data Entry tab, a working area for investigators and clinical research coordinators to enter study execution data.
Error When Event Doesn't Have a Change Reason 26R1.2
Use Case
Updates to the user interface (UI) now provide an error message and ensure that a reason for change is always captured. A reason for change could potentially have not been captured when simultaneous users were entering the same event data, and the user’s page was not refreshed following the other user’s data entry or when one user had multiple tabs open and was revising the same event data in both tabs.
Description
Users will encounter an error if they attempt to change an Event Date or Visit Method that was previously empty in their view but already contains data in the system from another tab or user. Vault will display an appropriate message, depending if the study is configured to use Visit Method:
- “An event date has already been entered. Please refresh the page and try again.”
- “An event date and visit method have already been entered. Please refresh the page and try again.”
To resolve the validation error, the user must refresh the page to view the current data before attempting further modifications.
Enablement & Configuration
This feature is automatically available.
Remove Editable Grid Validation for Range Checks 26R1.2
Use Case
Previously, when entering data into a grid, users encountered a different experience than they did on standard forms. If a value was entered that fell outside of a pre-defined range, the grid would display a warning message that appeared to prevent the form from auto-saving or being submitted.
Description
We have updated the behavior of editable grids to ensure that range checks on number items and units are handled consistently across the platform.
When a user enters a value into a grid that is outside the configured minimum or maximum range, the system will no longer display an immediate validation warning under the field. Instead, the data will auto-save as normal, and the system will automatically open a query to flag the out-of-range value.
Prior to 26R2
After 26R2
Enablement & Configuration
This feature is automatically enabled.
Data Review
Features in this section are changes to the Review tab, a working area for clinical research associates and data managers, or to review functionality within the Data Entry tab.
Prevent Changing the Query Team When Editing a Query 26R1.2
Use Case
To improve consistency and data integrity, users with multiple roles can no longer change a query’s assigned team after the query has been created. Previously, this setting was editable in some cases when Quick Queries were not in use.
Description
Veeva EDC now restricts multi-role users from editing the Query Team field once a query is active. While users can still select a team when first opening a query, they are no longer permitted to switch teams while editing the query message.
When editing an existing query, the system hides the Query Team dropdown menu to prevent changes and displays the assigned query team as a read-only badge for reference.
Prior to 26R2
After 26R2
If a query was originally assigned to the wrong team, the user should close that query and open a new one with the correct query team selected.
Enablement & Configuration
The update is automatically applied in studies where the Quick Queries feature is not currently in use.
Rename Snapshots to Bulk Lock & Freeze 26R1.2
Use Case
Vault EDC now uses intuitive “Bulk Lock & Freeze” terminology to make the UI more consistent with the tool’s core functionality of managing data status changes through bulk actions. This update replaces the “Snapshots” labels throughout the application with “Bulk Lock & Freeze” or “Filter” wording. By standardizing labels across menus, buttons, and confirmation dialogs, the system provides a more cohesive experience.
Description
“Snapshot” labels seen within EDC are updated to “Bulk Lock & Freeze” to improve functional clarity. The update impacts labels seen within the Review tab, Role permissions, Email notifications, and Bulk Operation reports.
- The “Snapshots” subtab in the Review menu is renamed to “Bulk Lock & Freeze,” and the “+ New Snapshot” button is now “+ New Filter”.
- When defining a filter, the labels are updated as seen in the definitions and Ready States.
- Confirmation dialogs for deleting, saving, or refreshing results now use “filter” instead of “snapshot”. Error messages for concurrent jobs or limited site access are updated for consistency, including the following:
- This will run a job to evaluate the filter [FILTER_NAME]. Do you wish to continue?
- Unable to perform this action because the Refresh Results job is running for this filter
- Role permissions in System Tools are relabeled from “Manage Snapshots” and “View Snapshots” to “Manage Bulk Lock & Freeze” and “View Bulk Lock & Freeze”.
- Automated emails for Refresh Results and Bulk Operation jobs now reference the “filter” name.
- E.g., Your Refresh Results job for the filter [Filter Name] has finished processing, and the results can be viewed in the application.
- The Bulk Operation Report now uses “Filter Details” and “Filter Results Summary” for the sheet labels.
- EDC Tools - Job names are updated to reflect “View Bulk Lock & Freeze”
- Help documentation and the help page URLs are updated to “bulk-lock-freeze”.
Enablement & Configuration
This feature is automatically available for use.
Increase Number of Columns in View Summary Grid 26R1.2
Use Case
In 25R3, the View Summary grid was limited to displaying only 16 columns. This meant that for longer repeating forms, such as Adverse Events or Concomitant Medications, review users couldn’t see all their data in a single view. This update allows review users to see all items on a repeating form directly within the system, eliminating the need to export data or view it form-by-form.
Description
The View Summary table has been updated to increase the number of columns, supporting viewing of up to 75 items on a single form.
Any repeating item groups that exist on the repeating form are automatically expanded, with all items shown as columns. A grid icon displays on the item label in the column which displays the message “This is a repeating item group.” on hover-over.
Enablement & Configuration
This feature is automatically available.
Assessments
The following are new features for the Assessments area of Veeva EDC.
Assessments Support File Attachments 26R1.2
Use Case
Assessors can complete records more efficiently by accessing and downloading file attachments directly within the Assessments tab. Reviewing file attachments along with other assessment data in a single location maintains continuity in the assessment workflow and ensures supporting study data is available when completing assessments.
Description
The Assessments UI now supports file attachments, allowing study builders to configure file attachment items as visible fields within Assessments. When configured, these items appear in the assessment supplemental data section as non-clickable text showing the de-identified file name, rather than a direct link. To access the file, a new action menu (three-dot icon) is available next to each file item, containing an option to download the file.
The de-identified file name and extension will be seen within the assessment. For study designs which have the file attachment item included in the reassessment configurations, a Site user replacing or deleting an existing file attachment in Data Entry will trigger a reassessment. If a file attachment is removed from the form, the de-identified file name in the obsolete assessment snapshot shows a hover message stating “File does not exist” and the download option is disabled.
Enablement & Configuration
This feature is automatically available for configuration in Studio.
Study Design & Configuration
Features in this area apply to Studio, the study design and configuration area for Veeva EDC.
Studio: Restore Dynamic Definitions 26R1.2
Use Case
Study Designers can now re-add accidentally removed dynamic designs, such as dynamic Forms or Events back to the study design in Studio without receiving an error and having to contact Veeva Support. Study Designers can also restore previously deployed dynamic definitions across casebook versions, eliminating delays and ensuring design continuity.
Description
Studio now allows designers to re-add deleted dynamic definitions for dynamic Forms, Events and Event Groups. The system automatically retrieves and applies the previous dynamic property settings when recreating the relationships between study objects. Users can restore relationships via the drag and drop editor or the Schedule view.
For example, if a user accidentally deletes a dynamic Form from an Event in Casebook version 2 that was deployed in version 1, adding that Form back now automatically restores its dynamic property from version 1 instead of triggering a system error.
Enablement & Configuration
Automatically available in Studio.
Direct Form URL in Email Notifications from Send Email Rules 26R1.2
Use Case
Form links in Send Email rules allow recipients to navigate directly from the email to a specific record within the participant’s casebook. By including form links within the email messages recipients no longer need to manually navigate to the record in EDC. They can quickly and easily access the exact data which is referenced in the email. This helps reduce navigation time in EDC and facilitates faster reviews of the clinical data.
Description
Study designers can include a new token, ${Custom.@Form.url_v}, within the Email Message field of Send Email rule actions. The token provides a direct link to the specific form instance for the data received in the email. The new static token is available in the rule editor picklist.
Upon clicking the link from the email, the system automatically directs the user to either the Review or Data Entry tab based on their permissions. If a user has access to both, the system defaults to the Review tab. If the email recipient doesn’t have access to either of these tabs, or if the link is to a restricted form where they don’t have permissions, Vault opens a “Page Not Found” screen. will be directed to a “Page Not Found” screen.
Enablement & Configuration
This feature is automatically available in Studio.
Item ILB Rule Identifier 26R1.2
Use Case
Study designers can now reference specific Intentionally Left Blank Reasons (ILB) directly within rule expressions. By evaluating ILB reasons via logic, EDC can automatically open queries or log protocol deviations, ensuring higher data quality and protocol compliance.
Description
The* intentionally_left_blank_reason_v attribute is now available via the auto-complete dropdown in the Rule Editor when referencing an item object. Rule expressions can now include this attribute to return the specific reason an item or item group was marked blank, such as “Not Done” or “Did Not Occur”. The ILB Reason attribute can be used with aggregates and form or item links. Rule identifiers can also include intentionally_left_blank_reason_v for lab analytes to return the Reason for Missing Result.
Enablement & Configuration
This attribute is available for use in rule expressions in Studio.
Study Administration
Features in this section apply to System Tools or EDC Tools, a study-level administration area for Veeva EDC.
SDE–SAS Logging Improvement 26R1.2
Use Case
Previously, when a Study Data Extract failed because of a minor data entry issue—such as a date with an invalid year—the job log would simply report a generic failure rather than identify the exact SAS error. This lack of detail meant clinical data managers and programmers often had to request technical assistance to identify the specific field or value causing the SAS error. This update provides immediate, specific feedback directly in the job log, allowing you to triage and correct data issues yourself. By identifying exactly which record is preventing the export, you can resolve the problem and re-run your extracts much faster.
Description
Veeva EDC now automatically identifies common data-related errors that cause SAS export failures and translates them into easy-to-read messages in your job log. Instead of seeing a broad translation error, the log will now list the specific item and the exact value that SAS could not process.
For example, if a field contains a date that the system cannot interpret, your log will display a message such as “Item (LBDTC) contains illegal data: (1000-12-10).”
To ensure logs remain easy to navigate, the system will display up to 50 individual errors. If an export contains more than 50 errors, a warning appears stating that the list has been truncated, so you can fix the first batch before reviewing others.
FTP UI Validation Enhancements 26R1.2
Use Case
When configuring FTP connections for clinical studies, even a small typo in a hostname or username can lead to failed data deliveries. This feature introduces validation directly into the setup screens to catch common errors as they happen. Preventing incorrect configurations — such as using the wrong delivery method for external destinations — can save time for administrators and ensure that study data flows to the correct locations without interruption.
Description
This feature enhances the user interface for FTP connections in both EDC and System Tools by adding validation checks and more detailed reporting as detailed below.
- Hostname Validation: If you select “Veeva Vault” as your delivery method for Clinical Database (CDB) connections, the system will verify that the hostname belongs to a Veeva domain. If an external hostname is detected, you will receive a prompt to use standard FTP or FTPS methods instead.
- Protected Directories: To prevent conflicts with internal system folders, the system will now prevent users from using the “/workbench” directory in the destination path for non-CDB connections.
- Username Formatting: For Vault connections, the interface now validates that usernames follow the required
+ pattern.
Additionally, the FTP Configuration Report has been upgraded to help with troubleshooting. It now includes columns for Username and Destination Path and tracks the last modified details more accurately by capturing changes to the specific connection settings, such as port or path updates.
Enablement & Configuration
This feature is automatically available.
Labs
Features in this section are new features for the Labs module of Veeva EDC.
Max Analytes per Lab Form/Panel Updated to 35 26R1.2
Use Case
Prior to this release, the default maximum number of analytes in a lab form and/or lab panel was limited to 25, which often required customers to submit ad hoc requests for manual increases. This update removes unnecessary hurdles and ensures sufficient capacity is available by default by increasing and standardizing this limit to 35.
Description
This update increases the default value for Max Number of Analytes in Lab Forms and/or Lab Panels from 25 to 35.
Enablement & Configuration
This feature is automatically available.
Connections & Integrations
Features in this section are new connections or integrations with Veeva Clinical Data or enhancements to existing ones.
Clinical Operations-EDC Connection: Restricted Subject Visit Data Synchronization 26R1.2
Use Case
Restricted data transfer via the Clinical Operations-EDC Connection ensures consistent visibility into unblinded subject visit data in CTMS. By standardizing the creation of Unblinded Subject Visit Data records, CTMS users now gain immediate clarity on the presence of restricted information in an EDC event independent of the presence of unrestricted data in the same visit. This provides a reliable and predictable indicator for unblinded event data.
Description
When an event in EDC contains restricted data, the Clinical Operations-EDC Connection now always creates an Unblinded Subject Visit Data record on the Subject Visit in CTMS, regardless of the presence of unrestricted data.
This new Clinical Operations - EDC Connection functionality does not change EDC behavior. Testing requires an integrated environment with Veeva CTMS Vaults that have restricted data transfer enabled.
Enablement & Configuration
This feature is automatically enabled for studies using the Clinical Operations-EDC Connection.
EDC Migrator
Features in this section are new features for Veeva EDC Migrator.
Allow the Capture of V&S Errors and Warnings Exceeding 32k Characters 26R1.2
Use Case
During the early stages or first few rounds of a new study migration, migration attempts often encounter numerous validation errors, such as data values exceeding the character limits defined in the study design. Previously, a 32,000-character limit on log files meant that not all errors were captured in a single run. This forced users into a repetitive cycle, fixing a batch of errors and re-running the migration, only to discover a new set of the same error types that had been truncated in the initial report. By expanding log capacity, this feature significantly reduces the number of iterations needed to clean source data, shortening the overall troubleshooting timeline and making the initial Validate & Stage phase much more efficient.
Description
This enhancement improves how the Migrator tool handles error and warning messages during the Validate & Stage process.
Previously, during migration execution, the system validated data against the study design and stored only the first 1,000 activities (errors or warnings) in memory. These were then written to the status object and truncated at a 32,000-character limit, which could result in incomplete reporting.
With this update, the system now manages error and warning activities in sections. When memory limits are reached, activities are written incrementally to file sections and later merged. This approach ensures that all unique errors and warnings are captured without duplication, enabling the generation of complete and accurate log outputs.
Enablement & Configuration
This feature is automatically enabled.