Veeva Commercial Vault 19R2 Deep Dive

Veeva Commercial Vault 19R2 Deep Dive
IT Focused Session

FDA Final Guidance Released
On June 21, 2019 the FDA released Final Guidance for the Electronic Submission (eCTD) of Promotional Materials on 2253 Veeva is dedicated to ensuring a seamless transition to eCTD submissions for our customers By June of 2021, all customers must provide 2253 submissions electronically via the gateway

Upcoming Webinars 19R2 Developer Release Deep Dive
4 Upcoming Webinars 19R2 Developer Release Deep Dive Enhanced Checkout and Vault File Manager Thursday, July 18th at 10am ET Thursday, July 25th at 12pm ET Join Veeva Customer Success and Product teams for an education session on new features in the Veeva Vault developer-focused toolkit This webinar is geared towards current users of the Vault Developer toolkit (API) Key topics for discussion will include: Detailed explanation of new features Overview of the Spark message notification system Considerations for using new features, and impact(s) features may have on your Vault or end users Advanced registration required In 2018, Veeva announced that we will stop supporting the Enhanced Checkout Java applet in 2019 In November 2019 (19R3), Enhanced Checkout will be disabled and removed from the Veeva Vault platform Join us for an education session on Enhanced Checkout and Vault File Manager where we will discuss: Why enhanced checkout is being retired What the flow will look like once Enhanced Checkout is retired Vault File Manager benefits Advanced registration required

3rd Annual Digital Asset Management for Life Sciences Forum
Tuesday, September 10, 2019 in Philadelphia Join brand managers, marketers, digital content managers, and marketing operations professionals Register now Discover what’s new Gain actionable tips Connect with peers

Veeva Vault Fall Community Forums
Join your peers and industry experts for a half-day of networking to share industry challenges and best practices. Location/dates: Boston (Cambridge), MA: Tuesday September 17 Whippany, NJ: Thursday September 19 Wheeling, IL: Thursday September 26 Highlights include: Veeva Vault Fall Community Forums Interactive deep dives conducted by Veeva product experts Networking based on relevant business cases

Agenda 1 Auto-On Features 2 Configurable Features 3 Admin Features 4
Objects

Legend Legend Enhancement to Existing Feature Admin Configuration: Requires enablement and configuration Auto-on: Automatically available / some set-up may be required A Admin Checkbox: Requires enablement Support: Must be enabled by Veeva Support S Always refer to the latest 19R2 Release Notes and Online Documentation for the most up to date version of documentation and configuration steps Demonstrated during webinar

Auto-On Features

Back to Vault from Brand/Medical Portal
Overview Vault users viewing a Portal can now return to Vault by clicking on the dropdown on the upper-left hand corner of the Portal’s Homepage Impact Provides a more seamless experience for users, as they will no longer need to manually redirect themselves back to Vault Considerations Remember to train users on where to find the return to Vault link Relevant only to Portal users who also have access to Vault (i.e. doesn’t concern Portal-Only Users) Clicking on the dropdown reveals an option to return to your Vault Clicking on the PromoMats or MedComms logo from the Portal Selector page will bring users back to Vault

Available Tasks Visibility
Overview Previously, the Available Tasks view only appeared on a user’s Home tab if Available Tasks were configured within the Vault In this release, the Available Tasks view will now always be visible to users on the Home tab Impact Improves performance of the Home tab Considerations Users will be able to accept an available task from Home > Available Tasks Available Tasks will always now be visible to users on the Home page Available Tasks: Allows Workflow Owners to assign a task to multiple users and request that any one of the assigned users accept and complete the task

Document State Type: Deleted
Overview Introduction of a new Deleted state type in all Vaults, which can be used for Documents that are not available for use, but should not yet be fully deleted Impact Admins can now map states from specific document lifecycles to a higher level ‘type’ Provides Admins with a ’soft delete’ option Use Case A document that will no longer be used can be put into a Deleted state until the required retention period has been satisfied Considerations Once a document enters the Delete state, it will only be accessible to Vault Owners While the feature is automatically available as a Lifecyle State Type, Admin must still configure the Deleted State Learn more about Document State Types New Deleted state

Vault File Manager Enhancements
Overview In this release, we have added several Vault File Manager capabilities to enhance the user experience and automate some of the processes working with File Manager When a user checks out a file to Vault File Manager, the file will automatically open after it has finished downloading A New "Undo checkout" action for files in your Vault File Manager application This will simultaneously remove the file from Vault File Manager, and Undo Checkout in Vault Checking out to Vault File Manager automatically downloads and opens the file Check this box to permanently associate the download links with Vault File Manager Ability to undo check out from the Vault File Manager desktop application

Vault File Manager Enhancements
Overview continued You can now click Check In from the document's actions menu in Vault, and it will automatically start checking in the file from Vault File Manager in the background Impact Improved user experience and automates manual processes whilst checking in / out documents with the Vault File Manager Considerations Vault File Manager is only available for Windows In 19R3 Enhanced Checkout will no longer be available. It will be replaced by Vault File Manager The Vault File Manager caters to most authentication tools and requires no user privilege to install Customers using Microsoft Azure AD to authenticate can now use Vault File Manager We have also added Custom URI support to the ‘PingFederate’ and ‘Other’ Authorization Server Provider options The local file is checked in after you enter the version description and the Vault File Manager refreshed Check in a file that was checked out to Vault File Manager In 19R3 Enhanced Checkout will no longer be available. It will be replaced by Vault File Manager. The Vault File Manager caters to most authentication tools and requires no user privilege to install.

Report UI Changes Overview Impact
The Vault Report’s user interface has been updated to include a Properties panel Impact Assists users in understanding a report’s settings Properties Panel displays: Report Type Flash Report Schedule & Associated User If Previous Versions are included If Report is Multi-Pass

Sticky Filters in Advanced Search
Overview Advanced searches now preserve any previously applied filters, allowing users to combine advanced and standard search criteria Impact Users can add or modify advanced search options without needing to reapply filters from their original search or saved view Considerations Duplicate filters have been removed from the advanced search dialog For example, the “File Format” filter is no longer displayed in the advanced search dialog because users can now apply that same filter in the standard search prior to opening the advanced search dialog

Pop Out Viewer for Document Hovercards
Overview Document hovercards that appear in the Library (tabular view), a report, or an object record now include a pop-out icon that can be clicked to open the document in mini-browser window Impact Allows you to quickly view a document without being taken away from the current page, helping to keep your place when navigating in Vault Document in Library (tabular view)

Pop Out Viewer for Document Hovercards
Considerations When you click another document hovercard pop-out icon, the current mini-browser window refreshes to display the new document Learn more about Document Hovercards Document within an Object Record Document within a Report

Configurable Features

Multi-Pass Reporting Overview Impact Considerations Use Case
Admins can now build more powerful reports by joining data from up to five (5) reports Impact Allows a single report to provide information that would previously require multiple reports Use Case Allows users to see Document information along with Created By User information Considerations Report Views are used to construct Multi-Pass reports Admins must create a corresponding Report View before creating the Report Type Report Views do not support prompts, groups, conditional fields, flash reports, or dashboards Filter conditions will not show when you run the report but will be applied Report Types are limited to Object and Object with Document Reports are matched on related object fields or object reference fields

Multi-Pass Reporting Configuration
Report View - Admin > Configuration > Report Views > [Create Report View] Click “Create” and determine the report view needed, add appropriate filters, and edit columns to include needed information and Save

Multi-Pass Reporting Configuration
Report Types - Admin > Configuration > Report Types > [Create Report Type] Click “Create”, select “Multi-Pass” from the Class dropdown, and select the appropriate relationships using the available Report Views and Save

Multi-Pass Reporting Running the Multi-Pass Report
Run report and it will contain previously created filters and columns. You can filter information further by adding filters to the report as needed Create the Report by selecting the newly-created report type and click Continue

Document with Created By User Report Type
Overview This new report type allows users to create reports which include both document information and information about the user who created the document Edit and change Status from Disabled to Active Once the report type is active, the ability to create the report will be available

Document with Created By User Report Type
Impact Allows users to see Document information along with Created By User information Considerations The new report type “Document with Created By User” is automatically provisioned (but Inactive) under Report Types This report is part of the Multi-Pass reporting Class type Configuration Admin > Settings > Configuration > Report Types

Vault replaces tokens with Field Values by auto-filling upon upload
Merge Fields for Excel Overview The Merge Fields feature is now available to use within a Microsoft Excel™ (XLSX only) source file This feature allows Vault to find tokens within an XLSX source file and replace them with values from Vault document fields Field merging enables template creation by auto-filling details like Product Name, Document Status, and Version Date Impact When Vault replaces tokens with field values, the system saves the updated version as the source file and if a user downloads the source file, they see the Vault field values rather than the tokens For backup purposes, Vault store the original uploaded source file without any modifications Use Case This feature provides customers with an automated, flexible, time saving solution when assembling content for publishing, that limits the risk of inaccuracies putting their documents out of compliance Vault looks within the uploaded file for text that matches this pattern Vault replaces tokens with Field Values by auto-filling upon upload

Add the Merge Fields shared Document Field to your Document Type
Merge Fields for Excel Considerations Merge Fields as a Shared Field should be added to your Document Type in Vault Tokens for a multi-select object reference field or for fields on that object, the process creates a comma-separated list in the cell Does not support Merge Fields barcodes and Merge Fields filtering Configuration Admin > Configuration > Document Fields Add the Merge Fields shared Document Field to your Document Type

Set Binder Content Version Binding to Steady State Entry Action
Overview This feature uses an entry action to automatically set binding rules for binder content to bind to the latest Steady State version Note that documents that are “Approved for Use” are bound to their latest Steady State and “Draft” documents are not

Impact The entry action will attempt to bind to the latest steady state version if it exists Use Case This feature can to be used to ensure that compliance package content is bound to the latest Steady state before going on to an approval cycle Considerations Feature not available in MedComms, PromoMats only Content that is not in a Steady State will not be bound Document types must have a Binder Lifecycle associated with it (Admin > Document Type > Edit Details > Available Lifecycles > Binder Lifecycle)

Configuration Admin > Configuration > Document Lifecycles > Binder Lifecycle > States > [State] > Entry Actions > Set Binder Content Version Binding to Steady State

Configurable Tab Filters
Overview Admins now have the ability set filters on custom document and object tabs Impact Allows a narrower set of documents or records to be displayed Use Case Quickly see a list of users who have logged in within a specified timeframe Only display documents, within a specified document type, that are in an Approved state > Configuration > Tabs > Edit 90 Day Expiration – Promotional tab

Configurable Tab Filters
Considerations Admin configured filters are not visible to the end user Admins can configure up to five (5) filters Contact Veeva Support to add additional filters To view or configure, you must have a security profile that grants the correct Admin: Tabs permissions Configuration Admin > Configuration > Tabs Use the +/- signs to add/remove filters Operators will vary based on selected field 3. Select filter criteria 1. Select tab type: Document or Object 2. Select Document Type or Object 4. Select operator Note: Operators will vary based on selected field 5. Select attributes Note: When available, click on the binoculars to to open a search dialog

Lifecycle Stages Overview Impact
This features makes it easier for a user to clearly identify which steps of a document or object record have been completed and which remain outstanding, when moving through a lifecycle Impact Allows Admins to group document and object lifecycle states into systematic stages Colour coding to represent whether a stage is completed (green), in progress (blue), or upcoming (grey)

Lifecycle Stages Considerations Configuration
Admins can configure up to ten (10) stages per document or object lifecycle Lifecycle Stages should be configured to reflect business logic Admins should not configure workflows, entry criteria, or other business logic based on Lifecycle Stages Configuration Document lifecycles: Admin > Configuration > Document Lifecycle Stage Groups Admins will also need to ensure document users have the following object permissions selected: Document Lifecycle Stage Label Document Lifecycle State-Stage Object Lifecycle Stage Label Object Lifecycle State-Stage Learn more about Lifecycle Stages States to the stage

Multi-Document Workflow: Support Specific Lifecycle Configuration
Overview Admins can now create Multi-Document Workflows that are only available for a specific lifecycle Fields from all document types associated with the lifecycle are available State change actions within these workflows can also use lifecycle states, rather than state types In these workflows, Admins can: Use a broader set of document fields to configure workflow updates Prompt users for field values Impact Allows for documents to be sent through Multi-Document Workflows which require lifecycle-specific elements Use Case A large number of photographs are loaded into Vault and require the Librarian to provide the rights data associated. These can be sent through a Multi-Document Workflow created for that specific Components Lifecycle

Multi-Document Workflow: Support Specific Lifecycle Configuration
Considerations This capability will be available in all Vaults Configuration Admin > Configuration > Multi-Document Workflows Learn more about Configuring Multi-Document Workflows Select the lifecycle applicable to the Multi Document Workflow

Multi-Document Workflow: Prompt for Fields on Start Step & Task Step
Overview Admins can now configure Multi-Document Workflows to prompt workflow initiators or tasks owners for field values Entered values will then populate across all documents included in the Multi-Document Workflow Impact Streamlines the completion of document information by populating data entered at prompts across all documents included in the workflow Use Case Admins can configure the workflow to prompt the workflow initiator to enter the Planned Publication Date when documents enter the approval workflow Considerations This feature works with cross-lifecycle workflows as well as single-lifecycle workflows With cross-lifecycle workflows, only fields associated with Base Document are available

Multi-Document Workflow: Prompt for Fields on Start Step & Task Step
Configuration Admin > Configuration > Multi-Document Workflows >[Multi-Document Workflow or Create New] Select ‘Prompt for Document Fields’ Select those fields of which are required Select Multi-Document Workflow

Multi-Document Workflow: Enhanced Support for Document Fields
Overview Admins are now able to configure Multi-Document Workflows to: Update non-shared document fields in a Content Action step Use document fields in conditions in a Content Action step This enables workflows to set document fields, for example Effective Date fields as well as perform actions on a document only if the condition is true Impact Automates the completion of certain document information across the all Documents within the Multi-Document Workflow Use Case A large number of photographs are loaded into Vault and require the Librarian to provide the rights data associated. These can be sent through a Multi-Document Workflow created for that specific Components Lifecycle and prior to the Librarian receiving the documents certain fields can be auto-populated based on the conditions met Considerations The document fields that will be available to update are dependent on the Multi-Document Workflow’s lifecycle The Content Action step can either ‘Always’ perform or ‘Perform with conditions’

Multi-Document Workflow: Enhanced Support for Document Fields
Configuration Admin > Configuration > Multi-Document Workflows ‘Create Step’ within the Multi-Document Workflow and Select ‘Content Action’ as the Type Select ‘Perform with Conditions’ and provide conditions Available fields are: Dependent on the lifecycle Non-shared Select the actions to update document field, confirm document field and set a value e.g. Today()

Multi-Document Workflow: Enhanced Document Timeline View & Audit
Overview The multi-document workflows timeline view and the document timeline view now displays workflow and task instances from where users can: cancel workflows and cancel tasks The document audit trail now also captures all workflow and task events Impact Uniformity between multi and single-document workflows providing a more consistent and better end user experience Considerations Prior to this enhancement, the object record audit trail captured all workflow and task events for multi-document workflows

Admin Features

Weekday Function and DateValue Enhancement
Overview This feature adds support for the Weekday() function in Vault formulas and allows the DateValue() function to accept an optional time zone parameter Weekday() function is a new feature that takes either a Date or DateTime field and returns the day of the week as a number. The number 1 represents Sunday and 7 represents Saturday DateValue is an existing function that converts a DateTime to a Date but has been enhanced, so that it now accepts a second optional parameter – the time zone Example: Today("user") - Impact By passing a time zone parameter to DateValue function, users are able to decide whether the returned date should be based on the user’s local time zone or a different time zone, instead of always defaulting to Vault time zone Considerations This is only available as a formula field for objects, validation rules and field defaults This is not available on workflow or lifecycle formulas, nor object lifecycles

From the Configuration Report
Document Workflow Step Details in Vault Compare & Vault Configuration Report Overview In this release, the Vault Compare and Vault Configuration Report functionality will include details for Document Workflow Steps Impact Provides greater visibility into the configuration From the Configuration Report

Vault Compare Enhancements
Overview Now supports comparison of Default and Override Rules, Documents & Binder Templates, and Vault Settings Improved readability of entry criteria, entry action and user action on lifecycle states for both Document | and Object Lifecycles Impact The Vault Compare report has added enhancements to support what the Config tool was previously used for Considerations Domain settings will only be included if the user generating the comparison is a Domain Admin

Rendition Profiles Event Action
Overview A new event action, Set Rendition Profile, is available for document lifecycles that will allow Admins to configure Vault to define conditions and automatically apply a chosen rendition profile Impact Provides greater flexibility for Admins to chose the required rendition Use Case Global companies can create rendition profiles that account for double byte character sets in countries where this is required and to specify the use of that rendition Ensures the rendition shows fonts exactly as intended

Rendition Profiles Event Action
Considerations Using specific renditions for the use cases above may result in larger file sizes on renditions Can be used on the following Event Actions: Create Document, Create Draft, Create Copy Configuration Admin > Configuration > Document Lifecycles > [Lifecycle] > Event Actions > [Event Action]

Compliance Package Generation: Enforce Documents Are in a Steady State Check
Overview Performs a check to ensure that materials are in a steady state prior to executing the Create Compliance Package bulk action Impact All materials must be in a steady state or an error will be displayed and prevent the user from creating the compliance package Considerations This feature does not ensure that prescribing information referenced by materials is in a steady state forms or supplementary forms that are automatically generated will continue to be created in a Draft state Configuration Admin > Settings > Application Settings > Compliance Package Generation > Enforce Documents are in Steady State

Objects

Field Formulas allow Related Object Fields
Update Record Field & Update Related Record Field Actions Support New Fields Overview The Vault Object Lifecycle and Workflows offer two actions for updating object record fields systematically: Update Record Field Update Related Record Field These actions are available within object workflows and as lifecycle state entry actions This release also allows Admins to leverage field values on related objects Object Lifecycle State Entry Actions allows: Update Record Field Update Related Record Field Field Formulas allow Related Object Fields

Update Record Field & Update Related Record Field Actions Support New Fields
Impact Provides Admin with greater flexibility to control how and when record fields and related record fields are updated on objects Use Case The Scheduled End Date on an audit record could be calculated based on the Closure Due Date on the related Project record Configuration (object workflow step) Admin > Configuration > Object Workflows > [Workflow] > create WF step

Update Record Field & Update Related Record Field Actions Support New Fields
Configuration (object lifecycle state entry action) Admin > Configuration > Object Lifecycles > [Lifecycle] > [State] > Edit Entry Actions > create Action

Create Records in Pop-up Dialog
Overview Vault can be configured to allow the use of a pop-up dialog window when a user is creating a new object record Admin have the option to enable ‘Create records in pop-up dialog’ option when: Configuring a custom tab Configuring a related object section Custom Tab example: When a user creates a record the Custom Tab Create Record Pop-up Dialog opens The Custom Asset Request Object Tab is configured to “Create Records in Pop-up Dialog”

Overview continued Related Object Section example: Our User Object Page Layout is configured with a Related Object Section called Manager that has ‘Create Records in Pop-up Dialog’ enabled When a user creates a new record from the related object section the Create Record Pop-up Dialog opens

Impact This enhancement allows for faster record creation and provides users with a more streamlined process for related object records while viewing the parent record data Considerations The ‘Create records in pop-up dialog’ option is disabled by default on custom tabs and related object section When the ‘Create records in pop-up dialog’ option is disabled, record creation will function as it does today, with records created in a new page When the ‘Create record on New Page’ option is enabled users will now stay on the related record page Learn more about Creating Records in the Pop-Up Dialog

Configuration (Custom Tab) Admin > Configuration > Tabs > [Object] > Enable Create records in pop-up dialog

Configuration (Related Object Section) Admin > Configuration > Objects > [Object] > Page Layouts > [Layout] > Create New Related Object Section or Edit Related Object Section

Dependent Picklists for Objects
Overview Admins are now able to create a dependency between two picklists fields on the same object. This allows admin to limit the values of a picklist depending on the value of the controlling picklist Admin control Picklist Dependencies via the Dependency Matrix

Impact More control over the values a user can select and ability to map out data restriction at the outset of data entry Use Case For a congress object, one might want to limit the possible values for region and language fields depending on the region where the congress is taking place Considerations You can have multiple controlled picklists depending on the same controlling field but you can only have one controlling field for a given picklist

Configuration Admin > Configuration > Objects >[Object] > Fields > [Picklist field] Click on Create Dependencies Select the controlling field Select the values and hit save

Filtering on Related Object Sections
Overview Related object sections on Page Layouts have been enhanced to include a full set of filter options Filter List is based on the related object fields

Impact Provides Admin with greater ability to control which records are displayed in related object sections based on business requirements and processes Use Case This feature can be used in the following ways: A related record section could show only records in the Active state, filtering out Inactive records To create separate related record sections based on the related record lifecycle state: Approved state records would show in a separate section from New and In Approval records Considerations Vault will convert any existing object type filters to filters under the Filter Related List section

Configuration Admin > Configuration > Object > [Object] > Page Layouts > [Layout] > Edit > Define Filter options

Audit Trail Field-Level Security Enhancement
Overview Currently, when a user is unable to see a hidden object field due to field level security, they also cannot see any fields (hidden or unhidden) in the record’s audit trail Now, when object fields are hidden from users using field level security, they are also filtered out of the record’s audit trail This feature also filters out hidden fields on related objects Use Case An internal compliance auditor may need to run planned or ad-hoc audit reports on stored Product and related Copartner metadata. However, sensitive Copartner metadata is hidden from most internal/external users and thus needs to be filtered out of audit reports, ensuring system wide metadata security and compliance Impact Provides a more intuitive user experience when generating object record audit reports Improves the UI object compliance reporting by aligning the object security model to the Vault UI functionality Considerations This feature has no effect on document audit trails Learn more about Audit Trails

Object Field Encryption
Overview This new feature enhances the existing encryption (data is always on encrypted disks) capabilities of Vault by giving you the option to set encryption at the field level, thus encrypting the value of the field itself Impact Sensitive information can now be even more secured by encryption at field level Use Case For information that falls into the Protected Health Information section, you can now ensure those fields are encrypted Considerations You can only enable this for a maximum of 10 fields per object Vault cannot add additional encryption on system fields, formula reference fields, document reference fields, or fields that already have values Cloning and Export Package will not bring values of Encrypted Fields Patient Age and SSN are encrypted fields that are protected when Vault is accessed via VMC by Support

Object Field Encryption
Configuration Admin > Configuration > Objects >[Object] > Fields > [Field] Select whether you want the field value to be encrypted

Secure Object Record Attachment
Overview The Secure Object Record Attachment feature increases the level of control over user access to attachments Enabling this setting adds four object actions to the object: Attachments: Delete Attachments: Edit Descriptions Attachments: Upload Attachments: View and Download ‘Allow Attachments’ must be enabled to use the ‘Action Security to Control Attachments’

Overview continued These settings control access to attachments for each object record, Application Role, and object lifecycle state At the Approved state, the Editor role: Cannot see the Download button Can see the edit description icon but cannot use it Cannot see the Upload button Can see and interact with the Attachments section and view attachments in the viewer Permission Access Details Attachments: Delete: View Users can see the Delete action on an attachment but cannot use it Attachments: Delete: Execute Users can see and use the Delete action on an attachment Attachments: Edit Descriptions: View Users can see the edit description icon but cannot use it Attachments: Edit Descriptions: Execute Users can see and use the edit descriptions icon Attachments: Upload: View Users can see the Upload button in the Attachments section and the Restore action on the attachment’s version history but cannot use either Attachments: Upload: Execute Users can see and use both the Upload button in the Attachments section and the Restore action on an attachment Attachments: View and Download: View Users can see and interact with the Attachments section and view attachments in the viewer. Users cannot see the Download button Attachments: View and Download: Execute Users can see and interact with the Attachments section and view attachments in the viewer. Users can see and use the Download button

Impact Provides Admin with greater flexibility to control who, when, and how object record’s attachments are accessed and managed Use Case An internal business process, such as an Asset Request, may require approval documentation to be attached to the record for compliance practices. When the asset request is approved, users are not allowed to download, upload or delete attachments Consideration Vault secures all attachments on a specific record as a whole Vault cannot secure attachments individually Learn more about Secure Object Record Attachments

Configuration Admin > Configuration > Objects > [Object] > Edit Details > Enable Use Action Security to control attachments This checkbox is only available if the Allow attachments setting is enabled on the object first Admin > Configuration > Objects Lifecycles > [Lifecycle] > [State] > Atomic Security: Actions > Edit

Appendix

Developer

Vault Java SDK – Record Workflow Actions
Overview Customers can now extend object workflows with custom behaviors Admins can select custom actions on the workflow start step and task steps to implement custom logic Determine workflow participants, for example who will get tasks Execute custom code when tasks are created, accepted, completed, reassigned, or cancelled Impact Implement unique business logic in review and approval workflows Once you write the custom code, you will have the option to create custom actions on the object workflow or the start step within the participant’s control

Vault Java SDK – Record Action on Object Lifecycle
Overview Admins can now configure record actions to execute as object lifecycle user actions, entry actions or event actions Impact This enables customers to extend their Vaults with custom behaviors available to users on all or specific lifecycle states Supported Events Create record Copy record State change User action Once you write the custom code, you will have the option to choose the User or Entry Action from this dropdown

Management of Signing Certificates for SAML & Spark
Overview Veeva normally rolls over the signing certificates for SAML and Spark every two years. This feature will allow Vault Admins to test the new signing certificate during the rollover period. The rollover period is the time between when the new certificate becomes available and the old certificate expires. Impact A Spark connection configuration and SAML profile configuration will allow customers to test connections with new certificates before the final rollover date Configuration

Veeva Commercial Vault 19R2 Deep Dive

Similar presentations

Presentation on theme: "Veeva Commercial Vault 19R2 Deep Dive"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Veeva Commercial Vault 19R2 Deep Dive

Similar presentations

Presentation on theme: "Veeva Commercial Vault 19R2 Deep Dive"— Presentation transcript:

Similar presentations

About project

Feedback