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.This flow is recommended for situations where an external identity provider is enabled for the tenant, allowing for 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.
- Users should pass different filenames for each input file when creating transactions for several files; refer to the user guide for more details.
- The connector uses the default
imageProcessingOptions("autoCrop": "Default","autoOrientation": "Default") when creating a transaction. - The
ExtractedDataoutput parameter is not filled out if “Values only” JSON is enabled in Process Skill Output settings. 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. Note that UiPath will also soon stop supporting UiPath Studio based on .NET Framework 4.6. For more information, see here.
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. |
Upgrading 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 re-configure your processes according to the methods described in the User Guide.Perform the steps below to install the 2.2 version.- Update the packages in the package source:
- Run the connector installer to unpack new connector version files.
- Upload all
.nupkgpackages from theABBYY Vantage Connector for UiPath\UiPath Activitiesfolder to your UiPath package source.
- Increment the connector’s version in all UiPath projects:
- Create backup versions of all UiPath projects with the connector that you need to update.
- Open your UiPath project where the previous connector version is used.
- Navigate to Manage Packages > Project Dependencies.
- 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). - Click Update, and then Save.
- A new package version of
Abbyy.UiPath.Vantage.Activitieswill appear in the Project tree. - Click the Refresh button in the Map Fields activity to use the new variable type for mapping repeatable groups with repeatable fields and groups.
- Update projects in Orchestrator. After updating project dependencies, publish the new project version in Orchestrator.
