The following is a list of new features introduced in 18R1. 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 18R1 . See below for an explanation of feature enablement and user impact.
| Feature | Enablement | Application |
|---|---|---|
| Authentication | ||
| Beta Login Experience | Admin Checkbox 1 | Platform |
| Working with Documents | ||
| Controlled Document Templates | Configuration | Platform |
| Export All Files from Individual Document | Admin Checkbox 2 | Platform |
| Vault File Manager: Limited Availability | Support 3 | Platform |
| New Languages for Multilingual Document Handling | Auto-on | Platform |
| Upload Files when Adding Document Relationships | Auto-on | Platform |
| Vault Objects | ||
| User & Person Object | Auto-on | Platform |
| eSignature Management for Objects | Auto-on | Platform |
| Formula Fields | Configuration | Platform |
| Record Favorites | Auto-on | Platform |
| Jobs on Objects | Auto-on | Platform |
| Record Icons | Configuration | Platform |
| Update Sharing Settings Step in Object Workflows | Configuration | Platform |
| Constrain Workflow Participants by Role | Configuration | Platform |
| Select All for Object Reference Fields | Auto-on | Platform |
| Yes/No as Checkbox | Configuration | Platform |
| Object Lifecycles & Workflows | ||
| Add Participants to Active Object Workflows | Auto-on | Platform |
| Support Joins for Actions on Related Records | Configuration | Platform |
| Document Lifecycles & Workflows | ||
| Related Document Conditions for State Change & Notification Jobs | Configuration | Platform |
| Enablement Change: Advanced Workflow Role Configuration | Auto-on | Platform |
| Reporting | ||
| Enhanced Reports Tab | Auto-on | Platform |
| Document Relationship Reports for Source Version-Specific Relationships | Auto-on | Platform |
| Configuration & Deployment | ||
| Locked Objects & Tabs | Auto-on | Platform |
| API Usage Logs | Auto-on | Platform |
| Support for OAuth 2.0/OpenID Connect | Auto-on | Platform |
| New Supported Component Types | Auto-on | Platform |
| Sub-tab Container Renamed to Menu | Auto-on | Platform |
| Permissions & Access Control | ||
| Edit Relationships Permission | Auto-on | Platform |
| Object Create Permission Grants Edit Permission | Auto-on | Platform |
| Require View Content Permission to Send as Link to Non-Vault User | Auto-on | Platform |
| “Upload Unclassified” Permission Renamed to “Always Allow Unclassified” | Auto-on | Platform |
| Vault Users | ||
| Increased Delegated Access Limits | Auto-on | Platform |
| Vault Java SDK | ||
| Admin UI for Vault Java SDK | Support | Platform |
| Data Model | ||
| Data Model Harmonization for Vault Platform | Auto-on | Platform |
| Commercial & Medical | ||
| Create Related Document User & Entry Actions | Configuration | PromoMats, MedComms |
| Standard Rights Management Fields | Configuration | PromoMats, MedComms |
| New Brand Portal Widgets | Configuration | PromoMats, MedComms |
| Launch Brand Portal from Portal Selector | Auto-on | PromoMats, MedComms |
| Update to Brand Portal Document Fields | Auto-on | PromoMats, MedComms |
| Data Model Harmonization for Commercial | Auto-on | PromoMats |
| Data Model Harmonization for Medical | Auto-on | MedComms |
| Multichannel | ||
| CRM Vault Metadata Sync | Configuration | PromoMats, MedComms |
| Approved Email: Update Litmus™ Preview for iPhone X | Configuration | PromoMats, MedComms |
| Single Document Multichannel Publishing: Support for MS Word™ Documents | Configuration | PromoMats, MedComms |
| Target Specific Presentation When Copying to Another Vault | Configuration | PromoMats, MedComms |
| Clinical | ||
| Site Users in Clinical Vaults | Auto-on 4 | Clinical |
| Link Clinical User Tasks to Milestones | Auto-on 5 | Clinical |
| Hover Card & Harvey Balls on EDL Items | Auto-on | Clinical |
| EDL Hierarchical View | Auto-on 6 | Clinical |
| Multi-Site Document Distribution | Configuration | Clinical |
| Clinical FTP Loader | Configuration | Clinical |
| Data Model Harmonization for Clinical Operations | Auto-on | Clinical |
| Sort Documents in TMF Viewer | Auto-on | eTMF |
| Default Monitoring Event Participants & Activities | Configuration 7 | CTMS |
| Monitoring Visit Confirmation & Follow Up Letters | Configuration | CTMS |
| Configure Trip Report Sections via UI | Auto-on 7 | Clinical |
| Quality | ||
| Check Sibling Records as Entry Action Condition | Configuration | QMS |
| Data Model Harmonization for Quality | Auto-on | Quality, QMS |
| Data Model Harmonization for QualityOne | Auto-on | QualityOne |
| RIM | ||
| MedDRA® Dictionary Loader | Configuration | RIM Registrations |
| Cascade Document Version Locking for Content Plans | Configuration | RIM Submissions |
| Support for Investigational Licenses | Configuration | RIM Registrations |
| Enable Object Types on Standard User Role Setup Object | Configuration | RIM |
| Submissions Archive AU v3.1 DTD Import | Auto-on | RIM Submissions Archive |
| Data Model Changes: xEVMPD Support | Auto-on | RIM |
| Veeva Snap | ||
| Veeva Snap Enablement Permissions | Auto-on | Veeva Snap |
| Enterprise Mobile Management Support | Configuration | Veeva Snap |
| Certified Copy | Configuration | Veeva Snap |
| Support Up-versioning of Documents | Auto-on | Veeva Snap |
| Performance Metrics for Veeva Snap | Auto-on | Platform |
| Log Capture | Auto-on | Veeva Snap |
Notes
1 Although Admins can enable this feature with an Admin Checkbox, we suggest coordinating with a Veeva representative before enabling.
2 This feature is Auto-On in PromoMats and MedComms vaults.
3 This is an initial release for this feature, with limited availability. To enable this feature, submit a request through Vault Support, so that a Vault Product Manager can coordinate its enablement.
4 In vaults with Site Users already created. Other vaults will need to create users with the Site User license type.
5 Auto-On in vaults where Milestone Templates and Template Tasks are enabled.
6 In vaults where Milestones and EDLs are managed with lifecycles.
7 In vaults where Trip Reports are enabled.
Enablement
See the following explanations of feature enablement options:
- Auto-On: Automatically activated and no Admin 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. In other cases, users need to perform some setup, for example, with new reporting features that require creation of a new report.
- 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 use an On/Off switch and/or configure the feature before it is available to use or is active; for example, an Admin must add document templates before users can create documents from templates.
- Support: On/off option controlled by Support