We are pleased to bring you the following additions and enhancements to Developer Portal features in 25R2.
Service Announcements are changes that may affect existing integrations. Organizations should assess these features against their existing integrations and make updates where necessary.
In 25R2, Veeva is upgrading Vault Java SDK to Java 17. Java 17 includes optimizations that can improve performance and efficiency compared to Java 8, allowing for reduced resource usage.
In this release, Vault is auto-enabling Java 17 compilation in all Vaults. When enabled, Vault compiles new SDK code deployments with Java 17 instead of Java 8. This means that enabling Java 17 does not automatically test your custom code for compatibility, as existing code is not recompiled. To test your code for compatibility with Java 17, redeploy any existing custom code to recompile with Java 17. We are also adding additional Java 17 syntax has to the JDK allowlist.
When Java 17 is enabled:
Learn more about how to upgrade your code to Java 17, including solutions to common Java 17 compilation errors.
See the full release schedule for more information about these release dates.
Release Date: April 25, 2025
We are pleased to bring you the following additions and enhancements to Developer Portal features in 25R1.2.
Direct Data API now includes an extract that captures document relationships in Direct Data files. This allows developers to represent the relationship between documents, such as based on, supporting, and so on, in downstream systems.
Direct Data API is designed for resiliency. When errors occur, Vault retries the Direct Data job. Starting in v25.2, Vault will return error information, including the next retry date (next_retry). This allows developers to build resilient integrations that can retrieve the file on or after the next retry date.
Direct Data API now has a new job called Direct Data Staging, which runs hourly. It is responsible for the initial staging of data and monitoring any configuration changes that happen in Vault.
When using Vault API or Vault Java SDK to create, update, and delete object records, developers who use an external ID now have access to the unique value supplied in the request payload. This means custom solutions can use external IDs to track success or failure without having to maintain a list of records supplied by the request. Additionally, when upserting records, Vault returns the event type (created or updated) in the response.
Enhanced endpoints and interfaces:
PositionalRecordIdFormattedoutputIn this release, we’ve added a new object class securitytree that allows configuring security trees. When Security Tree objects are created, a corresponding User Tree Assignment object is created automatically with the name defined in the user_tree_assignment_object_name attribute. Developers can then assign the Security Tree object to objects using the security_tree_object attribute. Assigning a security tree automatically generates a Tree Assignment object with the name defined in the tree_assignment_object_name attribute.
Metadata provided in Vault API and Vault Java SDK has been enhanced to return the tree security configuration, and roles assigned using Tree Security are returned when using Object Role APIs and RecordRole Java SDK Services.
A new attribute, replicate_sharing_from_parent, is available on the Object.Field component and allows developers to configure sharing settings to be replicated from the parent object. When this setting is enabled, Custom Sharing Rules and Matching Sharing rules are deleted, and integrations cannot use Vault API or Vault Java SDK to add manual roles. Developers should evaluate existing custom solutions before enabling this setting.
The Retrieve Object Record Collection will not be supported when using API v25.2+. Older API versions are not affected. Instead of this API, developers should use Direct Data API or VQL for optimal performance.
The Retrieve Document Version Notes as CSV API will not be supported when using API v25.2+. Older API versions are not affected.
Instead of this API, developers should use the Read Annotations APIs to retrieve document annotations by document or by ID:
The Retrieve Anchor IDs API will not be supported when using API v25.2+. Older API versions are not affected.
Instead of this API, developers should use the Read Annotations APIs to retrieve anchor annotation IDs by document or by ID:
Integration accounts no longer need admin permissions for Quality Teams to use the Manage Quality Team Assignments API. Users are still required to have API access and edit permissions for Quality Team Relationships on the specified records.
Learn more about the user and admin-facing functionality of this feature in Vault Help.
Developers can now access the Pre-Default Object Reference Field Setting metadata for object fields using ObjectMetadataService.
Using MDL, administrators can now configure the Inboundemailaddress component to notify Vault User and Person senders if the Email record is created in a Bounced state. A new attribute, send_bounce_notification, has a default value of false.