Release notes 26.1 - Automate_Evolve - Latest

Automate Evolve Release Notes

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Evolve
Version
Latest
ft:locale
en-US
Product name
Automate Evolve
ft:title
Automate Evolve Release Notes
Copyright
2026
First publish date
2018
ft:lastEdition
2026-08-11
ft:lastPublication
2026-08-11T10:01:02.380000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Automate
L4_Investment_Segment
SAP Automation
L5_Product_Group
Winshuttle Enterprise
L6_Product_Name
Automate Evolve

What's new

Configure default Grid View items per page

A new option Set default items per page (Between 10 to 200) has been introduced under Personal Preferences > Grid View that allows you to set a default number of items to display per page. This preference is saved to your profile and automatically applied across all grids, eliminating the need to manually adjust the view on each screen.

For details, refer to Personal Preferences.

Assignment Links open Forms directly

When the Show Assignment Link property is enabled on an approval node or activity node in a form solution, the assignment link in the notification email now opens the forms directly for the form solutions.

Previously, the assignment link opened an information page, where you had to click Open to access the task.

Note: For Excel solutions, Task Detail screen remain unchanged.

For details, refer to Approval Node Properties and Activity Node Properties.

Asynchronous bulk reassignment

Two new workflow configuration keys are available to support asynchronous bulk reassignment of tasks and processes:

  • BulkReassignmentAsync: Enables asynchronous bulk reassignment flow. When enabled, a background job is created immediately and processes the reassignments asynchronously. Users receive a notification when the job is complete.
  • BulkReassignmentMaxConcurrentJobs: Defines the maximum number of bulk reassignment jobs allowed to run concurrently.

For details, refer to Workflow Configuration Options.

CSV support for Start Excel Process API

The Start Excel Process API now supports a new {APIRoute}/csv endpoint that accepts a Base64-encoded CSV file and converts it to Excel internally before starting the process.

For details, refer to Start Excel Process API.

MCP Server support

Automate Evolve now includes a built-in MCP Server that exposes Evolve workflows, SAP OData APIs, and Automate Studio scripts as tools for MCP-compatible AI clients. Any AI client that implements the Model Context Protocol can connect to the Evolve MCP Server to interact with Evolve processes and data.

The MCP Server supports three tool categories:

  • Studio script tools: Expose RFC, Fiori, or GUI HTML Automate Studio scripts from a library of type SAPAPIStore as MCP tools. Input mapped fields become input parameters; log and output fields become output parameters.
  • SAP OData API tools: Expose SAP OData APIs (Fiori gateway) as MCP tools for GET operations without requiring individual Query Scripts. Write operations are disabled by default.
  • Evolve tasks and processes tools: Enable MCP clients to query and act on assignments, processes, and documents in Evolve. Tools include GetAssignments, GetProcesses, GetDocuments, CompleteAssignment, TaskReassignment, CompleteProcess, and Start Form Process.

Tools are assembled using a configured LLM connection, which generates tool descriptions automatically. Assembled tools are visible and manageable in Operations > AI Tools.

For more information, see Evolve MCP Server.

For installation instructions, see MCP Server installation.

Third‑party software support

Added support for S/4HANA Public Cloud 2608.

Fixed issues

  • LDAP queries did not run when using LDAPS (port 636).
  • In the Set Duration dialog, the placeholder text displayed Enter days instead of Enter minutes.
  • In Form Designer, using the Move Up and Move Down buttons to reposition checkbox fields in multi-view forms caused an unexpected error.
  • Non-mandatory dropdown fields using a data connection as the data source displayed duplicate values when switching to a translated language.
  • In the Scheduler list view, page 2 and higher did not appear when the number of scheduled jobs exceeded the default page size.
  • In the Precisely classic theme, log settings buttons did not display text labels, and an unnecessary scrollbar appeared in the side navigation.
  • When searching for users to import through Active Directory lookup in a SAML-authenticated environment with Azure, an unexpected server error was displayed.
  • When multiple Evolve browser tabs were open simultaneously, an unable to update: entity already exists error was displayed.
  • Active Directory group synchronization failed when AD groups were assigned to a portal, and email notifications for groups with multiple members contained empty addresses.
  • When importing a solution, an error occurred if the APIFields table already had 999 or more sparse indexes.
  • Documents with special characters, spaces, or very long file names in form links did not appear in the document queue.
  • In an Excel workflow, the SAP attachment script (FB03) using GUI for HTML with a service account failed to attach documents.
  • When configuring a Salesforce API connection, the hostname was appended twice in the request URL, causing API calls to fail.
  • When upgrading Evolve, the upgrade failed with a DACPAC error when the route field had a varchar limit below 2048.
  • When archiving processes, form load rules were not executed before the screen image was generated, causing dynamic content to not be rendered in archived form images. The generated screen image was also zoomed in, making repeating table columns unreadable.
  • In the group assignment panel, the scrollbar was missing when the group list exceeded the visible area, preventing users from reaching the Save and Cancel buttons.
  • After a SAML session timeout, a connectivity error was displayed instead of redirecting users to the home page.
  • In a Microsoft Azure environment with a GCC High tenant configuration, user lookup failed because the GCC High resource URL was not used to build the Azure graph client.
  • Scheduled jobs were stuck in Not Started status and were not picked up by the scheduler.
  • When a button had both a collapse rule and a reject rule, clicking the button triggered mandatory field validation errors for fields that were already collapsed.
  • In form solutions, the OK button in confirmation pop-ups had low text contrast, making the label difficult to read.
  • When running an AD sync job with Azure Entra ID, manager details were lost for users after synchronization.
  • Document search did not return results for solutions that had custom columns.
  • Special characters in workflow comments were displayed as encoded or numeric values in the Process History.
  • After upgrading from version 25.0, columns in lookup controls within form solutions could not be resized.
  • When exporting document lists to Excel, the Status column displayed internal numeric values instead of user-friendly status text.
  • Updating a Reference Data List (RDL) from Excel add-in or Studio failed instead of updating successfully.
  • Publishing a Google Sheet from a shared drive to Evolve failed with an Object reference not set to an instance of an object error.

Known issues

  • In the Google Sheets add-on, execution logs may not be generated after a revised script is resubmitted, approved, and executed.
  • In the Google Sheets add-on, cross-linked scripts that use Macro functionality do not work for published or unpublished scripts.
  • In MCP Server, promoted fields returned by the Get Assignment, Get Process, and Get Document tools may display the API field name instead of the solution field name shown in the Evolve user interface.
  • When creating a manual Query Report, only the first 10 SAP servers are displayed in the server selection list.
  • When starting a form process through the MCP Server, default values for elements that are not included in the current view may not be displayed.