> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Release notes for the UiPath connector
> Version history for the ABBYY Vantage Connector for UiPath: new features, changes, bug fixes, limitations, and known issues in each connector release.
This page lists the new features, changes, fixes, and known issues in each release of the ABBYY Vantage Connector for UiPath, starting with the most recent version.
## Changes
* Updated core package to .NET Framework 4.8.1 and .NET 8.
* Updated NLog from v4.7.13 to v4.7.15.
## Fixes
* Fixed dependency conflict between NLog and UiPath.System.Activities packages to support new versions of UiPath Studio.
## About the release
The main purpose of this release is to support App Principals (utilizing OAuth 2.0 Client Credentials
Flow), intended to facilitate a smoother and more secure integration between ABBYY Vantage and
third-party systems. The functionality offers an improved authorization method for Machine-to-Machine
(M2M) applications, enabling seamless integration without user intervention.
## Main features
### Server-to-server authentication scheme
A new authentication flow called **Client Credentials**, which is suitable for server-to-server
communications, is now supported in the Vantage API. This flow is designed for cases when there is an
application that allows end-users to process documents using Vantage without having accounts in
Vantage.
The new flow can be enabled for any tenant's API client. When enabling the flow, the tenant
administrator can assign roles that will be granted to the application that connects to Vantage using
this flow. When connecting to Vantage, the application will get an access token with the roles specified
in the client's API settings.
Use this flow when an external identity provider is enabled for the tenant, which allows
authentication in Vantage even when the Authorization Code flow would not be suitable.
## Bug fixes
| Jira Ticket # | Description |
| ------------- | --------------------------------------------------------------------- |
| CONN-2821 | Authorization fails when the Vantage tenant is configured to use SSO. |
## Limitations and known issues
### Limitations
* Cross-platform compatibility for UiPath Studio projects is not supported.
* Pass a different filename for each input file when creating transactions with several files. For more information, see [Use Skill activity](/vantage/connectors/uipath/activities/use-skill).
* The connector uses the default `imageProcessingOptions` (`"autoCrop": "Default"`, `"autoOrientation": "Default"`) when creating a transaction.
* The `ExtractedData` output parameter is not filled out if the **Values only** JSON option is enabled in the **Output** activity of the Process skill. This parameter is filled in only when the full JSON data export option is enabled.
* Opening the documentation from the activity context menu in UiPath Studio is disabled.
* .NET Framework version 4.7.2 and higher is supported. UiPath will also soon stop supporting UiPath Studio based on .NET Framework 4.6. For more information, see the [UiPath Windows legacy compatibility documentation](https://docs.uipath.com/studio/standalone/2025.10/user-guide/about-the-windows-legacy-compatibility).
### Known issues
| Jira Ticket # | Description |
| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| CONN-2547 | Password/Client Secret fields are considered empty when the Secure Password/Secure Client Secret field is mapped to an empty variable. |
| CONN-2953 | Image fields are not supported in the Map Fields activity. |
| CONN-3008 | The tree with nested groups, fields, and match variables disappears from the Map Fields activity when switching to another activity. |
| CONN-679, CONN-537 | Proxy settings are not applied if optional parameters (password or protocol) are not specified. |
| CONN-395, CONN-676, CONN-1555, CONN-3205, CONN-3495 | Incorrect error messages. |
## Upgrade the connector
As the 2.0 version of the connector introduced several new capabilities, some of these are entirely
incompatible with 1.x releases. To use this version of the connector and its new features, you must
reconfigure your existing processes.
Install the 2.2 version with the following steps.
1. Run the connector installer to unpack new connector version files.
2. Upload all `.nupkg` packages from `ABBYY Vantage Connector for UiPath\UiPath Activities` to your UiPath package source.
1. Create backup versions of all UiPath projects with the connector that you need to update.
2. Open your UiPath project where the previous connector version is used.
3. Navigate to **Manage Packages** > **Project Dependencies**.
4. In the list of dependencies, find `Abbyy.UiPath.Vantage.Activities`. Select the item and in the **Version** drop-down menu, select the new version (`2.2.0.x`).
5. Click **Update**, and then **Save**.
6. A new package version of `Abbyy.UiPath.Vantage.Activities` appears in the Project tree.
7. Click the **Refresh** button in the Map Fields activity to use the new variable type for mapping repeatable groups with repeatable fields and groups.
After updating project dependencies, publish the new project version in Orchestrator.
To convert Windows-legacy projects to Windows compatibility, follow the procedure outlined in the [UiPath Documentation](https://docs.uipath.com/studio/standalone/2025.10/user-guide/about-the-windows-legacy-compatibility) for each Windows-legacy compatibility project.