1. Veeva Commercial Vault 19R2 Deep Dive
MedComms Focused
July 2019

2. Auto-On Features

3. Back to Vault from 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
Clicking on the dropdown reveals an option to return to your Vault
Clicking on the MedComms logo from the Portal Selector page will bring users back to Vault

4. Back to Vault from Medical Portal
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)

5. 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

6. 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 Deleted state, it will only be accessible to Vault Owners
Configuration
Admin > Configuration > Document Lifecycles
Learn more about Document State Types
New Deleted state

7. 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
Impact
Improve user experience and automate 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.

8. Vault File Manager Enhancements
When a user checks out a file to Vault File Manager, the file will automatically open after it has finished downloading
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
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
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

9. Vault File Manager Enhancements
Checking out to Vault File Manager automatically downloads and opens the file
Ability to undo check out from the Vault File Manager desktop application

10. Vault File Manager Enhancements
Check in from Vault a file that was checked out to Vault File Manager
The local file is checked in after you enter the version description and the Vault File Manager refreshed

11. 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

12. 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

13. 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)

14. 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

15. Admin Features

16. 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

17. 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

18. 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

19. 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]

20. Configurable Features

21. 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

22. Multi-Pass Reporting Configuration
Report View - Admin > Configuration > Report Views .

23. Multi-Pass Reporting Configuration
Report Types - Admin > Configuration > Report Types > [Create Report Type]
Create the Report by selecting the newly-created report type and click Continue
Click “Create”, select “Multi-Pass” from the Class dropdown, and select the appropriate relationships using the available Report Views and Save

24. 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

25. 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

26. 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

27. 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

28. 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
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 timezone
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
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
The Weekday Function can inform users what day of the week a date or datetime is
Use Case
Users can use the Weekday Function to set a date to 30 days from now but ensure the day is a weekday on an object in PromoMats

29. Weekday Function and DateValue Enhancement
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
Examples
DateValue() is used when comparing a Date to a DateTime and you want to be specific about what value is used for the DateTime to Date conversion. This allows for the server or user time zone to be specified
Today("user") -

30. 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

31. 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

32. 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)

33. 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

34. 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
Select the lifecycle applicable to the Multi Document Workflow
Prior to 19R2 Multi-document workflows didn’t allow lifecycle choices

35. Multi-Document Workflow: Support Specific Lifecycle Configuration
Impact
Allows for documents to be sent through Multi-Document Workflows which require lifecycle-specific elements
Use Case
A large amount of training material is coming up for review and needs to have new expiration dates set
These can be sent through a Multi-Document Workflow created for that specific Field Medical Lifecycle
Considerations
This capability will be available in all Vaults
Configuration
Admin > Configuration > Multi-Document Workflows
Learn more about Configuring Multi-Document Workflows

36. 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 or task owner to enter an expiration date and this will be propagated across all content in the 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

37. Multi-Document Workflow: Prompt for Fields on Start Step & Task Step
Configuration
Admin > Configuration > Multi-Document Workflows >[Multi-Document Workflow or Create New]
Fields can be made required or optional
Prompt for Document Fields

38. 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
Update document shared fields in a Content Action step, this enables workflows to set document fields
Use document fields in conditions in a Content Action step, this enables workflows to perform actions on a document only if the condition is true
Use Case
There is a large amount of training material to review and update. Using a Content Action the Admin may choose to update certain fields based on criteria defined in the workflow.
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’

39. 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
Select the actions to update document field, confirm document field and set a value e.g. Today()
Available fields are:
Dependent on the lifecycle
Non-shared

40. Multi-Document Workflow: Enhanced Document Timeline View & Audit
Overview
In multi-document workflows, the document timeline view now displays workflow and task instances from where users can: view timeline and audit history, add, replace and participants, cancel workflows and 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
Workflow tasks now available for Multi-Document workflows from Action Toolbar

41. MedComms Focused Objects

42. 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
Related Object example:
When a user creates a record the Create Record Pop-up Dialog opens
Case Object Page Layout – edit Case Request Object

43. Create Records in Pop-up Dialog
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 (Related Object Section)
Admin > Configuration > Objects > [Object] > Page Layouts > [Layout] > Create New Related Object Section or Edit Related Object Section
Configuration (Custom Tab)
Admin > Configuration > Tabs > [Object] > Enable Create records in pop-up dialog

44. Dependent Picklists for Objects
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
Anytime you want to limit the choices of a picklist based on a controlling picklist
Request Category and Request Sub-Category
Region and Locale
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

45. Dependent Picklists for Objects
Configuration
Admin > Configuration > Objects >[Object] > Fields > [Picklist field]
Click on Create Dependencies
Select the controlling field
Select the values and choose save

47. Appendix

48. General Updates Add Event Description to Audit Exports
The Event Description field will now be included in the export of an Audit Trail
Show Family Name in Domain Information
When viewing Domain Information, a Domain Admin will now see the application family name, rather than the application name
Ex: ‘Commercial’ will display for all PromoMats and MedComms Vaults
Data Model Changes for User Role Setup Source
Introduces ‘Source’ picklist and ‘Source Reference’ text field on objects with the User Role Setup class
Both fields are optional and non-editable
Future releases will use these fields to track origination of User Role Setup records
New Supported Component Types
Document Lifecycle Stage Group*
Object Lifecycle Stage Group*
*Both are supported for Configuration Migration, Configuration Reports and Vault Compare
Details for document workflow steps will now be included in the Vault Compare and Configuration Report
Scalable FTP
An upgraded Vault FTP infrastructure that takes greater advantage of AWS™
- Improvement of the complete migration process
- Better visibility of documents being consumed
- Shortened time for documents to become usable in Vault after load

49. Vault Release Cycle – 3x per Year
2019
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
V19R2
scoping
2019 R1
2019
V20R1
scoping
V19R3 scoping
2019 R2
2019

50. Pre-Release Vaults
Validation testing for new features can be performed in Pre-Release Vault
Access to Pre-Release is limited to Vault Owners of Production Vaults and Product Support by default
Access can be requested via a Support ticket (Zendesk) via the Customer Support Portal
Pre-Release environments are available for the 4 weeks before and 4 weeks after a General Release
4 Weeks before: prepare and test
4 Week after: change control close out activities

51. VeevaDocs
Contains validation documentation for Veeva Products and Veeva Operational Reports
Organized into Binders by product and release
Access can be requested via Support ticket (Zendesk) via Customer Support Portal

52. Release Notification
Vault users that opt in via their User Profile will receive an notification about
Upcoming General Releases
Invitations to General Release overview webinars
Pre-release & validation availability
Go-live date reminders
Users that do not check the box will not be notified about upcoming General Releases

53. Notification Emails from Veeva
Opt-in to Product Announcements in User Profile to be contacted about:
Initial release announcement (RIA)
Release webinar invites
Pre-release and validation document availability
Go-live & key date reminders
Opt-in to Service Availability notifications in User Profile to be contacted about:
Planned system maintenance
Service disruptions

54. trust.veeva.com
Offers up to date information on all of Veeva Systems’ service status
Communicates known issues, current status, and incidents of service unavailability
Calendar of known maintenance windows and planned downtime
Listed by Product & POD

55. Administer Communications
Admins can manage who receives communications for each vault
Service Availability Notifications can be configured using one or both of the following methods:
1. Provide an address for an individual, or a distribution list for multiple people, in each Vault
Admin > Settings > General Settings > Service Availability Notifications
2. Enable Service Availability and Product Notifications for an individual user, or use Bulk Action to setup for multiple users at once
Admin > Business Admin > Users
Customers can report on the User object to:
Determine who opted in to Product Announcements and Service Availability notifications
Use Bulk Actions to set or remove this option for multiple Users

56. Service Announcements
Starting with 19R2, Vault will display a dismissible banner to communicate planned release downtime to all Vault users
Banner will appear 24 hours prior to the scheduled downtime 
Time will be listed in PDT with the appropriate US/EU/APAC POD timezone in parentheses
Only English is supported
If a user does not log in during the 24 hour period, the user will not see the banner

57. Objects

58. 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

59. 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

60. 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

61. 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

62. Filtering on Related Object Sections
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

63. Filtering on Related Object Sections
Configuration
Admin > Configuration > Object > [Object] > Page Layouts > [Layout] > Edit > Define Filter options

64. 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

65. 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

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

67. 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’

68. Secure Object Record Attachment
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

69. Secure Object Record Attachment
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

70. Secure Object Record Attachment
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

71. Dataset Configuration Migration Enhancements
Overview
Added support for any non-system managed unique fields as object lookup (Key Field / idParam)
Added support for Update and Delete operations
Impact
Previously, Datasets only supported a limited set of unique field lookups and custom fields were not supported
In addition, while creating Datasets in configuration migration packages there was no ability to include any update or deletion of records
Considerations
System managed / auto-generated fields cannot be used as unique lookup keys