Developer Features in 25R3
Filters
Application Family
Tags
We are pleased to bring you the following additions and enhancements to Developer Portal features in 25R3.
Service Announcements
Section link for Service AnnouncementsDigiCert G2 certificate
Section link for DigiCert G2 certificateIn 25R3, Veeva will migrate from the DigiCert Legacy Root Certificate to the DigiCert G2 Root Certificate for signing Vault SSL Certificates. This is to align with DigiCert and Mozilla's end of life for the Legacy Root Certificate in April 2026
TLS 1.3 Support for Legacy FTPS
Section link for TLS 1.3 Support for Legacy FTPSTLS 1.3 is now supported on Legacy FTPS connections. New integrations should use File Staging API.
Validate Document Creations after Event Actions
Section link for Validate Document Creations after Event ActionsFor documents created using Vault API or Vault Java SDK, field validation will now take place after any existing Event Actions. Previously, validation occurred before Event Actions were invoked, preventing document creation if an empty mandatory field was intended to be populated by an Event Action.
Spark Signing Certificate Public Access
Section link for Spark Signing Certificate Public AccessIntegrations can now retrieve the Spark signing certificate from Vault API without a Vault session ID. This allows developers to build integrations that can accept a Spark message and verify the signature without needing authenticated access to Vault. This change applies to all Vault API versions prior to and after v25.3.
Upcoming Deprecation of Submission Archive Export APIs
Section link for Upcoming Deprecation of Submission Archive Export APIsAs part of our ongoing efforts to ensure future scalability and continued performance of Submissions Archive, the following RIM Submissions Archive API endpoints will be deprecated in all versions of the API and no longer supported as of 26R3:
- Export Submission
- Export Partial Submission
- Retrieve Submission Import Results
- Retrieve Submission Export Results
These endpoints will be replaced by new Submissions Archive Export API endpoints. For customers with existing integrations, the new API endpoints will be available starting with 26R2, enabling you to prepare for the upcoming 26R3 deprecation.
Release Highlights
Section link for Release HighlightsLabel Sets
Section link for Label SetsLabel Sets allows alternative labels to be displayed in the Vault UI within a single language to support use cases where different groups of users within a given country or region may have different terminology. Learn more about the user and Admin-facing functionality of this feature in Vault Help
Developers can create new Labelset configurations using MDL, and integrations can import and export labels for the label sets using Vault API.
/api/{version}/messages/{message_type}/label_set/{name}/actions/exportAsynchronous Workflow Tasks
Section link for Asynchronous Workflow TasksVault Admins can now configure workflow steps that execute a specified job. Jobs can be configured to automatically complete the job step once the job has finished, or developers can use the WorkflowInstanceService to complete the job task. This allows admin and developers to build asynchronous steps into their workflows. Developers can also use Spark and HTTP Callout to execute logic externally, and use the new Complete Workflow Job Step API to complete the workflow task. Additionally, workflow job steps can be queried using VQL to obtain relevant details about the job step.
Vault API v25.3
Section link for Vault API v25.3Direct Data API
Section link for Direct Data APIPicklist Rename Tracking
Section link for Picklist Rename TrackingWhen a picklist value associated with an object or document field is renamed, Direct Data API now includes the old value in the object or document's delete CSV file. This helps developers remove the old value from downstream systems. The new value will continue to be included in the update CSV file.
Include Inactive Object Fields
Section link for Include Inactive Object FieldsDirect Data API now includes inactive object fields in Full and Incremental file extracts. This allows developers to load historic Vault data into their downstream systems.
Additional Attributes for Object Audit Extract
Section link for Additional Attributes for Object Audit ExtractDirect Data API now includes integration-focused attributes in object audit trails, including object and field API names, old and new API values, and audit group IDs. These new attributes can be used to join audit records to data records in downstream systems.
Include All Queryable Document Fields
Section link for Include All Queryable Document FieldsDirect Data API now includes all queryable document fields. The additional fields will be included in the Full and Incremental files created after the 25R3 release.
Enhanced Background Processing
Section link for Enhanced Background ProcessingDirect Data API is built for resiliency and will automatically retry when errors occur. The Vault Admin UI no longer displays job operations for Direct Data API, and the jobs are excluded from VQL targets. Admins and developers can determine success and retry status using the Retrieve Available Direct Data Files endpoint.
New Endpoints
Section link for New EndpointsExport Attachment Field Files API
Section link for Export Attachment Field Files APIDevelopers can now export attachment fields files in bulk for a given Vault object and for up to 500 record IDs. Attachment field files are collected asynchronously and zipped for easy download. Learn more about this endpoint in the v25.3 API Reference.
Bulk-cancel Jobs in Queued or Queueing State
Section link for Bulk-cancel Jobs in Queued or Queueing StateDevelopers can now cancel jobs in Scheduled, Queued, or Queueing state using Vault API. Not all Queued or Queueing jobs can be cancelled and cancellation is best-effort. Vault API will return errors for jobs that cannot be cancelled. Learn more about this endpoint in the v25.3 API Reference.
Existing Endpoints
Section link for Existing EndpointsSupport for Picklist Names in Single Document and Binder Updates
Section link for Support for Picklist Names in Single Document and Binder UpdatesVault API now supports using picklist names when updating single documents and binders. Previously, only Picklist labels were supported. This means developers can use consistent values instead of labels that can change per the user’s language.
Bulk Support for Document Text Export
Section link for Bulk Support for Document Text ExportThe Export Documents and Export Document Versions endpoints now support exporting document text in bulk. When developers include text=true in their API request, Vault creates a "text" folder containing a text file (text_file.txt) with the extracted text for each exported document version.
Create Single Document Version API: Return Major and Minor Version in Response when File Parameter is Used
Section link for Create Single Document Version API: Return Major and Minor Version in Response when File Parameter is UsedVault API now returns the major and minor version of new document versions created using the Create Single Document Version endpoint and the file body parameter. This new document metadata is only available for Vault API v25.3+.
Delegate Access: Vault Owner Group Restriction
Section link for Delegate Access: Vault Owner Group RestrictionThe system-provided Vault Owners group now allows editing the Delegate access allowed only among group members configuration. Developers can use Vault API to change the value of this attribute.
Notifications Suppressed in Migration Mode
Section link for Notifications Suppressed in Migration ModeWhen using Migration Mode with document and Vault object APIs, including Vault Loader, Vault will suppress any notifications related to the request. This helps reduce load on Vault and unnecessary emails to end-users.
Vault Loader
Section link for Vault LoaderSupport for Changing Object Type
Section link for Support for Changing Object TypeVault Loader now supports changing object types on object records. This allows developers to use Vault Loader API, CLI, and UI to easily change object types in bulk.
Document Text Export
Section link for Document Text ExportVault Loader now supports including document text when exporting documents. A document’s text can be used to train AI models and perform comprehensive searches outside of Vault. This enhancement is included in Vault Loader API, CLI, and Vault UI.
Object & Document Attachments & External ID
Section link for Object & Document Attachments & External IDA new field, attachment_external_id__sys, has been added to the attachments__sysr relationship for documents and object record attachments. This allows developers to query for external IDs and use them when updating attachments using Vault API and Vault SDK.
Enhanced Display Formatting in VQL
Section link for Enhanced Display Formatting in VQLThe TODISPLAYFORMAT() function in VQL now reflects how data is displayed in Vault UI, even for text and number fields without format masks configured. This can ensure consistency between data retrieved via VQL queries and the visual representation for number fields in Vault UI.
Enhancements to FIND
Section link for Enhancements to FINDThe FIND clause has been enhanced to support using the scope modifier on relationships from the SELECT clause.
SELECT id, product__vr.name__v
FROM study__v
FIND ('Trial' SCOPE product__vr.name__v)Additionally, the FIND clause can now be used in subqueries. Note: the FIND clause is not supported on attachment subqueries.
SELECT id, (SELECT name__v from study__vr FIND ('US'))
FROM product__vSELECT id
FROM product__v
WHERE id IN (SELECT id FROM study__vr FIND ('US'))Vault Java SDK
Section link for Vault Java SDKCustomizable Timeout Period for SDK Jobs
Section link for Customizable Timeout Period for SDK JobsA new attribute, timeout_duration, has been added to the Jobmetadata component. This attribute allows developers to override the existing default timeout to a lower maximum timeout for SDK jobs. Allowed values are defined in minutes and include: 60 (1 hr), 240 (4 hrs), 480 (8 hrs), 720 (12 hrs), 1380 (23 hrs). If set, this attribute overrides the existing default timeout, which is 23 hours (1380 minutes) for one-time jobs or 72 hours (4320 minutes) for scheduled jobs.
Jobs SDK: Support for a List of String field types
Section link for Jobs SDK: Support for a List of String field typesIn this release, the JobParamValueType interface now supports a List of String field types as input when setting job parameters when invoking a job. Additionally, the JobValueType interface now supports a List of String field types as input when setting parameters during job initialization and processing. This allows developers to directly provide a list of Strings as input and eliminates the need for extra custom code.
SDK Record Role Support for Removing Inactive Users
Section link for SDK Record Role Support for Removing Inactive UsersRecordRoleService now supports removing inactive users from object record roles. Previously, attempting to remove a user would throw an exception if the user was inactive.
Document Field Metadata SDK Enhancements
Section link for Document Field Metadata SDK EnhancementsDevelopers can now inspect all metadata for document fields using Vault Java SDK. This allows developers to build logic based on Docfield attributes such as min/max length for Strings and min/max values for Numbers.
QueryDescribe for SHOW statements
Section link for QueryDescribe for SHOW statementsQuery Describe for SDK now supports SHOW statements. This allows developers to inspect the data types and labels of query targets.
Veeva Quality
Section link for Veeva QualityAuditor Profile API
Section link for Auditor Profile APIVeeva QMS now supports associating Auditor Roles to Auditor Profiles in bulk. Developers can submit a CSV with up to 500 Auditor Role and Auditor Profile pairs, and Vault asynchronously associates the Auditor Role to the Auditor Profile. Learn more about this endpoint in the v25.3 API Reference.
Quality Teams Migration API
Section link for Quality Teams Migration APIVeeva Quality now supports creating Quality Team members for migration purposes. A new endpoint has been introduced that accepts the object record’s external ID, the user name, and API name for the team role to be added. Vault API now supports creating these configurations in bulk, and performs the operations asynchronously. The creation of the team members is optimized for performance. Learn more about this endpoint in the v25.3 API Reference.
Action Path Enhancements: Improved Flexibility and UI
Section link for Action Path Enhancements: Improved Flexibility and UINew attributes have been added to the Qmsactionpathconfiguration components in Veeva QMS. The allow_in_progress_changes attribute supports Change Actions to be associated with the Action Step in the In Progress state. The hide_other_actions attribute allows developers to define whether or not the Other Actions section shall be displayed from the Action Step app section.
Veeva RIM
Section link for Veeva RIMHAQ Response Automations
Section link for HAQ Response AutomationsThis feature streamlines the process of responding to Health Authority Questions (HAQs) by introducing the Initiate Response action, allowing RIM users to create a response record, start a submission, auto-generate a content plan, and create a response document from a single, guided flow. Learn more about the user and admin-facing functionality of this feature in the Vault Help Release Notes
To support this functionality, the MDL for the Rimdoctypeconfig component now includes the new response_document_type boolean attribute.
Export API: Support for Published Submissions
Section link for Export API: Support for Published SubmissionsVeeva RIM now supports exporting published submissions using the existing Export Submissions endpoint. Previously, only imported submissions were supported.
Veeva Clinical
Section link for Veeva ClinicalData Change Request API
Section link for Data Change Request APIVeeva Clinical Operations now supports submitting a Data Change Request (DCR) to Vault and OpenData Clinical. With this, OpenData Clinical customers who are using the entire dataset in separate systems can remotely raise DCRs in their Vault and track their resolution. Learn more about this endpoint in the v25.3 API Reference.