Skip to content
Vault Logo
Vault Developer Portal Developer
Advanced Search

    Release Notes

    Developer Features in 26R3

    Filters

    Application Family

    Tags

    We are pleased to bring you the following additions and enhancements to Developer Portal features in 26R3.

    Vault Java SDK

    Section link for Vault Java SDK

    SDK: Document Lifecycle Entry Criteria & Action Config Metadata

    Section link for SDK: Document Lifecycle Entry Criteria & Action Config Metadata
    • Vault Java SDK
    Release Date: 26R2.2; August 21, 2026

    This feature provides developers with a read-only, structured way to inspect the rules, conditions, and actions associated with a specific lifecycle state.

    With this release, we've added new Vault Java SDK interfaces to retrieve lifecycle configuration metadata for entry criteria and entry action configuration.

    The new interfaces extend ObjectLifecycleMetadataService and DocumentLifecycleMetadataService, and follow a request/response pair pattern with a Builder for each new service method

    • ObjectLifecycleStateEntryCriteriaMetadataRequest
    • DocumentLifecycleStateEntryCriteriaMetadataRequest
    • ObjectLifecycleStateEntryActionMetadataRequest
    • DocumentLifecycleStateEntryActionMetadataRequest
    • ObjectLifecycleStateEntryCriteriaMetadataResponse
    • DocumentLifecycleStateEntryCriteriaMetadataResponse
    • ObjectLifecycleStateEntryActionMetadataResponse
    • DocumentLifecycleStateEntryActionMetadataResponse

    Vault API v26.3

    Section link for Vault API v26.3

    Grouping ID in Audit Exports

    Section link for Grouping ID in Audit Exports
    • Vault API
    Release Date: 26R2.2; August 21, 2026

    The grouping_id attribute is now available in the document audit details for the Retrieve Audit Details and Retrieve Complete Audit History for a Single Document endpoints. The Grouping ID column is also available in the CSV exports for these endpoints.

    The Grouping ID groups the entries that belong to the same transaction. The Grouping ID attribute was previously only available for object audit trail details.

    API/SDK Support for Object Reference Notation for Document Fields

    Section link for API/SDK Support for Object Reference Notation for Document Fields
    • Vault API
    • Vault Java SDK
    Release Date: 26R2.2; August 21, 2026

    To allow better portability and improved readability of code and payload, object reference notation can now be used to set object reference field values on a document via Vault API or Vault Java SDK.

    docToUpdate.setValue("document_product__vr.name__v", "VERTEO-NATEVBA")

    Direct Data API

    Section link for Direct Data API

    Grouping Id for Document Audit Log Extracts

    Section link for Grouping Id for Document Audit Log Extracts
    • Direct Data API
    Release Date: 26R2.2; August 21, 2026

    Direct Data API exports of document audit trail will now expose the grouping_id attribute, which groups entries that belong to the same transaction.

    MDL

    Section link for MDL

    Admin Configurable Entry Criteria Validation Messages

    Section link for Admin Configurable Entry Criteria Validation Messages
    • MDL
    • Vault Java SDK
    Release Date: 26R2.2; August 21, 2026

    To provide a better user experience for entry criteria on document and object lifecycles, Admins can configure optional validation messages for each rule of up to 500 characters. If Admins choose not to configure custom validation messages, Vault returns the default system messages.

    Validation messages can be retrieved via Vault Java SDK using the getErrorMessage() method.

    In support of this feature the MDL for document and object lifecycles has been updated with the <errorMessage> tag for <action> nodes in the XML.

    Quality Teams Standard Triggers (SDK Object Groups)

    Section link for Quality Teams Standard Triggers (SDK Object Groups)
    • MDL
    • Vault Java SDK
    Release Date: 26R2.2; August 21, 2026

    Currently, Quality Teams dynamically provision custom triggers for custom objects. This consumes Vault Platform trigger capacity, subjects the Veeva QMS application logic to custom SDK timeouts (500 ms) and memory limits, and causes VPK deployment errors due to inconsistent name-truncation behaviors across Vaults.

    This release addresses those issues by utilizing Vault Platform's SDK Object Groups, which enables the Veeva QMS application to use a single unified standard trigger to coordinate execution across both standard and custom object types.

    This release adds a new SDK Object Group named team_enabled_objects_group__v for the QMS application. The group contains all Quality Team-enabled objects, ensuring standard triggers are used for all Quality Teams. The new group is hidden from customers and is read-only.