We are pleased to bring you the following additions and enhancements to Developer Portal features in 19R1. REST API features added in 19R1 only affect API v19.1, unless otherwise noted.
Release Date: December 14, 2018
We are pleased to bring you the following additions and enhancements to Developer Portal features in 18R3.2. REST API features added in 19R1 only affect API v19.1, unless otherwise noted. You can learn more about the 18R3.2 Release in Vault Help.
Vault Owners can now migrate or create object records in non-initial lifecycle states using Vault’s Object Record Creation API. Vault Owners can specify
X-VaultAPI-MigrationMode=true in API header and provide a valid lifecycle state (
state__v) field value in the API body to create record in any lifecycle state.
With this release OAuth 2.0 / OpenID Connect Profiles support managing mapping between client IDs defined by Authorization Servers and client IDs defined in client applications. This allows integrating with Authorization Servers where client IDs must be uniquely generated per each app and cannot be configured with the static client IDs built into native applications such as Vault File Manager or Veeva Snap. To take advantage of this feature, the Discovery API can now accept the native application client ID and will include the client ID of the remote Authorization Server if the mapping is configured.
For additional tracking purposes, every Vault REST API call accepts an optional
client_id to represent an external integration client. As of this release,
client_id supports uppercase characters in all versions of the API. Learn more about Client ID in the REST API Documentation.
You can now update the status (Active/Inactive) of a picklist value via the API. Prior to this release, deleting a picklist value just inactivated the value and hid it from admin. In order to re-activate an inactivated value, an API user makes the following call:
They then pass in
status as the body parameter, and either
Inactive as the status value.
Event actions are configurable actions that take place automatically when a user creates a new document, creates a new draft of an existing document, or creates a copy of an existing document. In the current release, you can only configure event actions with a custom action coded through Vault Java SDK.
To make an action available for configuration as a document event action, specify the usage as