21R3 Feature Enablement Details
Pre-Release Date: November 8, 2021 | CDB Pre-Release Date: November 12, 2021 | Release Date: November 19 & December 3, 2021The following is a list of new features introduced in 21R3. 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 21R3. 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 21R3 may have different enablement settings. See What's New in 21R3 for more detailed enablement information.
Feature Enablement Summary
Feature Name | Configuration | Dependencies | Day 1 Impact to Primary Users | Users with Day 1 Visibility |
---|---|---|---|---|
Data Entry | ||||
Actions for Repeating Item Groups |
|
|||
Empty Form Link Indicator | Studio |
|
||
Unsetting ILB Restores Default Data |
|
|||
Data Review | ||||
Run Core Listings Job from Review Tab |
|
|||
Display Historical SDV & DMR Status when Requirement Mode is Set to No Review | Review Rollup Version 2 |
|
||
Protocol Deviations Study Filter | Protocol Deviations |
|
||
Clinical Coding | ||||
Batch Upversioning Enhancements |
|
|||
JDrug Suggestions & Upversioning |
|
|||
Study Design & Configuration | ||||
Allow Studio Users to Create Organizations, Collections & Studies |
|
|||
Arms & Cohorts | Studio | Expression Grammar V2 |
|
|
Progressive Display Enhancements | Rules V2 |
|
||
New Subject Statuses to Align with CTMS |
|
|||
New Aggregate Functions | Expression Grammar V2 |
|
||
Previous & Next for Repeating Event Groups, Forms & Item Groups | Expression Grammar V2 |
|
||
Rule Syntax Enhancements | Expression Grammar V2 |
|
||
Study Administration | ||||
Audit Trail Export by Site |
|
|||
Audit Trail Export Filtering |
|
|||
Extract Job Governor | null |
|
||
Study Data Extracts: Add Additional Columns to System Datasets |
|
|||
SDE: General Enhancements |
|
|||
SDE: Versioning |
|
|||
Study Listings |
|
|||
Error Console Enhancements |
|
|||
Include Full Hierarchy in Preview/Run Rules |
|
|||
Labs | ||||
Randomization | ||||
Set Subject Status to Randomization Date | Randomization |
|
||
Role Management & Security | ||||
Show Course Completion in the Training Report | Vault Admin | Veeva Learning Integration |
|
|
Veeva Learning Integration Enhancements | Veeva Learning Integration |
|
||
Study Role Enhancements |
|
|||
Deployments | ||||
Migration Environments |
|
|||
Vault CDB | ||||
Batch Queries & Review |
|
|||
CDB Deployments | CDB |
|
||
CDB Views |
|
|||
Additional UI Filters for Listings |
|
|||
Review & Query Dashboards |
|
|||
Ingestion Audit Log |
|
|||
Key Manager |
|
|||
Auto-increment Sequence Number | Workbench |
|
||
Pin Columns in Listings |
|
|||
CQL Editor Enhancements |
|
|||
Integrations | ||||
Safety Link Support for External Labs | EDC Tools |
|
||
Coding Values in E2B |
|
|||
Treatment Forms in E2B | EDC Tools |
|
||
Long Narratives |
|
|||
Migration Vault | ||||
Limited Availability: In the current release, Migration Vault is only available to early adopter customers. Contact your Veeva Services representative for details. | ||||
Support for Migration of Restricted Data | Migration |
|
||
Post-load Form Status Selection | Migration |
|
||
Validate YAML for UTF-8 Character Set | Migration |
|
||
Migration UI Enhancements | Migration |
|
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.