We are pleased to bring you the following additions and enhancements to Developer Portal features in 26R1.
Release Date: December 19, 2025
We are pleased to bring you the following additions and enhancements to Developer Portal features in 25R3.2.
Vault can now execute custom business logic when documents and document versions are created, updated, and deleted. This allows custom solutions to populate and clear field values, create related records, start SDK jobs and workflows, and perform complex validation logic. Developers familiar with record triggers can easily deploy doctype triggers to their Vault. Doctype triggers are assigned to a single Doctype, including base_document__v, and support all existing SDK services. Doctype triggers do not fire for updates to document attachments, document relationships, document roles, or annotations.
For performance reasons, Vault API no longer supports using the Retrieve All Documents and Retrieve All Binders endpoints. Existing integrations will continue to work using older API versions prior to 26R1, but we recommend building new integrations using VQL and the Submitting a Query API. Customers using this deprecated API should consider migrating their solution to VQL.
Paginated VQL queries can now be paged through for a maximum of 72 hours after being run, even if more than 20 minutes passes after the last page access.
Developers can now inspect the event type after executing a delete operation on object records. This allows for generic handlers to be built to process insert, update, and delete operations.
Developers can now determine if a given object has auditing enabled or not.
Developers can now execute VQL queries using QueryService and get the results as user-defined models (UDMs) directly instead of first processing QueryExecutionResults and transforming them into UDMs. This allows developers to streamline code that responds to Custom Pages and Web APIs.
Developers can now query the following query targets natively in SDK using QueryService:
archived_documentsmatched_documentsrenditionsbinder_node__sysUsing MDL, Admins and developers can configure Picklist entries to be ordered by the order attribute. Starting in 25R3.2, Admins and developers can also configure Picklist entries to be sorted by the end-user label, ascending or descending. To support this functionality, we’ve added the new order_type attribute to the Picklist component type.