# February 2026 > **Improved extraction reliability for specific vendors** ## February 26, 2026 ### Bug fix **Improved extraction reliability for specific vendors** Extraction models such as LayoutLM and Helix no longer skip specific fields for certain document vendors. Field extraction now behaves consistently across supported vendors. ## February 24, 2026 ### Document Understanding API v2 (Preview) Document Understanding API v2 adds taxonomy-driven extraction and validation, business rule evaluation, expanded non-Latin language support, and 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 example, changing field hotkeys or display color). * 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 IXP data type (for example, `Date`, `Number`, `MonetaryQuantity`). * A new predefined project offers enhanced support for non-Latin character sets through. **Breaking changes** When upgrading from **Document Understanding API v1 to v2**, update yourn automations for the following changes: * Tag-based routes now use `/projects/{projectId}/tags/{tag}/...`. Requests using the previous route structure return **400 Bad Request** in v2. * The `fields` property was removed from **Discovery** responses. Use `taxonomy` instead. * The Discovery routes now return `tags` instead of `tag`. * IXP extraction results are now returned as **FieldGroups** instead of **Tables**, which requires updates if your automation currently treats extraction results as tables to handle the new FieldGroup structure and data types. * Update logic that checks FieldType == Table. In v2, those entries return FieldType == FieldGroup. If your parser only handles **Table**, it will ignore the data. :::note Review and update your integrations before migrating to **Document Understanding API v2**. For detailed migration steps and examples, see [Migrating integrations from Document Understanding API v1 to v2](https://docs.uipath.com/document-understanding/automation-cloud/latest/api-guide/migrating-integrations-from-document-understanding-api-v1-to-v2). ::: ## February 18, 2026 ### Field groups and Monetary quantity support (Preview) Field Groups and Monetary quantity support in Validation Station, Activities, and APIs are now available in Preview. Field groups enable the display of hierarchical field structures in Validation Station, allowing logical organization of extracted data. Groups can be single-value, multi-value, or mixed, consisting of fields and tables. Field Groups preserve the hierarchical structure of extracted data, making large, multi-page document packets easier and faster to validate. The new MonetaryQuantity field type introduces dedicated amount and currency data types, eliminating data type mismatches between extraction and validation. This enhancement aligns the Document Understanding data type model with IXP Unstructured and Complex Documents. ## February 12, 2026 ### Bug fixes * Fixed an issue where the Validation Control in (Custom) Apps and (Custom) Action Apps triggered the On Ready component callback event too early, causing operations such as setting field values in the On Ready workflow to fail. * Fixed an issue where OpenAI licensing exceptions were incorrectly exposed. ## February 3, 2026 ### Permissions for field access Based on a role, you can assign permissions for field access. * The **Fields.Create** permission allows a user to create a field. * The **Fields.Delete** permission allows a user to delete an existing field. * The **Fields.Read** permission allows a user to view a field. * The **Fields.Update** permission allows a user to update an existing field. Users with the **Document Understanding Data Annotator** role or the **Document Understanding Viewer** role only have the **Fields.Read** permission. Users with the **Document Understanding Developer**, **Document Understanding Model Trainer**, or **Document Understanding Project Administrator** roles have all available field permissions. :::important Existing custom roles that include document type permissions do **not** automatically include these new fields permissions. As a result, users assigned to these custom roles cannot create, edit, or delete fields. To enable these actions, you must update the applicable custom roles and explicitly add the required fields permissions. ::: For more information, check the [Role-based access control](https://docs.uipath.com/document-understanding/automation-cloud/latest/user-guide/role-based-access-control) page. ### Tenant level Projects permission A new **Projects** permission is available at the tenant level. Project creation is now controlled at the tenant level via the **Projects.Create** permission, while project-level permissions are limited to read, update, and delete actions based on role assignment. Users with the **Document Understanding Administrator** role assigned can create projects using the new **Projects.Create** permission. For more information, check the [Role-based access control](https://docs.uipath.com/document-understanding/automation-cloud/latest/user-guide/role-based-access-control) page.