26R1 Feature Enablement Details
Pre-Release Dates: March 16 & 23, 2026 | Release Dates: April 10 & 17, 2026The following is a list of new features introduced in 26R1. For each feature, the list includes information on how enablement works and which applications include the feature. You can see detailed explanations for the features below in What's New in 26R1. See an explanation of feature enablement and user impact below. Note that unless otherwise specified, the enablement settings provided apply to existing vaults and studies. Any studies created after the 26R1 may have different enablement settings. See What's New in 26R1 for more detailed enablement information.
Feature Enablement Summary
| Feature Name | Configuration | Dependencies | Day 1 Impact to Primary Users | Users with Day 1 Visibility |
|---|---|---|---|---|
| Assessments | ||||
| Medical Assessments Grid Updates |
|
|||
| CDMS | ||||
| File Attachments | ||||
| New Stable URLs for EDC Application Tabs | ||||
| Clinical Coding | ||||
| Form to Form Link Visibility in Coder |
|
|
||
| WHODrug B3/C3 Field Label Updates |
|
|
||
| Display Freeze & Lock States in Coder for Queries |
|
|
||
| Improved JDrug Autocoding for Deleted Codes |
|
|
||
| Improved Tracking of Edited Coder Query Messages in Audit Trail |
|
|
||
| Coding Administration | ||||
| Update Coding System Label to Veeva Coder |
|
|
||
| EDC Clinical Reporting | ||||
| SFF Enhancements for Clinical Reporting Studies | ||||
| Support JDrug Coding Dictionary in Clinical Reporting |
|
|||
| Listing Data Grid Improvements in Clinical Reporting |
|
|||
| Incremental Import Updates for Clinical Reporting Lab Labels |
|
|||
| Add Job ID to Manifest and Export Log |
|
|||
| Clinical Reporting User Session Management |
|
|||
| Imaging: Asynchronous Individual Exam Download | Imaging |
|
||
| Imaging: Update DICOM De-identification Profile |
|
|||
| Labs | ||||
| Modifier Support for Lower/Upper Age Values in Normal Ranges |
|
|
||
| Remove Automatic Addition of Trailing Zeroes to Lower & Upper Normal Range Values | ||||
| Study Design & Configuration | ||||
| Studio Casebook Version Update |
|
|
||
| Studio: Copy Lab & Imaging Forms Across Vaults | Both the source and destination studies must have the Lab/Imaging setting enabled in order to copy successfully and to display in the forms listed in the Form Copy. For Lab forms, the analyte, global codelist, and units must exist in the destination study to copy the form successfully. For Imaging, the global codelist for modality must exist in the destination study to copy the form successfully. |
|
|
|
| Studio: Validate Any Design Changes | Development environment(s) - Control Center |
|
|
|
| Subject ID Generation Settings Included with Study Copy | New studies |
|
|
|
| Studio Copy Log: New Summary Tab & Log Messages | New Studio copies |
|
|
|
| Form Names & Schedule Driven Defaults Appendix Options in Studio PDFs |
|
|
||
| Display Item's Previous Submit Value in Email Messages |
|
|||
| Increased Length for Studio Help Content | ||||
| Enforce Reciprocal for Expression Engine v2 Rules |
|
|||
| Enforce Valid Derived Item Configurations |
|
|||
| Studio Rules: Enforce Explicit Blank Handling |
|
|||
| Rule Emails Should Display in Study Language & Locale |
|
|||
| Studio: Core Data Definition Validations |
|
|||
| Role Management & Security | ||||
| New Query Teams |
|
|||
| "Manage Safety Configuration" Permission Moved to "Study Design" Section |
|
|||
| Integrations | ||||
| Clinical Operations - EDC Connection: Protocol Deviation Management for Connected Studies in CTMS Only |
|
|
||
| Clinical Operations-EDC Connection: Partial SDV and DMR Reflects as In Progress in CTMS |
|
|||
| Clinical Operations-EDC Connection: EDC Study Country Name Preserved for Connected Studies |
|
|||
| Clinical Operations-EDC Connection: Aggregated User Exception Messages by Study Countries and Study Sites for Identical Issues |
|
|||
| Safety-EDC Connection: Connection Configuration Available for Every EDC Vault |
|
|||
| Safety-EDC Connection: New Study Drug Management and Identification from Item Value |
|
|||
| Safety Integrations: Follow-Up Scan Job Independent of Scheduling User |
|
|||
| Safety-EDC Connection: New Standard Safety Fields and Adjusted Configuration Restrictions |
|
|||
| Safety Integrations: Reporter Details with New Source, Email & Phone | Person_sys for Just-in-Time VeevaID Registration and Enhanced User Management |
|
||
| Review Listing Item Value Change Detection |
|
|||
| Listing Access | CDB |
|
||
| Import Error & Warning Code Aggregation |
|
|||
| Manifest Builder Updates |
|
|||
| New Third-Party Data Type Validations |
|
|||
| Import Audit Updates |
|
|||
| Unblinding Rules Deployment |
|
|||
| Third Party Data Import Notification When Pending Approval |
|
|||
| Support JDrug Coding Dictionary in CDB |
|
|||
| CDB Grid Improvements |
|
|||
| Filter Menu Redesign for Listings |
|
|||
| My Observations Assignments Filter in Review Listings |
|
|||
| Additional Clean Patient Tracker Columns |
|
|||
| Filter Menu Redesign for Clinical Reporting Listings |
|
|||
| Update Review Listing Timing Thresholds |
|
|||
| Listing Data Grid Improvements |
|
|||
| Study File Format API Enhancements | ||||
| Incremental Import Updates for Clinical Reporting Lab Labels |
|
|||
| Add Job ID to Manifest and Export Log |
|
|||
| Reprocess Third Party Data on Subject Not Found Warning |
|
|||
| Data Type Based Third Party Data Masking |
|
|||
| CDB User Session Management |
|
|||
| Data Review | ||||
| Snapshots UI/UX Consistency and Label Updates |
|
|
||
| Protocol Deviation Names in a Report Open the Review Tab |
|
|||
| Data Entry | ||||
| Improved Event Groups Marked for Removal | ||||
| Two Step Event Reset | Data Model 2 |
|
|
|
| Updated Form Reset and Form ILB Dialogs | ||||
| Randomization | ||||
| Disable EDC Randomization for New Studies | New studies only |
|
|
|
| Study Administration | ||||
| Person__sys for Just-in-Time VeevaID Registration & Enhanced User Management |
|
|||
| Event-Based Review Plans |
|
|
||
| Test Data Verification Job |
|
|
||
| Centralized Principal Investigator Management |
|
|||
| FTP Delivery Updates |
|
|
||
| Extended Date Range for Data Change Extracts |
|
|
||
| Subject Progress Listing: Updated Logic for Complete & Clean Statuses |
|
|
||
| User Management Support for Unmapped Training Requirements |
|
|||
| Support Higher-Volume Rule Jobs |
|
|||
| Event & Form Progress Listings: Updated Column Order |
|
|
||
| Study Deployments: Move "Include System Data" Option |
|
|||
| Redesign Rule Job Output File |
|
|||
| Enablement Change: Deployment UI & Processing Improvements |
|
|||
| Job History Includes SDS & Studio Validations |
|
|||
| Removed Legacy CDB Workbench Export Job from EDC |
|
|||
| EDC Migrator | ||||
| Limited Availability: In the current release, EDC Migrator is only available to early adopter customers. Contact your Veeva Services representative for details. | ||||
| Migrator & YAML Builder Updates |
|
|||
| Migrator Support for Signing Casebooks with Open Queries |
|
|||
| Enable CDB Incremental Setting for Migrators |
|
|||
| Safety Integrations: Suppress Safety Case Data Transfers during EDC Changeovers |
|
|||
| Migrator: Reconcile Listings Enhancements |
|
|||
| EDC API | ||||
| EDC API Features |
|
|||
| DQS API | ||||
| CDB API Features |
|
|||
Enablement Legend
- Configuration: This field lists the location(s) where configuration for this feature occurs, for example, "Studio" or "EDC Tools". "Support" indicates that this feature must be enabled by Veeva Support, and "Vault Admin" indicates that configuration must be performed by a Vault Owner in the vault's Admin area.
- Dependencies: This field lists any dependencies required to use this feature, for example, Labs or Expression Engine V2. The other columns assume that the dependencies are enabled/in use.
- Day 1 Impact to Primary Users: This feature is visible and available to one or more primary user teams (Site Users, Clinical Team, and Coders) on day 1. Otherwise, this feature is either only visible to study designers or administrator users, it requires configuration before it is visible to primary users.
- Users with Day 1 Visibility: This feature is visible to these users on day 1 if no configuration occurs.