22R1 Feature Enablement Details
Pre-Release Date: March 28, 2022 | CDB Pre-Release Date: April 4, 2022 | Release Date: April 8 & 22, 2022The following is a list of new features introduced in 22R1. 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 22R1. 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 22R1 may have different enablement settings. See What's New in 22R1 for more detailed enablement information.
Feature Enablement Summary
Feature Name | Configuration | Dependencies | Day 1 Impact to Primary Users | Users with Day 1 Visibility |
---|---|---|---|---|
CDMS | ||||
Standardize DateTimes in Email Notifications |
|
|
||
Enablement Change: Action UI |
|
|
||
Display Item Group Headers in Detail PDFs |
|
|
||
Data Entry | ||||
Form Linking UI/UX Enhancements |
|
|||
Item to Form Linking | Studio | Data Model V2 |
|
|
Enablement Change: Removed Ability to Opt Out of Item-level Intentionally Left Blank |
|
|||
Data Review | ||||
Additive Review | Studio | Review State Rollup V2 |
|
|
Access Study Listings Jobs from the Review Tab |
|
|
||
Enhancements to Medical Assessments |
|
|||
Ability to Jump to Previous/Next Instance in Expand Log Form Layout |
|
|
||
Clinical Coding | ||||
Unique Terms Report |
|
|||
Inactivate Coding Forms |
|
|||
Labs | ||||
Add Analyte Name Column to Audit Trail | Labs |
|
||
Add Initiated by Study and by Site Columns | Labs |
|
||
Add Lab Name & ID to Outdated & Updated Normals Reports | Labs |
|
||
Randomization | ||||
Option to Require Login Credentials to Reveal Treatment | Randomization |
|
||
Study Design & Configuration | ||||
Library Classifications |
|
|||
Use Destination as Origin when Copying into a Library |
|
|||
Comparison Rules Enhancements | Data Model V2 |
|
||
Track Removal of a Child from the Parent as an Update on the Parent |
|
|||
New Attributes, Functions & Usability Improvements for Rules | Expression Grammar V2 |
|
||
Query Scoping for Repeating Objects |
|
|||
Event Window Updates |
|
|||
Studio Usability Improvements |
|
|||
Study Administration | ||||
External FTPS & FTP UI Enhancements | Whitelisted IP Address & Port Range |
|
||
SDE: Include Randomization Treatment |
|
|||
Reconstitute Code Requests Job Enhancements |
|
|||
SDE: General Enhancements |
|
|||
SDE: UI Configurator |
|
|||
Deployments | ||||
Vault Configuration Report |
|
|||
Restore Study Environments |
|
|||
Role Management & Security | ||||
Study Role Enhancements |
|
|||
Prevent Bulk Updates to User Email |
|
|||
Integrations | ||||
Codelist Mapper for Safety Configuration |
|
|||
Suspected Concomitant Medication | EDC Tools | Form Linking V2 |
|
|
Vault CDB | ||||
Import Manifest Builder |
|
|||
Import Change Approval |
|
|||
Export Change Detection & Updates |
|
|||
New @HDR & @Form Attributes |
|
|||
Migration Vault | ||||
Limited Availability: In the current release, Migration Vault is only available to early adopter customers. Contact your Veeva Services representative for details. | ||||
Casebook Version Limit Validation |
|
|||
SDV, ILB, Frozen, Locked & Signed Attributes |
|
|||
Source Stamping |
|
|||
Support for Migration of Code Requests |
|
|||
Support for Migration of Studies Using Safety Link |
|
|||
View Pending Records |
|
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.