Fixed issues - 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-06-26
ft:lastPublication
2026-06-26T05:25:23.706000
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

  • Email approval was incorrectly approving tasks in version 24.0
  • Messages were not returned in the RUN LOG during BAPI execution, displaying only No message returned from SAP.
  • Archive jobs errored out when processing large number of documents.
  • Scheduled queries ran multiple times despite being set to run once, causing duplicate SQL records and data complexity.
  • Evolve form displayed an F12 error, blocking access to forms and process history.
  • Evolve form triggered an F12 error related to the Wait for Child process, preventing changes.
  • AD group synchronization failed with a given key was not present error when adding a new user and running the sync job.
  • The XK02 transaction was executed twice instead of once during the BDC script run, resulting in duplicate entries and errors.
  • The SAP lookup element in forms showed the same data in both the value and description columns for the purchasing group (EINE-EKGRP).
  • Archiving from version 24.0 was slow and did not archive all processes, leaving thousands of items in cost center, non-product billing, and internal order.
  • The Manage User plugin was able to add groups across apps however, it was unable to delete them.
  • An error occurred while opening a document link.
  • Validations were not triggered on the required fields that were hidden through rules.
  • The Manage User plugin failed to assign apps to users after a user was created in some apps and groups.
  • Query continues to reference original environment after exporting and importing query and reference list into new Evolve server.
  • Importing new users from Excel failed for usernames in non-email format.
  • The Evolve form triggered an F12 error, preventing any changes.
  • The offline activation was not working for some activation codes.
  • Incorrect Your portal access is updated email triggered when user was removed from the group.
  • Form fields appeared blank despite containing values in version 24.0.
  • The system performance degraded after upgrading to version 24.0, causing slowness form loads and high CPU usage.