New Features: Study Versioning and more...Release Date: September 29, 2017
Release Date: September 29, 2017
We are pleased to bring you the following new features in this week’s release. See details about each feature’s enablement below.
As part of our commitment to ongoing innovation and customer success, Veeva is moving its worldwide computing infrastructure from managed data centers to the Veeva virtual private cloud (VPC) running on Amazon Web Services (AWS). This began in the second half of 2017 across all Veeva product lines. See AWS Migration FAQ.
Prevent Auto-Creation of Initial Repeating Form Record
When a repeating Form is first added to a Casebook, Vault will no longer automatically create an initial repeating Form record. Repeating Forms may not be required or used during a study. This feature eliminates the work of removing unused repeating Form records. A data entry user can click + New to create the first repeating Form.
Changing an Event Date Prompts Reason for Change
When users change Event’s dates, Vault prompts them to select a reason for change in the same way as when they change Item values. Organizations can work with Veeva Support to configure the list of reasons for change to have different change reason options than Item-level change reasons.
Freeze & Lock all Forms in an Event
This feature allows EDC users with freeze or lock permissions to be able to apply or undo these actions to all forms in an event. Users can apply these actions by selecting Freeze All Forms or Lock All Forms from the Event’s More Actions menu.
Study administrators can control and build new Casebook Definition versions for a Study. This feature includes the ability to lock casebook versions to prevent changes and create new versions for editing. With versioning, study administrators and clinical programmers can export and import versioned Casebook Definitions. This feature supports study design changes without impacting existing Casebooks.
Object Field Defaults
With the Object Field Defaults feature, Admins can set default values for object fields to populate upon object record creation or save. These defaults can use a literal value, such as a specific number, or a formula. Formulas for field defaults use functions and operators to combine literal values and tokens. Users can override default values if they have permission to edit the field. By using object field defaults, organizations can ensure consistency across fields such as Serial Number or that a field, like Legal Question, is always set to Yes on certain records.
Flash Report Preview
This feature allows the option to include reports in Flash Report emails. With this option, customers can easily access and preview reports from the Flash Report email. When scheduling a Flash Report, users now have the option to select the Include report in email checkbox. This option includes a copy of the report in HTML format in the Flash Report’s email and contains a link to the report in Vault.
Vault Loader & Configuration Migration
New Supported Component Types for Configuration Migration
The following component types are now supported for Configuration Migration and Vault to Vault comparison.
- Report & Dashboard
- Rendition Type
- Workflow Participant Rule
- Document Relationship Type
- Field Layout
Vault Configuration Report
Vault Configuration Report allows a user to extract the configuration of a vault into an Excel report. This report includes configuration of components as well as reference data used by the components. The Vault Configuration Report is particularly useful for tracking a vault’s configuration during migrations and implementations.
Vault Java SDK
Debug Log for Vault Java SDK
Vault Java SDK allows Veeva Services to program custom business logic which executes whenever users perform an operation on records. With the addition of the Debug Log, programmers can easily troubleshoot issues in their code. The Debug Log captures details about programming errors and errors which result from exceeding governance limits (Vault Java SDK errors). To inquire about Vault Java SDK solutions, contact Veeva Services.
Register OAuth2/OIDC as Metadata in SSO Profile
To enable external applications to discover and configure the login requirements and authentication flows for Vault OAuth2.0 / OpenID Connect users, those applications need to obtain the remote authorization server metadata. This feature allows configuration of remote authorization server metadata so it can be discovered and downloaded by external applications.
Google Chrome Blocks Saved Passwords in eSignature
To provide better security, Veeva blocks most browsers from remembering passwords. A recent update to the Google Chrome browser allowed it to remember Vault passwords in some circumstances. With this release, Vault has modified the eSignature password field to prevent Chrome from remembering passwords.
Feature Enablement Details
|Prevent Auto-Creation of Initial Repeating Form Record||Auto-On||EDC|
|Changing an Event Date Prompts Reason for Change||Auto-On||EDC|
|Freeze & Lock all Forms in an Event||Auto-On||EDC|
|Register OAuth2/OIDC as Metadata in SSO Profile||Support||Platform|
|Google Chrome Blocks Saved Passwords in eSignature||Auto-On||Platform|
|Object Field Defaults||Configuration||Platform|
|Flash Report Preview||Auto-On||Platform|
|Vault Loader & Configuration Migration>|
|New Supported Component Types for Configuration Migration||Auto-On||Platform|
|Vault Configuration Report||Configuration||Platform|
|Vault Java SDK|
|Debug Log for Vault Java SDK||Configuration||Platform|
|1 The Option to Disable Auto-Save on Forms feature (EDC) was removed from the release.|
See the following explanations for feature enablement options:
|Auto-on||Automatically activated and no configuration is required before using the feature; note that in some cases, a new feature is dependent on another feature that must be enabled or configured.|
|Admin Checkbox||Admins must turn on the feature with an Admin checkbox. Note that some “Auto-On” features have a checkbox setting that hides the feature; these will show “Auto-On.”|
|Configuration||Admins must configure the feature (separately from an Admin checkbox) before it is available to use or is active; for example, a Clinical Programmer must create an Item Definition of a certain new Item Type.|
|Support||On/off option controlled by Support.|