**Source URL:** https://limited.veevavault.dev/rn/26r3

# Developer Features in 26R3

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

## Vault Java SDK

<ReleaseNote id="OOU0000000RP016" lr="26r2.2" app_family="platform" version="26r3">
### SDK: Document Lifecycle Entry Criteria & Action Config Metadata

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`
</ReleaseNote>

## Vault API v26.3

<ReleaseNote id="OOU0000000Q4005" lr="26r2.2" app_family="platform" version="26r3">
### Grouping ID in Audit Exports

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.
</ReleaseNote>

<ReleaseNote id="OOU0000000R5017" lr="26r2.2" app_family="platform" version="26r3">
### API/SDK Support for Object Reference Notation for Document Fields

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")`
</ReleaseNote>

## Direct Data API

<ReleaseNote id="OOU0000000S9056" lr="26r2.2" app_family="platform" version="26r3">
### Grouping Id for Document Audit Log Extracts

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

## MDL

<ReleaseNote id="OOU0000000RI013" lr="26r2.2" app_family="platform" version="26r3">
### Admin Configurable Entry Criteria Validation Messages

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.
</ReleaseNote>

<ReleaseNote id="OOU0000000RG023" lr="26r2.2" app_family="quality" version="26r3">
### Quality Teams Standard Triggers (SDK Object Groups)

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.

<Aside>
After this release, Veeva QMS will no longer utilize the triggers defined for *Quality Team* enabled objects on the following Vault Admin UI pages:

*   **Admin > Configuration > Record Triggers**
*   **Admin > Configuration > Record Role Triggers**

These triggers will be removed from the Veeva QMS application in a future release. When an Admin configures a new *Quality Team*, the associated triggers will automatically be included in the `team_enabled_objects_group__v`, and will not appear in *Admin > Configuration > Record Triggers* or *Admin > Configuration > Record Role Triggers*. Furthermore, the `record_trigger` and `recordrole_trigger` attributes of the new *Quality Team*'s corresponding `Qualityteam` MDL component will be blank.
</Aside>
</ReleaseNote>