Pre-Release Date: November 15, 2016 | Release Dates: December 2 & 9, 2016
We are pleased to bring you Vault V16. Read about the new features below. You can find information on enabling new features in V16 Feature Enablement Details.
Vault Documents
Integration with Microsoft Office Online
With this enhancement, users can easily and simultaneously collaborate on content creation within Microsoft Office Online applications (Word, PowerPoint, Excel). Any Vault user with an Office 365 business account can edit documents directly within their browser, without downloading any files or installing a plugin. Learn more.
Document Tags
Admins can now create tags to label any document with a topic, category, or other type of identification. Users can easily find tagged documents by searching or filtering on the tag name.
Organizations can also choose to automatically tag documents that include specific phrases in the full text content. For example, VeePharm could automatically tag documents that include the phrases “side effects,” “adverse events,” or “adverse reactions” with the Safety tag. Vault analyzes and tags new content after file upload. Learn more.
Create & Import Document Links
This release expands on the Link Annotations feature by introducing a fuller set of options. Users can now create Linked Document relationships, including links to anchors in related documents, from the relationship panel. Previously, adding these relationships required users to create link annotations. We refer to the relationship and link to anchor as Document Links. Document Links may or may not have attached link annotations.
When first adding a Document Link from the relationship panel, there is no related link annotation. Users can opt to create a related link annotation using the Link to Content action. When creating annotations this way, users don’t need Edit Fields permission on the document and do not need to select an anchor.
Users can also import Document Links from one document to another in the same vault. This enhancement significantly reduces the effort required to create similar reference links on multiple closely-related documents.
The Document Links feature streamlines the process of creating and reusing reference links. Learn more.
My Collection
Users sometimes need to create an ad hoc selection of documents from multiple different filter sets and library views. Today, they create temporary binders to group documents before performing some action on them. The new My Collection feature gives users a quicker way to meet this need. When using My Collection, users add documents to their personal My Collection page from any document tab or from the Doc Info page. Inside My Collection, users can perform bulk actions like Edit Fields, Change State, or Create Batch. After performing actions, there’s a quick option for removing all documents, leaving My Collection ready for the next time it’s needed.
My Collection serves a different purpose from Favorites, which are more useful for storing a semi-permanent list of documents that matter to a user. Learn more.
Legal Hold
With this release, Vault enables customers to meet regulatory and legal compliance requirements for preserving documents related to ongoing litigation. The new Legal Hold capability allows users with the Legal User security profile to create legal holds (as object records), easily apply them to documents according to subject matter, and lift those holds when appropriate.
Customers can rest assured that documents under legal hold remain preserved in such a way that users cannot delete content, but the business can continue leveraging documents across authoring, workflow, and lifecycle activities. Learn more.
Create & Relate Object Records from Documents
This release enables users to create object records while working with specific documents and relate the two through a document reference field (new in V16) on the object. Prior to this release, users needed to create or find the document and then navigate away to create a new object record and select the document. This feature introduces a new configurable user action in document lifecycles that can accomplish these steps without leaving the document.
With the new action, users can create an object record directly from a document version and Vault will automatically select the correct document in the document reference field. This feature is available in any application, but is particularly useful for creating document change requests in QualityDocs Multi-Document Change Control. Learn more.
Add to Binder Bulk Action
This release introduces a new bulk document action to efficiently create a binder and add a large number of documents to it. The new Add to Binder action also allows users to add documents to an existing binder. When using this action, Vault always adds documents to top level (“root”) of the binder, rather than to specific sections. If the binder’s root section already includes one of the documents, Vault does not add it again. Learn more.
Generate XFA PDF Forms from Vault Objects
In past releases, Vault introduced support for FDA Form 2253 generation in PromoMats and Submissions applications. Now, Vault can generate and populate any XFA PDF form, for example, FDA Form 2301. Using object records in the new XML Element object, Admins can build the underlying structure of a form’s XML and map the field inputs to document fields from within the Admin area. When users trigger the new Generate Form configurable user action, Vault creates a new form document, constructs the XML using the object records, and populates the newly created form with values from the mapped fields. Learn more.
The existing Generate 2253 action is only available for the Compliance Package document type, and only where the binder’s Country is United States. However, Admins can configure the new Generate Form action to apply to any lifecycle state, and with a variety of conditions. Each action can generate up to five (5) forms, allowing Admins to replicate the current 2253 process by generating both FDA Form 2253 and Supplementary Sheet 1 in a single action. Admins can set up form generation from a binder (where mapped fields can be on the binder or its component documents) or from a single document.
Organizations that wish to use this feature should work with their Vault Services team to complete configuration.
Doc Info: File Info Section
In the Doc Info page, the fields displaying source file information (Size, Format, Pages, etc.) now appear in the new File Info section, directly under the General section. This release also introduces the new File Name field to show source file details.
Renditions & Annotations
Sticky Note Annotations
In this release, users can create “sticky notes”: note annotations with a fixed size icon placemark. Using sticky notes, users can comment on a specific item, region, or element without creating a boundary box or selected text. Vault preserves the sticky note format and icon when using the Offline Annotation feature. Learn more.
Restore Placement for Bring Forward Annotations: Restores Across Pages
This enhancement builds on functionality from V15, allowing Vault to restore placement for text annotations (notes and links) brought forward from a past version. In the initial release, Vault could only restore annotations on the same page. With release, Vault searches across all pages and restores placement if the selected text is found anywhere in the document. Note that Vault cannot restore placement when the text exists multiple times in the document. Learn more.
Generate Bookmarks for Captions
If enabled, this enhancement allows Vault to bookmark captions within an MS Word document, even if the document does not include a List of Figures. Vault groups the bookmarks into sections by caption label type: List of Figures, List of Tables, or List of Equations. Learn about auto-generated renditions.
Bookmark Styles
When creating bookmarks for MS Word files, Vault can now replicate some of the heading formatting within the document viewer Bookmarks panel and within the downloadable PDF viewable rendition. Organizations can enable each of these settings separately. Learn about auto-generated renditions.
Title Style: Vault generates headings for Title styles in MS Word. These bookmarks appear like a Heading 0 above Heading 1.
Uppercase: Headings using All Caps or Small Caps will show as all uppercase bookmarks.
Bold & Italic Font Styles: Headings using Bold or Italics styles will show with the same effects. Note that this styling affects only the downloaded viewable rendition.
If your vault generates bookmarks based on the document’s table of contents, bookmarks won’t include any of the above styles, unless the document itself does not include a TOC.
This example shows the bookmarks in a downloaded viewable rendition.
Multi-Document View Available from Object Records
This release expands the multi-document viewer, allowing users to open it for related documents on an object record. This viewer provides a seamless and contextual way for users to view a group of documents.
We’ve also made several other enhancements to the multi-document viewer:
More information about the related binder or object record is visible.
Open workflow tasks on related object records are visible.
Users can start a bulk document action.
Sort Comments on Videos by Timestamp
This feature allows users to sort document-level comments on video documents by the first valid timestamp in each comment. This enhancement lets users view comments in the same order as the content they discuss. Replies, comments without a valid timestamp, and comments on non-video documents continue to sort by Creation Date.
Enhanced Image Quality in MS Word Viewable Renditions
When enabled, this feature preserves the native image resolution (if 600 PPI or lower) in viewable renditions from MS Word source files. Vault will downsample images greater than 600 PPI. As a result, viewable renditions may have a larger file size and renditions may take longer to generate.
Note that users must set the MS Word option for Image Size and Quality in their source files to Do not compress images in file prior to inserting images because MS Word’s default downsampling is 220 PPI. Learn about auto-generated renditions.
Overlays & Signature Pages Don’t Flatten Fillable PDFs
In previous releases, Vault “flattened” fillable forms (XFA and standard PDFs) when applying an overlay or signature page. This enhancement preserves fillable functionality in these forms. Downloaded renditions will include the overlay or signature page, but users will still be able to fill out the forms.
Adobe InDesign 11 (2015) Support
This release adds support for rendering InDesign files created with the latest version of Adobe InDesign CC (2015). Learn about InDesign rendering.
Vault Objects
Document Reference Fields on Objects
Object records can now include fields that reference documents. Admins can configure document reference fields to point to a document or to a specific version of the document. When creating or editing object records, users simply pick a document from the field. Learn more.
For example, the Change Request object has a document reference field to identify the document version for the requested change. The user creating the Change Request record uses the Document to Change field to select a specific document version for the request.
EDL Item Actions: Upload Files & Create Placeholder
This feature speeds up and simplifies the process for creating placeholders or creating new documents from uploaded files. When users select Upload or Create Placeholder from the actions menu on an EDL Item record, Vault initiates the creation process and defaults field values on the placeholder or new documents with values from the EDL item. Learn about working with EDLs.
Create & Relate Documents from Object Records
Create & Relate Documents from Object Records allows users to manage an object record’s related documents while staying in the context of that record. Users can quickly add and remove existing documents from the record, or create a new document and automatically relate it to the record. Prior to this feature, users needed to navigate to each individual document in order to link it with or unlink it from an object record.
Note that this functionality is for documents related through a Object-type document field, not through a document reference field on the object.
Create & Relate Records from Records
This feature provides a quicker, simplified process when users are creating or editing object records with object relationships. A user editing a record can create a new record in the related object without leaving the context of the original record. Prior to this feature, users who found that a needed reference object record did not yet exist would need to save the record they were creating, navigate away, create the new related record, and navigate back to the original record.
For example, a user entering product details can create the related product family without leaving the product detail screen.
EDL Template Object
This feature improves the creation and management of EDL (expected document list) records by separating templates from the actual objects. EDL Template and EDL Item Template are new objects, distinct from EDL and EDL Item objects. With this change, the templates can have different fields and administrators can design more logical access control. Users create EDL and EDL Item records from templates using the new Create EDL from Template action, available from the EDL list in Admin > Business Admin or a custom object tab. Learn about configuring EDL templates.
Save & Create Button for Object Records
This feature streamlines the process of creating multiple records. When users finish filling fields to create one record, they can click Save + Create to continue directly to creating the next record.
Hierarchical Copy & Cascade Delete for Over 1,000 Records
This feature extends the “Hierarchical Copy” and “Cascade Delete” capabilities to support copying/deletion of over 1,000 records. Large deletions and all copies occur asynchronously.
Setting to Skip Specific Fields when Copying Records
This enhancement provides a new setting on object fields: Do not copy this field in object record.
Access Related Records from Object Record List View
In the object record list pages, columns displaying object fields now render hyperlinks, which simplify navigation within Vault. For example, the Studies list page includes the Product field, which now renders the related product as a link. Users can click the link to open the Product record detail page. This feature is available in object record lists within Admin > Business Admin and custom object tabs.
Lifecycle & Workflow
Batch Approval
Batch review and approval of documents has been one of Vault’s most requested features. This release allows users to bulk review and approve documents with less complex lifecycles.
Batch Approval uses the new Batch object and Batch Approval object lifecycle to facilitate this process. Users relate documents to a Batch record using the new Create Batch option within bulk document actions, then send the record through its own lifecycle. Admins can configure special entry actions within the Batch Approval lifecycle which update the lifecycle states of related documents.
Using this feature, it’s even possible to move documents with different lifecycles using a single batch action. To support this, we’ve expanded the existing “special” states (now called “state types”) to include In Review and Rejected, in addition to the existing options: Starting State, Steady State, Superseded State, and Obsolete State. Admins configuring state entry actions for the Batch Approval lifecycle select a state type to move the documents to, rather than an explicit document lifecycle state. Vault will then move documents to the corresponding state specific to their lifecycle. For example, an entry action on a Batch record moves all related documents to the state type Steady State. Based on the documents’ different lifecycles, individual documents move into various states like Approved for Distribution and Approved for Use.
A new object record entry criteria (only available for the Batch Approval lifecycle) allows Admins to prevent a Batch record from entering a state unless its related documents meet specific criteria based on their states. For example, a Batch record cannot change to Approved state if some of its related documents are in the Rejected state type.
Learn more about configuring and using Batch Approval.
Object Workflow Task Comments
With this feature, Admins can configure object workflows that allow task owners to enter comments when completing a task. Depending on the workflow configuration, the comments could be required and/or associated with a specific verdict.
Learn more about configuring object workflows.
Object Workflow Step to Update Record Fields
This feature extends the ability to automate business processes in Vault with a new type of step in object workflows. Admins can now configure a workflow to update a record field as part of an automated process. For now, we’ve limited this ability to text, number, and date field types. Admins can represent the update value as a formula, which also supports several text and date functions. Support for other field types will be available in future releases. Learn more.
Available Tasks for Object Workflows
Available Tasks enhances the way that Vault assigns tasks in object workflows. By selecting this option, Admins can configure a workflow that makes a task available to a group of participants, any of whom could claim and complete the task. Once a user has claimed the task, Vault assigns it to that user and it no longer appears as available to others. This pattern for task assignment can streamline business processes by offering work to a group of users who are all qualified to complete the task. Learn more about configuring object workflows.
Roles as Recipients for Entry Action Notifications
When configuring notifications as a document lifecycle state entry action, Admins can now select a document lifecycle role as the recipient. Unlike selecting groups, selecting roles makes recipients specific to each document’s sharing settings. This enhancement allows organizations that send region-specific notifications to streamline their configurations. Learn more.
Task Comments Visible in Object Record Workflow Timeline
Comments entered by assignees when completing a workflow task now display in the Workflow Timeline section of the object record detail page. This feature lets workflow participants or other record viewers quickly see the comments related to a task, such as the explanation of the selected verdict.
Notification Workflow Step to Display ‘Show More’ Link
When users select Show decisions and comments from previous task in a workflow notification step, the Show More link to view comments in the Notifications page no longer appears. Users can still view workflow notification comments in the Doc Info page.
Configuration & Administration
Configuration Migration Packages
Configuration Migration Packages allow an Admin to migrate configuration changes between two vaults. Using this feature, customers can now configure and test in a sandbox vault and then migrate their changes to a production vault. On the source vault, Admins select configuration components for an Outbound Package and then export as a Vault Package file (VPK). Admins on the target vault can then import the VPK as an Inbound Package, review, and deploy it. Learn more.
Object Attribute Lookup Fields for Documents
In V15, we introduced the new Lookup field type for documents. Originally enabled only by request, Lookup Fields for Documents are now available in all vaults.
Lookup fields “look up” an attribute on an object record already associated with a document and bring its value down to the document as a read-only field. Lookup fields can support search, filtering, and reporting. They can also provide document viewers with additional context for Dynamic Access Control. Learn more.
Configuration Mode
This feature allows System Admins or Vault Owners to place their vault into “Configuration Mode.” This mode locks out all non-Admin users, creating a safe environment for performing configuration changes. Learn more.
Permission Set Control for Allowed Delegates
This release introduces a new way of limiting the Delegate Access feature, which aids customers that allow partner organizations to access their vaults. The new Allow as a Delegate permission lets Admins prevent users with specific security profiles from becoming delegates. Using this feature, an organization could, for example, only allow internal users or first-level support personnel to become delegates. The restriction applies to both users delegating their own accounts and to Admins delegating on behalf of other users. Users without this permission can still delegate their own accounts to a user with the permission.
With this release, we preserve your vault’s existing functionality by granting the new permission on all standard permission sets. To remove the new permission, your vault must use custom security profiles and permission sets.
Vault Loader Enhanced Logging
Users can now choose to include metadata or field values in the output log files when creating documents or object records via Vault Loader. Vault queries for metadata and field values after creation and includes the output in the log files. Learn about Vault Loader.
New Metrics for Performance Statistics
In this release, we’ve added the following metrics to the Performance Statistics object. These metrics provide insight into system response time and how frequently users view object record lists or object record detail pages:
Avg Time Object List View
Avg Time Object Detail View
Object List View Count
Object Detail View Count
Learn more about performance metrics.
Reuse Names of Deleted Fields
Vault now allows Admins to reuse names of deleted document fields, for example, [CODE] audience__c. Previously, customers needed to log Veeva Support requests in order to reuse the name of a deleted field. Now, Admins can simply name new fields as needed.
Dynamic Access Control
User Role Constraints
This feature allows Admins to constrain role assignments to specific users if the vault uses Dynamic Access Control to secure documents or object records. When saving a User Role Setup record, the system checks the new User Constraint object to verify that the role assignment is allowed.
Your organization can use this feature in the context of large-scale or global deployments where Business Admins are located in different countries or different business units provision their own local users. Central Admins can control which roles are available to specific users in order to prevent mistakes in sensitive security assignments. Learn more.
Custom Roles on Objects
In previous releases, Dynamic Access Control for objects supported only the standard roles: Viewer, Editor, and Owner. This new feature introduces the ability to add Application Role records to an object configuration and select role permissions (Read, Edit, Delete) specific to that object. Custom roles are only available on objects that use Matching Sharing Rules.
This feature unifies the security model for documents and objects. For example, Admins can define the Medical Reviewer application role and set up this role with both document and object permissions. The same role can now drive both document and object access permissions, simplifying the setup process.
Learn about configuring custom roles and about this feature’s enablement.
DAC for Objects: Secure Object Records by Name
This feature expands the Matching Sharing Rules feature (Dynamic Access Control on object records) by allowing Admins to create User Role Setup records that explicitly reference a specific record on the secured object. For example, a User Role Setup record could assign Thomas Chung to the Editor role on study VVT485-301. This new capability reduces the setup needed to secure object records and is particularly useful for securing records in a parent-child relationship, like Study > Study Country > Study Site. Learn more.
Support for Auto Managed Groups in Configurations
Before this release, Admins could not select Auto Managed groups in various configurations, for example, when configuring document field-level security overrides. In this release, Admins can use a new setting on Auto Managed groups to make them available for configurations. Learn more.
As part of this change, vault cloning now includes any Auto Managed groups that are available for use in configurations. If the related User Role Setup records don’t exist on the new vault, cloning creates empty groups.
UI & Field Changes to Application Role Objects
We’ve made several minor changes to the Application Role object:
Admins can now review, create, edit, and delete Application Role records from Admin > Users & Groups. Depending on the object configuration, the object may not appear in Admin > Business Admin.
The Application Role object now includes Label and Name fields. Vault migrates the previous Name value into the new Label field and auto-populates the Name field.
Notice for Dynamic Access Control Lifecycle Roles
Warnings now appears in the document lifecycle role Sharing Rules tab (Admin > Configuration > Document Lifecycles) if the sharing rules differ between the lifecycle roles that use the same application role. Although this will not cause any problems currently, it may cause migration failures when Vault releases features in the future. Learn more.
Reporting
Workflow with Object Report Types
New Workflow with Object report types support reporting on object workflows in a similar manner to the existing Workflow with Document report type. These reports can pinpoint open and late tasks for object workflows, and then group tasks by owner, date, or other attributes.
To use object workflow reports, Admins will need to create a new report type for each workflow-enabled object. Report authors can then use these report types to create new reports. Workflow with Object reports support other recent reporting enhancements such as conditional fields. Learn more about creating new reports.
New Options for Workflow with Document Reports
This release enhances the existing Workflow with Document report type by adding support for conditional fields. Conditional fields enable report authors to categorize document workflows and tasks based on conditional expressions that evaluate workflow, task, and document attributes. Learn more about creating new reports.
Setting to Allow Deleted Picklist Values in Report Filters
Users can filter the reports by deleted picklist values. This ability is now associated with an Admin > Settings checkbox, Allow deleted picklist values in report filters, and so an Admin can disable it.
Audit Logs
Cover Pages for PDF Audit Exports
This release improves the compliance process by adding an auto-generated cover page to all PDF audit log exports. Admins can edit the standard template for this page to show the information that is most relevant for their organization, including:
Name of the vault
Name of the audit log (System Audit History, Document Audit History, etc.)
Date and time of the export
Username of the user who exported
Details for filters applied to the audit log
All PDF exports of audit logs or audit trails now also include a footer showing page numbers, as well as the date and time of the export.
Note that enabling this feature changes Signature Pages (in Admin > Business Admin) to Signature & Cover Pages. Learn more.
eTMF & Study Startup
Create Milestones from Templates in Clinical Vaults
Admins can now create Milestone Templates (object records), providing a consistent, efficient approach to milestone creation. With milestone templates, users create milestones in bulk for their studies, countries, and sites, using templates tailored to match country-specific business processes. Previously, a user had to create many individual milestones for each study. Learn more.
This feature deprecates Up and Previous milestones and introduces Milestone Dependencies in their place.
In this release, Vault delivers a Study Startup milestone template set that includes generic milestone templates (including dependencies and associated EDL templates) at the study, country, and site levels.
Apply EDL Templates for Milestones
Many organizations track expected documents according to specific milestones. This feature lets users apply an EDL template to a Milestone record. With an EDL template applied to the milestone, users can more accurately plan and track relevant EDL items for a milestone. Further, organizations can configure EDL templates which, beyond creating new EDL Item records, also update existing EDL items. For example, when a team plans a new site-level milestone, users can apply an EDL template that increases the expected number of EDL items for the site. Learn more.
Set Milestone Values by EDL Item
The “Apply EDL Templates for Milestones” feature introduced the ability to associate Milestone records with expected documents (EDL Item records) to measure TMF completeness by a given deliverable. This feature builds on that functionality by allowing users to view documents by milestone, based on the milestone’s expected documents. The enhancement provides a consistent experience and allows users to easily visualize the connection between milestones, documents, and expected documents. Learn more.
As part of this feature, we will deprecate the “Milestone-Document Linking” feature. Vault will no longer auto-populate the Milestone document field based on the Milestone Type field value.
Saved Views in Site Activation Progress
Within Study Startup’s Site Activation Progress view, users can now save filters as custom views. This enhancement lets users refer back to common criteria more easily. Learn more.
RIM
Submission Content Planning
This release allows RIM Submissions customers to create and track submission content plans directly in vault using EDL (Expected Document List) objects and the new Tree View feature. Admins can define the various content plan templates (as EDL Template and EDL Item Template object records) to accommodate regional variations. Templates may include repeating sections, for example, Submission Clinical Studies and Submission Drug Products. Updating the Content Plan (EDL) object configuration lets organizations add additional fields to track details that are specific to their business process or submission format. Learn more.
This a limited release feature available only to early adopters.
Tree View
Tree View helps users explore a hierarchy of related records. The view supports multiple related objects as well as self-referencing object relationships. Users can search all records related to a common root, sort records within a hierarchy, perform bulk actions on the records, and export the hierarchy as a formatted list. Learn more.
Tree View is a limited release feature available only to early adopters with Submission Content Planning.
RIM Data Model Updates
With this release, all applications in the RIM suite will receive new object definitions. Some of these changes are in response to customer feedback, while others continue to move Vault closer to full IDMP coverage. Learn more about the data model updates.
Auto-Delete Orphaned Submissions Documents
To help ensure that SubmissionsArchive reflects only finalized content that the organization submitted to the Health Authority, this release introduces the automatic deletion of “orphaned” files. Deletion works via a daily job that cycles through the vault and identifies documents not associated with a submission. These orphaned documents can occur when users import and subsequently remove a submission, and the files in the submission are not referenced by another application. Learn more.
Cascade Delete for Self-Referencing EDL Objects
This feature extends the “Cascade Delete” capability to support deletion of child EDL records.
Hierarchical Copy: Copy Field Values from Parent EDL Records
This enhancement allows users to choose whether or not to copy updated field values from a parent EDL record to a related EDL record when using hierarchical copy. Learn more about copying records.
SPL File Renditions
The enhancement lets Vault create a viewable rendition for ZIP files containing the Structured Product Labeling (SPL) XML and accompanying image files. Learn more.
QualityDocs
Multi-Document Change Control
V16 introduces a set of enhancements designed for Multi-Document Change Control. In this release, Vault includes the tools needed to accomplish these functions, but Admins must define custom lifecycles and workflows for the routing of change controls. The individual components that support this feature are entirely configurable, allowing organizations to model many different business processes.
Organizations that wish to use Multi-Document Change Control immediately should contact Veeva Support to discuss enablement and configuration. The next release will introduce enhancements to provide a best practice configuration, and will help customers get started more quickly with this feature.
Better Flows for Change Requests & Change Controls
Vault users can manage change requests separately from change controls, which enables collection, organization, and triage of requests. These abilities allow proactive planning and change execution.
Change Managers can define and capture a plan for simple single document changes or for complex changes affecting multiple documents planned for release or obsolescence. A single Multi-Document Change Control record can govern release of new documents, superseding of existing documents, and obsolescence in a single flow, streamlining some of the most complicated aspects of change management. Organizations can further automate this process via scheduled jobs, mitigating risk and simplifying change execution.
Notifications on Change Requests
As Change Managers route requests through their own dedicated lifecycle or the system routes them automatically using a related change control, Vault can send automated notifications to submitters, keeping them in the loop as change happens.
Support for Complex Workflow Configurations
Change control approval flow is fully configurable. Documents may undergo their own lifecycles’ best-practice workflows up to the point where approval would occur. The document change control routes the Change Control record as well as its governed content. With this, organizations can use a single approval workflow with a single verdict (per approver) to execute large-scale change.
Operations Cascade to Governed Documents
All operations (captured eSignatures, state changes, and field updates) executed on or by the Change Control record cascade down to the individual governed documents. This means that documents which undergo change control have complete audit trails linking them to the governing Change Control records. It also means the documents’ eSignature pages are complete, optionally manifesting signatures captured as part of the Change Control record’s approval. Vault displays this information in the document’s Version History as well as in the audit trail.
Multichannel
Create Presentation Retains Dynamic Content
PowerPoint documents often contain links to other locations within the document and hyperlinks to external sites. The Create Presentation action can now convert PowerPoint source files into HTML content so that the links remain active in CLM.
Create Presentation Supports Incremental Updates
This enhancement improves the Create Presentation action to better handle updates to the related original document. Vault users can now version specific multichannel slides using this action. For example, if only page three (3) of the original document contains updates, Create Presentation will only version the multichannel slide document corresponding to page three. Previously, removing a slide from an existing presentation would cause that slide to enter its lifecycle’s Obsolete state. As of this release, removed slides will no longer change state. Learn more about using Create Presentation.
New Objects, Fields & Picklist Values to Support CRM Enhancements
This feature adds various new objects, fields, shared picklists, and picklist values to Multichannel vaults in order to support CRM enhancements like Engage Meeting and Content Type for Approved Email. Learn more about setting up approved emails.
Approved Email Enhancements
The Email Template Type picklist now includes the Remote Meetings Invite Template value, which allows users to specify that a template is valid for Engage Meeting invites.
The Content Type object allows users to associate custom content types with email templates.
We’ve added the new Content Type field to the Email Template document type. This field can specify the related content type for an email template.
General CLM Integration Enhancements
The Multichannel Slide document type includes the new iOS Viewer field. Selecting the WKWeb View option provides an improved view of HTML CLM on iOS 10 or later.
The Disable Actions field has new options for Navigation Bar and History Buttons.
UI Updates & Minor Enhancements
Delete All Notifications
Users can now delete all of their notifications (Home/Tasks > Notifications) by clicking Delete all. Previously, users could only delete individual notifications.
Updated UI in Library Tabular View
We’ve updated the interface for the tabular view in the Library and other document tabs. In addition to visual changes, users can now also toggle between truncating and wrapping cell contents.
Reclassify with Search-Based Selector
When reclassifying documents, user can now use the searchable document type selector. Users who want to use the hierarchy-based selector can open it by clicking the Advanced link.
<img class="alignnone size-medium wp-image-35728" src="h