document-understanding
latest
false
- Document Understanding for Automation Cloud and Test Cloud
- Document Understanding for Automation Cloud and Test Cloud Public Sector
- Document Understanding for Automation Cloud and Test Cloud Dedicated
- ML packages and public endpoints
Document Understanding release notes
June 26, 2026
Introducing Field Groups and Monetary Quantity
Field Groups and Monetary Quantity are now generally available in Validation Station, activities, and APIs. For more details, refer to Taxonomy Manager.
This enhancement aligns the Document Understanding data type model with the IXP Unstructured and Complex Documents.
Document Understanding API v2
Document Understanding API v2 is now generally available. API v2 adds taxonomy-driven extraction and validation, business rule evaluation, expanded non-Latin language support, and Intelligent Xtraction and Processing (IXP) FieldGroup support in the extraction result.
What’s new
- Discovery returns the associated taxonomy in the response so you can use it to guide extraction and validation.
- Extraction and Validation accept taxonomy as an input parameter. This enables partial extraction, data type overrides, and additional validation customization. For details, see Use the Validation Service.
- The API evaluates business rules defined in the taxonomy during extraction and validation to ensure that extracted data complies with configured requirements, such as mandatory fields and allowed values.
- Predefined projects now support tag-based extraction using a single tag named Production.
- IXP extraction result is now returned as FieldGroups instead of Tables. With FieldGroups, each field preserves its actual data type. For details, see Taxonomy Manager.
- A new predefined project offers enhanced support for non-Latin character sets.
Document Understanding API v2 breaking changes
The following changes require updates to your automations when migrating from API v1 to v2:
- Response bodies on all routes now use PascalCase property names instead of camelCase. Any case-sensitive integrations, such as those written in Python, JavaScript, or others, require updating to match the new casing.
- Tag-based routes now use
/projects/{projectId}/tags/{tag}/.... Requests using the previous route structure return a 400 bad request error in v2. - The
fieldsproperty has been removed from Discovery responses; integrations must usetaxonomyinstead. - The Discovery routes now return
tagsinstead oftag. - IXP extraction results are now returned as FieldGroups instead of Tables, which requires updates if your automation treats extraction results as tables to handle the new FieldGroup structure and data types.
- Entries that previously returned
FieldType == Tablenow returnFieldType == FieldGroup. Parsers that handle onlyTableresults will not process this data. For detailed migration steps and examples, check Migrating integrations from Document Understanding API v1 to v2.
June 8, 2026
Bug fixes
Blank pages caused extraction highlights to appear on the wrong pages in Action Center. Extraction results were unaffected.