Pre-Release Date: March 21, 2016 | Release Dates:April 15 & 22, 2016
We are pleased to bring you Vault V14. Read about the new features below. You can find information on enabling new features in V14 Feature Enablement Details.
Workflow Flowchart
Admins can now view workflow configurations in a flowchart style. From this view, they can also add new steps to existing workflows, navigate to step detail pages, and delete steps. Hover cards show additional information about the step, which was not previously available in the grid view. This feature provides the ability to export the workflow diagram for documentation purposes. As a bonus, the workflow details section now provides clearer information on the state of a workflow and quicker access to activate a new workflow configuration.
Dynamic Access Control for Documents
Dynamic Access Control (DAC) is a new access control model for documents that automates the assignment of users to document roles. Admins no longer need to manage groups and override rules when using DAC. Admins can enable DAC on each lifecycle role individually. Single-user roles (Owner and Coordinator) cannot use DAC.
In this model, Admins control user role assignment by managing records in the new User Role Setup object. This object can be administered by IT administrators or end users (country teams, etc.). A User Role Setup record includes a user, role, and several context values which further qualify the user’s context for the role. For instance, Thomas is a Reviewer for the CholeCap product in the United States.
If some values in the User Role Setup record are left blank, the access granted can be more general. For example, Amir is a Reviewer for the CholeCap product, but does not have a specific country selected, so he could get Reviewer access to all documents for that product if a corresponding sharing rule existed.
Based on a User Role Setup record, Vault automatically:
Adds the user as a member of an Auto-Managed Group. For instance, Thomas would become a member of the CholeCap-United States-Reviewer group and Amir would become a member of the CholeCap-Reviewer group.
Grants the Auto-Managed Group the document role for relevant documents. For instance, the CholeCap-United States-Reviewer group would automatically be given the Reviewer role on all documents where Product is CholeCap and Country is United States. Note that this step only occurs if the related Auto-Managed Group doesn’t already exist.
As user role assignments change (when users create, edit, or delete User Role Setup records), Vault automatically reassesses group membership and document access.
Learn more about Dynamic Access Control for Documents.
Auto-File Documents to Binders
With this release, Vault Platform delivers the ability to automatically file documents into binder sections based on document type and configurable metadata. In a single Auto-File Documents action, users can populate an entire binder with documents in their vault. After the initial filing action, users can perform subsequent auto-filing actions to refresh the binder and keep its contents up to date.
This new auto-file capability is available for all Vault applications except eTMF. eTMF retains its distinct approach for auto-filing, which is specifically tailored to work with trial master file business processes.
For Submissions, Vault supports the ability to perform incremental auto-filing actions, ensuring that a given binder contains only documents that it needs to provide for the related submission.
To prepare for auto-filing, an Admin configures a binder template by assigning metadata fields and document types to the desired binder sections. Users then create a binder based on a configured template and provide specific values for the assigned fields on binder sections.
For example, Thomas creates a binder using his organization’s custom Campaign binder template, which includes a Television Ads section. The template section has a default filing rule: Type = Promotional Piece > Advertisement > Television and allows for filing on the Product and Marketing Campaign fields. Thomas then edits the section filing rules on his binder to specify: Product = CholeCap and Marketing Campaign = Cardioman. When Thomas uses the Auto-File Documents action, Vault adds any documents with Type = Promotional Piece > Advertisement > Television, Product = CholeCap, and Marketing Campaign = Cardioman to the binder section. Learn more.
Bulk Replace for Owner & Coordinator Roles
Users can now perform a bulk document action to replace the users in the Owner and Coordinator roles. Previously, users were unable to update these role assignments using bulk actions.This functionality will facilitate transitioning employees between projects, as well as onboarding new people. Unlike when updating sharing settings on individual documents, users do not need to first assign the user to another role. Learn more.
This functionality is also available in the API.
Merge Fields for MS Word
The Merge Fields feature allows the use of Vault tokens in MS Word documents (DOCX format only). Vault then replaces the tokens with data from the associated document and object fields. For example, a title page can now include the name of the document as stored in Vault. Subsequent updates to the Vault fields or document content will trigger a re-synchronization between the source file and field values. This new feature saves users time and eliminates inconsistencies between source files and Vault fields.
To enable, Admins apply the new Merge Fields shared field to any document types that need to use the feature. Learn more.
Expected Document Lists for eTMF
This exciting new feature enables customers to measure the completeness of projects like clinical studies. The feature includes a core object model and batch matching job. The data model represents lists of documents that need to be collected for a given project (studies, etc.). A batch job can match documents with the data model and provide a status for each expected document of Completed, In Progress or Not Started. This batch job provides an efficient and hassle-free way of managing completeness.
This feature also includes functionality to support eTMF-specific use cases:
Users can bulk create expected document lists (EDLs) for all study countries and sites within a study.
Users can bulk update the “requiredness” and “number of expected documents” settings across EDL items within the same study country or study site.
Conditional Report Fields
With conditional report fields, report creators can categorize data in a more meaningful way. This feature allows users to create a field where categories use conditional expressions to determine whether they apply to each report row.
For example, a user could group a report by Document Status with a conditional field that shows a category labeled “Not Started” for Draft state documents, another labeled “Finished” for Approved state documents, and a third labeled “In Progress” for documents in every other state.
Conditional fields can then group data into these categories. In the current release, conditional fields are available only for the new document relationship report types, but this feature will support other report types in a future release.
Conditional fields can also be used in dashboards to visually indicate the distribution of data between categories.
Document Relationship Report Types
Document relationship report types enable organizations to measure content reuse, as well as which documents are used most widely to support other documents. These reports can show information about the source document, target document, and the relationship itself.
Report Types
This feature includes new standard report types, which make it easy to report on Based On and Supporting Document relationships:
Original with Copy
Copy with Original
Supported Document with Supporting Document
Supporting Document with Supported Document
Users can repurpose these report types to report on other types of relationships. To do so, users must edit the default Alias values and Relationship Type filter when creating a report using one of the above report types. The Alias values and Relationship Type filter they set should reflect the relationship type they wish to view.
Field-to-Field Filters
Using new field-to-field filters, this feature can select related documents that are similar or different in an important way. For example, a user could select documents where the original has one Country value and copies have a different Country value.
Aliases
Reports that use the new report types also support custom Alias values that allow the report creators to name each side of the relationship in a way that is meaningful to their users. For example, in a report that shows global documents with country-specific copies, aliases could label the original as “Global Document” and the copy as “Local Document.”
Aliases appear in filter labels and column headings within the report.
Smart Filters on Search Bar
Smart Filters detect when terms or phrases in a search match certain metadata values and automatically convert the search terms into filters. This enhancement allows users to quickly navigate to set of documents simply by searching for core metadata values like Promotional Pieces Approved for Use, which will filter on document type and status.
Combinations of filters and text searches can also help find documents quickly. If I need a document called “Screening Form” on a specific study site called “A-123”, I can type “Screening Form A-123” so Vault will filter on site and search for the terms “Screening Form”.
Smart Filters apply to the following fields:
Document Type
Sub-Type
Classification
Document Status
Product
Country
Study > Study Country > Site (eTMF only)
Learn more.
Drag & Drop for Document Creation & Versioning in Binders
Users can now more quickly create new documents and upload new versions to existing documents by dragging and dropping files into a binder. Drag and drop a single file onto an existing document or placeholder to upload a new version. Drag and drop one or more files onto a binder section to create new documents and add them to the binder section. We’ve also updated the Back to binder links to work more consistently after viewing a document from within the binder. Learn more.
Like past drag and drop features, users who access Vault using older versions of Internet Explorer will not have access to this functionality.
Spreadsheet-Style Editing for Object Records
In this release, we’ve introduced the ability to edit values inline on object list pages’ grids. With inline editing, users can use Microsoft Excel-like keyboard shortcuts and mouse clicks to easily traverse and modify data. This will allow users to more efficiently work with large amounts of information stored in object records. Learn more.
Include Versions in Binder Export
This release enhances asynchronous binder export by adding the ability to specify which versions of selected documents to include in the export. Users can elect to export all major versions, all major and minor versions, or only the versions dictated by the binder’s version binding rules at the time of export. For study sponsors, CROs, or other key stakeholders needing to provide more information about documents in a publishing or handover phase, this ability to specify versions to export provides a more complete view of the binder and its contents. Learn more.
Vault-Specific Delegation
In past releases, delegating your account access to another user (in a multi-vault domain) granted access to all of your vaults.
Improved Process
This release improves the delegation process:
Admins can enable or disable delegated access for individual vaults.
When users delegate access to another user, that user only gains access to the current vault.
A user can now delegate access to up to 25 users, rather than just one.
Enablement
In vaults that currently use delegated access, this feature will be available automatically for the V14.0.1 release. Existing delegations will continue to work in most cases, but will exist as individual delegation rules for each vault, rather than across vaults. For example, Thomas delegated his account (with PromoMats, MedComms, and Submissions vaults) to Gladys. Gladys only has access (through her account) to PromoMats and MedComms vaults. In the previous version, Thomas’ delegation would be a single rule and would give Gladys access to all three vaults. In this version, the system has migrated the existing delegation to the PromoMats and MedComms vaults, but has not migrated it to the Submissions vault because Gladys doesn’t have access there.
UI Updates
When this feature is enabled for a vault, there are several UI enhancements that users will see:
Styling in the User Profile page is slightly different.
The User Profile page provides a set of links along the right-hand side where users can jump directly to a specific section of the page.
In Admin > Users & Groups > Users, the user details page includes a new Delegate Access tab.
The new Active Delegations page (Admin > Users & Groups) shows all delegation rules that are currently active within a vault.
System-Managed Object Record Names
Admins can now choose to have the Name field managed by the system, so users do not need to enter a name value for each record. The automatically-generated name can have specified text and an incrementing number. For example, “VEEV-0009876” would be generated by VEEV-{#######}. Learn more.
Referenced Object Filter
Admins can now define a filter on object reference fields, limiting the records to a more relevant or valid list from which users can select. For example, an Admin could limit references to only Product records that have Product Status set to Available.
Referenced object filters also allows Admins to create a single object as a master list of values, consolidating references to a single object, rather than creating many similar objects. Various object reference fields in different objects can reference this same object, and each field can be filtered to allow users to only select the relevant records. Learn more.
Advanced Overlays with Custom XFA Templates
This release will allow customers to get more out of Vault overlays. Building on the changes implemented for advanced eSignature templates, Admins can now configure overlays to show document content anywhere on a document page, in any format, with wrapping, truncation, or shrink-to-fit rules as required by business needs. Vault matches page size and orientation on a per-page basis (within a single document) using the various templates that Admins provide. If a page has no matching overlay template override file, Vault will default to the ‘simple’ overlay definition, meaning there is no risk of content leaving the vault unmarked. Customers who add advanced overlays to their vaults will experience some extra preparation time per document as Vault renders and applies those overlay templates throughout downloaded content.
For users who need it, an example XFA overlay file is available. Learn more.
Advanced Workflow Role Configuration
With Advanced Workflow Role Configuration, you can now define a set of business rules to determine which roles are required, optional, or hidden on the workflow start dialog. As you expand your vault usage to new product lines and markets, compliance requirements across products/markets can vary. Instead of creating a separate workflow per product/market, with this new feature, you can simply define a set of rules that controls whether a role in a workflow is required, optional, or hidden on the workflow start dialog for a particular document, based on its metadata. Learn more.
Hierarchical Copy for Object Records
In this release, users can copy an existing object record. If configured, users can also choose to copy a hierarchy of child and grandchild records. This provides significant time savings. In some cases, hundreds of child and grandchild records are automatically copied rather than individually created.
Simple “shallow” copy actions are automatically available on all vaults. However, hierarchical or “deep” copy must be individually enabled on specific child objects via the Parent Object-type field. Learn more.
Lookup Field Type
Admins can use this new feature to specify fields from a parent or referenced object that should appear in the context of a related object, allowing users to view additional relevant information in reports, object list pages, and object detail pages. For example, Admins could create a lookup type field on the Marketing Campaign object, which pulls in the Therapeutic Area field from the related product. By providing information from related objects in another context, users won’t need to click back and forth to get all the details they need.
Reusable Picklists
Picklists can now be reused across multiple object and document fields. This enhancement allows an Admin to manage a single list of values (picklist) and have this utilized by multiple fields. There are no steps required to make a picklist reusable. When Admins create a new picklist-type field, they’ll simply have the option of using an existing picklist or creating a new one. Learn more.
Vault Loader Extracts for Users, Groups, Document Versions, Source Files & Renditions
Organizations can now use Vault Loader to extract:
Users
Groups
Document version metadata
Document renditions
Documents source files
Vault holds extracted files on the vault’s FTP server, where users can download them using an FTP client like FileZilla, FireFTP, etc., as long as they have appropriate FTP permissions to download. Note that Vault will periodically delete old files from the FTP server. Learn more.
Vault Loader: Single CSV Loading for Documents, Versions & Roles
Users can now employ a single CSV file to create documents, assign users/groups to roles, and create document versions. This enhancement streamlines the document creation process via Vault Loader. Learn more.
Role-Based Color Coding for Annotation Notes
This enhancement allows Admins to assign a note color to any lifecycle role. The assigned color is then enforced when a user adds a note or reply while completing a workflow task. The assigned color is only enforced when the user has one or more tasks utilizing the same role. It is not applied when a user has no tasks or has multiple tasks that use multiple roles. Learn more.
Vault to Vault Migration of Multichannel Content
With this feature, users can copy a multichannel presentation and all of its slides (including sub presentations and shared resources) from one vault to another. If the content already exists in the target vault, the system will version the existing documents, rather than creating duplicates.
To configure, Admins can set up the Copy to Another Vault user action for various lifecycle states. This action first validates the source presentation to ensure that it meets a set of requirements for copying, for example, any referenced objects have an External ID specified. Once validated, the user must provide login information for the vault to which they are copying. A second round of validation then ensures that the presentation meets the target vault’s requirements, for example, all required fields are populated.
After validation, Vault displays a summary screen to confirm all of the proposed changes to the target vault. This summary allows users to identify the documents that the action will create or version, as well as displaying warnings. When the copy action is complete, the initiating user receives an email notification. The new Source Vault Link document field lets users see where copied documents originated.
CRM Publishing for Approved Email
For customers using Approved Email integration, we’re introducing the ability to trigger integration sync directly from Vault. This feature allows users to quickly trigger an ad-hoc sync instead of waiting for the scheduled process to run, or requesting someone with access to CRM manually trigger a sync. The items listed below will be available beginning in 13.5.4, but the full functionality will not become available until Veeva CRM V26.
To support triggering the CRM sync process from Vault, we’ve introduced a new object (CRM Org) and a new tab (CRM Publishing). The new tab allows users to trigger a sync action.
The new Multichannel Loader permission will control visibility to the CRM Publishing tab.
Vaults which have the CLM or Engage Integration enabled and already have the CRM Org object will see a new Approved Email picklist option on the Integrations field. Learn more.
CLM Integration Preview
With this feature, users can preview CLM content stored in their vaults from a browser, instead of having to sync the content to a mobile device. Content rendering will depend on how the HTML content was created. Because of browser limitations, some CLM content will not render accurately. Customers should evaluate this feature with their content before enabling it for all users.
When users access the preview action on a document with new or updated content, Vault sends the distribution package to a content distribution network in a format that can be rendered in a browser. This process can take some time, so Vault notifies the user when it’s complete. This notification includes a link to open preview the content. Subsequent preview actions for the same content will open the preview in a new browser window.
Because of browser limitations, some CLM content will not render accurately within a browser. Customers should evaluate this feature with their content before enabling it for all users.
Event Management Approved Email Integration
In vaults that use the new Event Management Approved Email Integration, users have access to new picklist values, fields, and objects that support the integration.
Document Fields: Event Topic, Template Subtype, Event Type
Objects: Event Topic
Picklist Values: Events Management Invite Template option in the Email Template Type field
Include Audit Trail in Binder Export
This release enhances the new asynchronous binder export functionality by adding the ability to include document audit trails in the binder export. For study sponsors, CROs or other key stakeholders needing to provide more information about documents in a publishing or handover phase, this ability to include audit trails lets those stakeholders see a more complete view of the binder and its contents. Learn more.
New Sharing Settings Panel & Details Page
This release updates the Sharing Settings panel in the Doc Info page:
Adding a user or group to a role on a specific document now takes fewer clicks.
It’s now possible to assign a user directly to the Owner and Coordinator roles, rather than assigning to another role and then updating. The previously assigned user no longer gets reassigned to the Editor or Viewer role, but is instead removed from the document.
Users can hover over the role name to see that role’s permissions for the current lifecycle state.
Users can click into a sharing settings detail page. If the document has more than ten (10) role assignments, the full list is only visible on the detail page. The detail page also shows whether a user or group was assigned to a role through DAC or manual assignment.
On the sharing settings detail page, users can search for a user to get a list of all roles the user has on the document, both directly and via membership in groups.
When using DAC for documents, a notice shows on the sharing settings detail page if the current role assignments are out-of-date because the vault is reindexing.
No Markup Option for MS Word Renditions
With this release, Admins can default all new auto-generated viewable renditions for MS Word source files to display “No Markup.” This feature introduces the new Do not show Markup in Viewable Renditions for Word documents setting in Admin > Settings > Rendition Settings. Learn more.
Reports on Object Lifecycle States
In V13, Vault introduced support for lifecycles on objects. In this release, object lifecycle attributes are available to use in reports. Reports that include objects with lifecycles now support grouping and filtering on the State attribute.
Dashboards will also support object state as a category for charts. If Admins have associated specific colors with states via the Lifecycle State Colors configuration page, these color choices also apply to object lifecycle states displayed in dashboard charts.
Object Counts as Calculated Fields in Tabular Reports
All tabular reports can now include a calculated field for each report object that shows a distinct record count. Users can add these fields as report columns and sum them like other numeric fields into groups. In addition to providing more detailed information about the total records for each object in the report, the new calculated fields make it easier to read group totals. Learn more.
Show Related Records in Custom Tab
In this release, the object record detail pages now provide a Show in Tab link for related object lists. By clicking this, a user can open the list of related children or complex joins in a custom tab. From this custom tab, users can further filter, export, or save the list as a custom saved view. Note that a custom tab must exist for the object in order for users to see the Show in Tab link.
Clickable URL Links
Vault can now display URLs within a text field as clickable links. This functionality is available in object list pages, object detail pages, and report results. In the current release, it is not available in the Doc Info page or in document views. When a user clicks the link, a new tab opens to display the linked resource. Learn more.
Permission Set Control for Accessing Tabs
This release adds an additional security option to control which tabs (Home, Library, etc.) certain users can access via permission sets. Organizations can now limit tabs intended for specific business functions to only those business users. This enhancement improves access control and provides the ability to simplify each user’s interface, so everyone sees only the tabs relevant to them. Learn more.
Advanced Re-Render
In this release, we’ve enhanced the Re-Render action to give users the option to select from a list of common viewer and rendering issues. This self-guided troubleshooting provides information that assists Vault in resolving the issue as well as generating a more accurate rendition. Users can also utilize the new Preserve Annotations option when they re-render.
Job Scheduler Support for Calling to External URLs
Vault Admins can now leverage the job scheduler to help synchronize external systems and integrations. This new job type allows Vault to reach out to any HTTPS URL with vault-specific information and log the type of response received, on a repeating schedule. Admins can use this to link up to external services within their compliance landscape, ensuring that disparate systems are kept in sync and that there is evidence of that synchronization within the vault itself. Like other jobs, jobs of this type log when they execute, what executes, and details on the response received from the remote host. These jobs can run with a specific user’s login identity, such that any integrating services could execute changes in the vault as that user, but would have the same level of access as that user. Learn more.
Vault Loader: Job Status Visibility in Operations Tab
Along with notifications, users can now also check on the status of their Vault Loader jobs from the Admin > Operations tab. The Job Status page displays specific details on the loader job’s status and allows users to download job results. Learn more.
Study Startup Enablement
This release introduces Study Startup (SSU) support to get your study to first patient, first visit faster. Study Startup, available as an add-on to Vault eTMF, adds two standard document types to eTMF. One supports the creation of SSU business process artifacts that are not filed into the TMF, such as contract and budget template files. The other, Study Startup Document Packages, supports the creation of binders for tracking key study documents, country adaptations/translations, regulatory and ethics filings at country and site levels, and site-essential document collection progress.
SSU submissions heavily reuse key study and study country documents. Rather than having to manually add the protocol to hundreds of site submission packages, SSU’s auto-population rules locate the study- or study country-specific version and add it. This single source of truth for key clinical documents empowers your teams’ line of sight, highlighting all affected submissions and making it easy to identify bottlenecks. All binders with the Study Startup Document Packages document type, its subtypes, or its classifications will support SSU’s nearest match auto-population rules. Learn more.
RIM Updates: Submission Import via ZIP and TAR.GZ
SubmissionsArchive users can now import compressed submission packages (ZIP and TAR.GZ) through the Vault UI instead of pre-loading them on the vault’s FTP. These single submission packages should reflect the structure as it was submitted to the health authority. Packages larger than 4GB should be placed on the Vault FTP site for import. Learn more.
RIM Updates: EU eCTD Module 1 Support
SubmissionsArchive users can now import European eCTD submissions created with DTD version 1.4 and 2.0. Learn more.
RIM: Bulk Create Planned Registrations
This enhancement allows users to quickly create Registration records based on the data defined in the Application and Submission records, ensuring quick, easy, and consistent data entry. Vault Registrations ensures that each product detail variation results in a unique registration, which facilitates tracking and management at a very granular level. This feature is especially important for grouped markets such as the European Union (EU) or Gulf Cooperation Council (GCC) where one marketing application can lead to multiple registrations across multiple countries. Learn more.
RIM: Bulk Create Activities & Submissions
This enhancement streamlines the data entry process for managing local affiliate tasks associated with a global regulatory change event. By allowing bulk creation of activity and submission records, Vault minimizes local data entry, reducing the risk of incorrect data entry or lack of centralized visibility. The bulk create wizard prompts the user for required metadata and associates all new records with the appropriate event and/or application. Newly created records are immediately reportable for central team visibility. Learn more.
RIM: Registrations Impact Assessment Report
The Impact Assessment Report allows regulatory affairs professionals to understand the global impact of any planned changes to the registered product details. Users can access this new one-click report from any Event record in their vault to get an at-a-glance understanding of the effort needed to implement a change in multiple markets. This report gives insight into marketed, approved, and planned registrations globally that share common information with the affected product details of a planned event. Learn more.
Support for Multiple SAML SSO Profiles per Domain
This release adds support for multiple single sign-on profiles, extending the capabilities of Vault to support complex identity management requirements within an organization. Alongside this feature, Vault now simplifies the configuration and management of SSO by externalizing the service provider metadata and allowing import of metadata from the identity providers. Learn more.
Adjustable Columns & Hover Card in Document Packages UI
The Send Document Package page now allows users to resize columns in the Step 1 section and can display a hover card with details for the documents in this section.
Expose “Grant Access to Veeva Support” to All Users
In Q1 2016, for PromoMats customers only, users will have access to a new first-line support service: the Global Service Center. As part of this effort, we’ve added an option on the User Profile page that enables PromoMats users to grant Global Service Associates access to their profiles in order to provide quick and effective resolutions to the user’s issues. An Admin must enable the feature before users can see the Grant Access to Veeva Support area on their User Profile page. The feature is off by default.
This enhancement also includes minor visual updates to the Grant Access menus.
Removal of Distribution History Report
In PromoMats, the Distribution History Report is tied to the standard Distribute and Withdraw workflows previously delivered with the application. In recent releases, we’ve updated these workflows to take advantage of the latest workflow features. As a result, Vault will remove the outdated Distribution History Report in this release. To see the same workflow and task details, users can click View Workflow History Report from a document’s timeline view.
Multichannel Loader Enhancements
Multichannel Loader now allows users to upload non-ZIP files as multichannel slides and utilizes Vault’s auto-packaging features to generate distribution package ZIP files. This feature also makes it possible for users to trigger the Create Presentation action for multiple documents at once.
Delete Access on System-Owned Custom Views
The Make Mandatory permission (via permission sets) now allows users to delete any system-owned custom views created during vault cloning.
Standard Views Accessible on Search Dialogs
Users can now access standard document views when adding documents to binders, linking documents in relationships, or creating anchors. Each of these search dialogs has an option to view Recent Documents, My Documents, and Favorites.
Revised Document Viewer Options in Doc Info Page
In this release, we’ve improved various options in the Doc Info page’s document viewer:
Users have greater visibility and one-click access to bookmarks via a new button on the toolbar, which opens a new bookmarks panel that provides easier bookmark navigation. Learn more.
We’ve moved the rotate actions from the Options menu to a single button on the toolbar. This button rotates the selected page 90 degrees clockwise (right) each time the user clicks. The rotate action is disabled in Notes and Thumbnail views.
The Find in Document function has moved from the Options menu to a button on the toolbar.
We’ve eliminated the Options menu.
Better Visibility into Tasks Completed by Delegates
This release provides customers with greater transparency for identifying when tasks are completed by delegates, as opposed to the task owner. When a delegate completes a task for another user, the delegate’s username will now appear, in addition to the task owner’s username, in relevant places, including Timeline View and the Active Workflows screen. Workflow History reports will provide this information in an optional Task Completed By column.
Stay on Detail Page after New Record Creation
After saving a new object record, users stay on the detail page instead of returning automatically to the list page. This change makes record creation easier for users who need to add record details that are not available during the initial creation.
Make a Copy Support for Planned Documents
The feature allows users to quickly create placeholders of the same type with fewer clicks. It is common to collect multiple documents of the same type for a given site, for example, investigators participating in a study will need to submit their CVs and medical licenses. This reduces the time required to create placeholders and enhances usability.
Optional Task Display Configuration Control
With this new feature, Vault Admins have better control over how roles with optional tasks should display on the workflow start dialog. Previously, when a workflow had a role with only optional tasks, the start dialog assumed someone would be assigned to those optional tasks, and prompted the workflow owner to provide task assignees as if the tasks were required, unless the workflow owner intentionally opted out of assigning anyone. With the new Workflow owners opt-in to assign optional-task roles option in Admin > Settings > General Settings, Admins can instruct Vault to assume that roles with only optional tasks are not needed by default. The workflow owner won’t need to assign any users or groups to a role if the role only has optional tasks.