Vault Developer Release Notes
Filters
Application Family
Tags
We are pleased to bring you the following additions and enhancements to Developer Portal features in 21R2.
Developer Features in 21R2
Section link for Developer Features in 21R2We are pleased to bring you the following additions and enhancements to Developer Portal features in 21R2. REST API features added in 21R2 only affect API v21.2, unless otherwise noted.
Service Announcements
Section link for Service AnnouncementsDeprecate Public iOS SDK
Section link for Deprecate Public iOS SDKThe Vault Mobile iOS SDK has been deprecated and will no longer be updated or made available for download. Existing solutions built using this SDK will continue to work and must be maintained by the developer.
Deprecating Vault-Wide Document Migration Mode
Section link for Deprecating Vault-Wide Document Migration ModeIn 20R2, we released the X-VaultAPI-MigrationMode API header to replace Vault-wide Document Migration Mode, which was never intended for use in live customer Vaults. In accordance with this, we’ve updated Vault Loader and Vault Certified Migration Partner tools to use the API header. In 21R2, Veeva Support will no longer enable Document Migration Mode for customers. In 21R3, we will deprecate Vault-wide Document Migration Mode completely, meaning that Vaults where Document Migration Mode is currently enabled will revert to normal behavior.
Enabling Document Migration Mode for an entire Vault has an effect on all users and prevents many Vault processes from operating. Instead, use the X-VaultAPI-MigrationMode API header with the Vault REST API’s Create Multiple Documents, Create Multiple Document Versions, Update Multiple Documents, and Add Multiple Document Renditions endpoints, or use Vault Loader with the Document Migration Mode checkbox. This minimizes risk and impact by ensuring that only the documents being created and updated in the API request are subject to migration mode limitations, and allows the rest of the Vault to be fully operational.
Access Permissions Change for Inbound Package Objects
Section link for Access Permissions Change for Inbound Package ObjectsRelease Dates:
- Limited Release Customers: 21R1.3; June 4, 2021
- General Release Customers: 21R2.0; August 6, 2021 Users now require the Migration Packages: Deploy permission in addition to object read permissions to read the following objects through the API or with VQL:
vault_package__v: Inbound Packagevault_package_data__v: Inbound Package Datavault_package_code__sys: Inbound Package Code This feature provides consistency with permissions in the Vault UI. If your integration queries these objects, you must update your integration user with the appropriate permissions. Note that Vault Owner and System Administrator security profiles are enabled with Migration Packages: Deploy permissions by default.
Global Changes
Section link for Global ChangesAdmins Can Edit All Picklist Labels & Picklist Value Labels
Section link for Admins Can Edit All Picklist Labels & Picklist Value LabelsStandard picklist labels and picklist value labels can now be updated in admin and via API and MDL.
Display the Unclassified Doc Type in Admin
Section link for Display the Unclassified Doc Type in AdminThe Unclassified document type (labeled as Undefined in previously created Vaults) is now a child of the Base Document type and visible in the Vault Admin UI. You can assign fields and document type groups to the Unclassified document types, and can also create document permissions on the document type. Note that required fields are not enforced while a document remains in the Unclassified document type (or the Inbox lifecycle).
Learn more about configuring document types in the Vault Admin UI in Vault Help
Relabel “Undefined” Document Type to “Unclassified”
Section link for Relabel “Undefined” Document Type to “Unclassified”In Vaults created after 21R2, the Undefined document type is relabeled as Unclassified. In Vaults that use Veeva Snap or custom integrations with the Vault REST API, relabeling the Undefined document type may cause errors when uploading documents. Check your integrations before updating this label. We recommend that customers experiencing errors change the label back to Undefined until this issue is resolved.
Relabel "Unclassified" Lifecycle to "Inbox"
Section link for Relabel "Unclassified" Lifecycle to "Inbox"In Vaults created after 21R2, the Unclassified document lifecycle is relabeled as Inbox. In Vaults that use Veeva Snap or custom integrations with the Vault REST API, relabeling the Unclassified document lifecycle may cause errors when uploading documents. Check your integrations before updating this label. We recommend that customers experiencing errors change the label back to Unclassified until this issue is resolved.
REST API v21.2
Section link for REST API v21.2New Endpoints
Section link for New EndpointsPromote to Production
Section link for Promote to ProductionWith this feature, Vault Admins can promote a pre-production Vault to a production Vault directly from the Vault API. This enhances the self-service model of sandboxing by allowing Vault Admins to fully manage a Vault's lifecycle from initial to go-live.
/api/{version}/objects/sandbox/actions/buildproduction/api/{version}/objects/sandbox/actions/promoteproductionView these endpoints in the v21.2 API Reference.
Existing Endpoints
Section link for Existing EndpointsAuth & Change My Password: User Credentials as Body Parameters
Section link for Auth & Change My Password: User Credentials as Body ParametersStarting from v21.2, the Authentication and Change My Password REST APIs ignore user credentials passed as query String parameters. These APIs only accept the username and password as body parameters. In previous API versions, we recommend using the body for these parameters as a best practice.
Read and Understood Document Workflows
Section link for Read and Understood Document WorkflowsThis feature allows administrators to create and run “Read and Understood” workflows for multiple documents.
Read and Understood workflows can’t be started using the Document Workflow APIs(formerly multi-document workflow), however, Read and Understood tasks can be completed, reassigned, or canceled using the Initiate Workflow Action APIs.
/api/{version}/objects/objectworkflows/{workflow_id}/actions/api/{version}/objects/objectworkflows/{workflow_id}/actions/{workflow_action}/api/{version}/objects/objectworkflows/{workflow_id}/actions/{workflow_action}When querying Read and Understood workflow tasks, the Retrieve Workflow Tasks and Retrieve Workflow Task Details endpoints now include the workflow_class__sys field in the response with a value of read_and_understood__sys.
/api/{version}/objects/objectworkflows/tasks/api/{version}/objects/objectworkflows/tasks/{task_id}Learn more in the v21.2 API Reference.
Restrict Document Workflow to a Single Document
Section link for Restrict Document Workflow to a Single DocumentWe are adding some new attributes as part of this feature for Object and Document(formerly multi-document workflow) workflows.
Attribute type is getting added with all workflows. This will determine whether a workflow is Object or Document (formerly multi-document workflow) workflow.
Attribute cardinality determines whether you can have only one or many documents. For e.g.
/api/{version}/objects/documents/actions/{workflow_name}will return type as Document and cardinality as One if it’s a Document workflow and can be used with only one document.
Learn more in the v21.2 API Reference.
Task Completion API Enhancement
Section link for Task Completion API EnhancementRetrieve Task Complete API
/api/{version}/objects/objectworkflows/tasks/{task_id}/actions/completenow returns tasks with eSignature.
Completion of tasks with eSignature continues to remain blocked through APIs.
Learn more in the v21.2 API Reference.
Prevent Reclassify for Checked-out Documents
Section link for Prevent Reclassify for Checked-out DocumentsFor all versions of the API, the Reclassify Document endpoint no longer allows reclassification for documents that are currently checked out.
/api/{version}/objects/documents/{doc_id}Include Inactive Classification on Single Document Version
Section link for Include Inactive Classification on Single Document VersionWhen retrieving single document versions, previous versions of the API return null for classification__v when the classification is inactive. In API v21.2+, inactive classifications return the classification name.
Facetable Attribute
Section link for Facetable AttributeMetadata describe queries on documents and objects will now return a facetable attribute with each field to indicate which fields will return facets when searching document or object tabs in the Vault UI.
Remove Duplicate Previous Page and Next Page Link in API results
Section link for Remove Duplicate Previous Page and Next Page Link in API resultsIn API v21.2+, the /audittrail endpoints contain only one previous_page and next_page link.
In previous API versions, these endpoints contain both previousPage and previous_page as well as nextPage and next_page links.
Audit API Returns Nulls
Section link for Audit API Returns NullsAudit API JSON responses now include null instead of empty strings when a field is blank. This change only affects v21.2+.
Learn more in the v21.2 API Reference.
Application-Specific Endpoints
Section link for Application-Specific EndpointsVeeva Safety: Inbox and Imported Case Create API from E2B
Section link for Veeva Safety: Inbox and Imported Case Create API from E2BThe Veeva Safety API can now receive E2B files and import to either Imported Cases or Inbox Items. New endpoints have also been introduced for retrieving import status and ACKs.
Learn more in the v21.2 API Reference.
VQL for Document Workflows
Section link for VQL for Document WorkflowsThis feature allows VQL developers to query Document Workflows (formerly multi-document workflow), workflow tasks, and supports relationships to user data. To access this data, we’ve introduced new query targets for actively running workflows and completed (or cancelled) workflows. Query results can be sorted, filtered, and paginated.
Learn more about querying document workflows in the VQL documentation.
Number Precision for Document Field Queries
Section link for Number Precision for Document Field QueriesThis feature enhances the decimal precision of field values for Number fields. As of VQL v21.2+, document read precision is based on the number field’s configured Decimal places.
For example, if you save a document number field with a value of 3.0 and the Decimal places for that field is configured as 2, you will see a field value of 3.00 in VQL query results.
Learn more about querying number fields with VQL.
Vault Java SDK
Section link for Vault Java SDKAction Icons
Section link for Action IconsYou can now specify one of 10 icons to display in the Actions menu for custom record and document actions using the icon element of a RecordActionInfo or DocumentActionInfo annotation. When a custom action is used frequently by a user, it is displayed in the most frequently used actions section of the Action Bar with the specified icon.
Learn more about Action Icons.
JSON Binding Annotations: User-Defined Model and Property
Section link for JSON Binding Annotations: User-Defined Model and PropertyThis features introduces a new Vault Java SDK code type, user-defined model, which
supports annotating getters and setters on a Java interface as a user-defined property. Using JsonService, developers can serialize a model to JSON and deserialize JSON to a model. Additionally, user-defined models can be used with HttpService to send and retrieve data using REST APIs.
Learn more about user-defined models.
Object Metadata Service Field Type Support
Section link for Object Metadata Service Field Type SupportStarting in 21R1.2, object field types and value types are now available for retrieval as part of the ObjectMetadataService. This functionality is extremely useful for use cases where the custom Java SDK code needs to have conditional logic based on the type or value type of a field.
Support PATCH on HttpRequest
Section link for Support PATCH on HttpRequestHttpRequest now supports the PATCH verb when making REST API calls with HttpService.
Audit Enhancements: On Behalf of User
Section link for Audit Enhancements: On Behalf of UserSystem and Application events that make data changes will be logged as System on behalf of {username}, which provides additional visibility into which user’s actions caused data to be created, updated, or deleted. Previously, these audit entries were logged simply as System. Existing audit entries will not be altered and only new audit entries will reflect this additional information.
ObjectFieldType Implements FieldType Interface
Section link for ObjectFieldType Implements FieldType InterfaceObjectFieldType now implements the common FieldType interface.