Release date: July 15, 2025 - 'Max Ordered Jobs (Tasks)', 'AVG Ordered Jobs (Tasks)' and 'Total Definitions' was added to the 'Defined Control-M Servers' sheet. (WBL-326612) Corrected Problems: - Qualifying large folders was not working when extracting the data using allowDuplicateFolderNames Control-M EM setting. (WBL-323457) Release date: July 2, 2025 What's new: - The migration tool now supports extracting global variable definitions from the On premise Control-M and deploying them to Control-M SaaS as pool variables. (WBL-323637) Release date: June 8, 2025 What's new: - The migration tool now supports migrating MFTE sites for a specific Control-M Server name. (WBL-320541) - The migration tool now support adding Daylight Saving Time to the Time Zone sheet in the Excel report. (WBL-325852) - The migration tool now supports extracting Global Variables from Control-M On-Premise, converting them to Shared Variables and deploying them to Control-M SaaS. (WBL-326059) Corrected Problems: - Migration of File Transfer Dual Connection profiles was failing when the Connection Profile contained the 'passphrase' attribute. (WBL-324006) - A misleading error message was being issued when the extraction of Control-M RunAs users was failing. (WBL-324718) - Deployment of Notification Destinations was failing when AAPI was returning the incorrect 'value' attribute in Console, Log and Alert destination types. (WBL-324072) Release date: May 16, 2025 What's new: - Jobs that run on agents with unsupported operating system are now reported in the Folder and Job issues sheet in the Migration tool Excel report. (WBL-319813) - 'Max. Daily Executions' and 'Average Daily Executions' was added to the 'Defined Control-M Servers' sheet. (WBL-320776) Corrected Problems: - The migration tool was unable to connect to Automation API in case the password contained a the equal ('=') character. (WBL-322400) - In some cases, Control-M Variable names with non trimmed space were being created. (WBL-317985) - In some cases, The Control-M server settings where not being properly deployed when using the migration tool in migrate/deploy mode. (WBL-324496) - Notification destinations were not being migrated properly when the notification value contained a an value with only spaces. (WBL-324072) Release date: April 15, 2025 What's new: - The Migration tool now supports a new mode to extract a predefined list of folders to allow data extraction after a migration project has begun. (WBL-306559) - Agents that run on unsupported operating systems were removed from the sheet Agents to Install in the Migration tool Excel report. (WBL-316896) Corrected Problems: - The Migration tool was not properly qualifying users with specific user permissions. (WBL-317466) Release date: March 23, 2025 What's new: - The Migration tool now supports extracting folder definitions in JSON format from Automation API with folder array structure when the EM option 'AllowDuplicateJobNames' is set. (WBL-307208) - The Migration tool now supports extracting and deploying Control-M roles with duplicate names by adding a unique suffix to the duplicated role names. (WBL-309928) - The Migration tool now supports qualifying if the EM statistics parameter STATISALG is used in the on premise Control-M. (WBL-251569) Corrected Problems: - Deployment of RunAs Users to Control-M SaaS was failing when a domain Run As User had the '\' character in it. (WBL-316873) - The EM Def usages qualification was not showing correct data about usages of EM Def in the on premise Control-M. (WBL-316141, WBL-316384) - Database queries to the EM Database that were being timed out were not being handled correctly. (WBL-316589) - In some cases, The daily execution in the Excel report was incorrect. (WBL-317271) - In some cases, the Migration tool was failing with the exception IllegalArgumentException. (WBL-316008) Release date: March 4, 2025 What's new: - The Migration tool now supports qualifying Enterprise Managed File Transfer can be migrated to Control-M SaaS when targeting Control-M SaaS V9.0.22.000. (WBL-305592) Corrected Problems: - The Qualification report was not differentiating between Control-M Agents on unsupported Operating System and Agents on incompatible or Unknown Operating Systems. (WBL-307930) - The Migration tool was not deploying variables in the Global pool that were detected in the Control-M On Premise job definitions. (WBL-312027) - The Qualification report was partially reporting on Self Service Rules. (WBL-313271) - LYBMEMSYM variable order was not being preserved when migrating Control-M jobs with LYBMEMESYM definitions. (WBL-311803) - Variables inside Control-M Embedded Script jobs were being migrated incorrectly. (WBL-313644) - In some cases, the LYBMEMESYM control file was not being validated properly. (WBL-311130, WBL-311075, WBL-311825) - All Shared variables were not being deployed when the HelixSharedVariables.json had one or more variables that have validation errors. (WBL-314963) Release date: February 12, 2025 What's new: - The Migration tool now supports deploying variables that were defined in the LIBMEMSYM control file as Pool variables to Control-M SaaS. (WBL-311985) Corrected Problems: - In some cases there was inconsistency in the Control-M folder count in the excel report. (WBL-307090) Release date: January 21, 2025 What's new: - Qualify if the source Enterprise Manager has roles with same name and different case. (WBL-308134) - Do not try to retrieve Application Integrator plugin definitions (.ctmai files) from Automation API if the Enterprise Manager version is lower than 21.200. (WBL-271187) - Qualify if any Automation API CLI command are being used. (WBL-283587) - Qualify if Pool Variables or Site Standards cannot be extracted due to Enterprise Manager version. (WBL-302127) Corrected Problems: - Retrieving daily job executions information from an Enterprise Manager with Oracle installation was failing. (WBL-308859) Release date: December 31, 2024 What's new: - The migration was failing when the Message field in a If-Notify Action contained a tab (\t) character. (WBL-304855) - The number of successfully deployed entities was added to the Migration Report Excel file. (WBL-255696) Corrected Problems: - Incorrect connection profile were being created when migrating Application Integrator job types. (WBL-306768) - The Migration tool was quietly ignoring failures to extract Local Connection Profiles when the agent version does not support extracting them. (WBL-304552)