Juni 2026

26. Juni 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.

Was ist neu

• 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.
• Die API wertet während der Extraktion und Validierung in der Taxonomie- definierten Geschäftsregeln aus, um sicherzustellen, dass extrahierte Daten konfigurierten Anforderungen wie Pflichtfeldern und zulässigen Werten entsprechen.
• Vordefinierte Projekte unterstützen jetzt eine tagbasierte Extraktion mit einem einzigen Tag namens Produktion.
• 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 fields property has been removed from Discovery responses; integrations must use taxonomy instead.
• Die Discovery-Routen geben jetzt tags${DNT_1} anstelle von tag${DNT_2} zurück.
• 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 == Table now return FieldType == FieldGroup. Parsers that handle only Table results will not process this data. For detailed migration steps and examples, check Migrating integrations from Document Understanding API v1 to v2.

8. Juni 2026

Fehlerbehebungen

Leere Seiten führten dazu, dass Extraktionshervorhebungen auf den falschen Seiten im Action Center angezeigt wurden. Extraktionsergebnisse waren unverändert.