> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/release-notes/canakkale-edition/canakkale-5.7.0/canakkale-5.7.1.md).

# Canakkale 5.7.1

## Release Summary

Autom Mate Canakkale 5.7.1 is a compatibility, security, and reliability-focused release that introduces new authentication and data-processing capabilities while strengthening upgrade stability and infrastructure management.

RESTful Web Service actions now support native Bearer Token Authentication, enabling tokens to be securely added to HTTP requests without manually constructing authorization headers. The Excel VLookup action has also been enhanced with First Match and Last Match options, giving users explicit control over the result returned when multiple matching records are found.

A major focus of this release is backward compatibility. Existing VLookup actions retain their previous Last Match behavior, historical action versions published under the former 4me library name are now available through Xurrent, and database migrations have been improved to support upgrades from older Autom Mate versions safely.

Canakkale 5.7.1 also includes dependency security updates, a MySQL version upgrade, automatic SSL certificate refresh capabilities for hybrid environments, and several user-interface corrections.

With these improvements, Autom Mate delivers more predictable upgrade paths, safer integrations, clearer data-processing behavior, and stronger infrastructure reliability.

***

## **Highlights of this Release**

### 🅱️ **Bug Fixes**

* Fixed migration failures that could occur while upgrading from older Autom Mate versions.
* Fixed incorrectly spelled English labels on the Dashboard and Object Assign action screens.

***

### ✨ **New Features**

* Bearer Token Authentication support for RESTful Web Service actions.
* First Match and Last Match options for the Excel VLookup action.
* Automatic SSL certificate refresh for hybrid environments

***

### 🛠️ **Enhancements**

* Historical action versions published under the former 4me library name are now displayed in Xurrent.
* Excel Source handling in the VLookup action has been improved.
* Application packages and dependencies have been updated to address security vulnerabilities.
* MySQL has been upgraded in line with current security and infrastructure requirements.

***

## **Detailed Version**

{% tabs %}
{% tab title="🅱️ Bug Fix" %}

* #### Migration Error During Upgrades from Older Versions

  An issue that could cause database migrations to fail while upgrading from older Autom Mate versions has been resolved.

  A migration introduced in version 5.3.0 adds new columns to the `version_info` table. During certain upgrade scenarios, particularly upgrades from version 4.4.0, differences in the existing database schema could cause the migration to attempt to create columns that were already present.

  This prevented the migration and overall version upgrade from being completed successfully.

  The migration process now checks the existing database schema before creating or modifying the required columns. Columns that already exist are no longer recreated.

  With this fix:

  * Upgrades from older Autom Mate versions can be completed successfully.
  * Different `version_info` table structures are handled safely.
  * Duplicate-column migration errors are prevented.
  * Fresh installations continue to work as expected.
  * Compatibility with existing database structures is preserved.

***

* #### English Spelling Errors in the User Interface

  Several incorrectly spelled English labels in the Autom Mate user interface have been corrected.

  The following changes have been applied:

  * `Estiamted` on the Dashboard has been changed to `Estimated`.
  * `Asssigned` in the Object Assign action has been changed to `Assigned`.
  * `Variable to be Asssigned` has been changed to `Variable to be Assigned`.

  Relevant screens, shared components, and localization resources have also been reviewed to ensure consistent terminology.

  These corrections do not affect existing application functionality or screen layouts.
  {% endtab %}

{% tab title="✨ New Features" %}

* #### Bearer Token Authentication for RESTful Web Service Actions

  A new Bearer Token Authentication option has been added to RESTful Web Service actions.

  When this authentication method is selected, the configured token is automatically added to the HTTP request using the following authorization header:

  `Authorization: Bearer {token}`

  Bearer Token Authentication is supported for all available HTTP methods:

  * GET
  * POST
  * PUT
  * PATCH
  * DELETE

  Users no longer need to manually create the Authorization header for standard Bearer Token authentication scenarios.

  Token values are not displayed in plain text in action logs or error messages. When the entered token already contains the `Bearer` prefix, the system prevents duplicate values such as `Bearer Bearer`.

  Existing RESTful Web Service actions that use other authentication methods continue to operate without any behavioral changes.

***

* #### First and Last Match Options for the Excel VLookup Action

  The Excel VLookup action now allows users to select which result should be returned when multiple matching records are found.

  The following options are available:

  * **First Match:** Returns the first matching record.
  * **Last Match:** Returns the last matching record.

  Newly created VLookup actions use First Match by default. This aligns the action behavior with the Microsoft Excel VLOOKUP function.

  To preserve backward compatibility, existing VLookup actions continue to use the Last Match behavior. Users do not need to reopen, edit, or save previously configured actions.

  There are no changes to the existing behavior for:

  * Single matching records
  * Unmatched values
  * Approximate matches
  * Existing validation and error handling

***

* #### Automatic SSL Refresh for Hybrid Environments

  An Auto-SSL Refresh mechanism has been introduced for hybrid Autom Mate deployments.

  The mechanism automatically manages SSL certificate renewal and ensures that renewed certificates continue to be used by the relevant services.

  This reduces the need for manual certificate replacement and helps prevent connection or service availability issues caused by expired SSL certificates.

  The new mechanism improves the reliability of secure communication between Autom Mate cloud components and services running in hybrid customer environments.
  {% endtab %}

{% tab title="🛠️ Enhancements" %}

* #### Historical Xurrent Action Versions Are Now Displayed Correctly

  The integration library previously known as 4me was later renamed to Xurrent. Some older action versions were published while the library was still identified as 4me.

  As a result, these historical versions were not always displayed in the action version selection screen after the library was renamed.

  The Xurrent action version list now includes versions published under both:

  * The legacy **4me** library name
  * The current **Xurrent** library name

  Versions from both library names are combined into a single version history, and duplicate version records are excluded.

  Affected actions, including **Create Request** and **Get Any Object with ID**, now display their complete version history.

  Historical action versions can be selected, saved, and executed normally. Version listing behavior for other libraries remains unchanged.

***

* #### Excel Source Handling Improved in the VLookup Action

  The Excel Source field in the Excel VLookup action has been updated to actively define the dataset used during the lookup operation.

  This provides clearer and more predictable source selection when configuring VLookup actions.

  Backward compatibility is maintained for existing configurations, and previously created automs continue to operate without requiring manual updates.

***

* #### Dependency and Package Security Updates

  Several application packages and third-party dependencies have been upgraded to address identified security vulnerabilities.

  These updates improve the overall security posture of Autom Mate while preserving compatibility with the existing application architecture and functionality.

  The upgrades also ensure that the platform continues to use supported and maintained dependency versions.

***

* #### MySQL Version Upgraded

  The MySQL version used by Autom Mate has been upgraded in line with current security and infrastructure requirements.

  The upgrade provides improvements in:

  * Database security
  * Runtime stability
  * Infrastructure compatibility
  * Long-term maintainability

  Autom Mate application and migration processes have been updated to support the new MySQL version.
  {% endtab %}
  {% endtabs %}

***

## User Notices & Guidance

This section highlights important behavioral changes, usage recommendations, and practical tips introduced in Canakkale 5.7.0. Reviewing these notes will help users adopt the new global notification framework, updated notification panel, Mate Agent monitoring, and the refreshed Dashboard Summary Mail smoothly.

{% hint style="danger" %}

#### Warnings (Critical Behavior Changes)

* Newly created Excel VLookup actions use First Match by default.
* Existing VLookup actions continue to use the legacy Last Match behavior.
* Changing the match option of an existing VLookup action may change the output when duplicate lookup values exist.
* Database and MySQL upgrades should be completed according to the standard Autom Mate upgrade procedure.
* Bearer tokens must continue to be treated as sensitive credentials even though they are masked in logs and error messages.
  {% endhint %}

***

{% hint style="info" %}

#### Hints (Productivity Tips)

* Use First Match when the lookup should behave like the Microsoft Excel VLOOKUP function.
* Use Last Match when the final matching record in the Excel source should be returned.
* Bearer tokens can be entered with or without the `Bearer` prefix.
* Historical versions published under 4me can now be accessed through the Xurrent action version list.
  {% endhint %}

***

{% hint style="success" %}

#### Best Practices (Recommended Usage)

* Test VLookup match-option changes with representative Excel data before applying them to production automs.
* Back up the Autom Mate database before performing application or MySQL upgrades.
* Test upgrades from older versions in a non-production environment before upgrading production systems.
* Store and manage Bearer tokens using secure credential-management practices.
* Monitor SSL certificate renewal processes in hybrid environments.
  {% endhint %}