Automator AI v.42 release - Review the what's new in Automator AI for the v.42 release.

When you prompt for a process with Co-Pilot for Automators, the system now automatically creates and links a placeholder automation for any node that is missing. The new automation is named uniquely based on the task, and its input and output variables are pre-mapped to match the process.

Co-Pilot for Automators now generates Python scripts for API Task using only libraries supported by the Cloud execution environment. The Python package does not bundle its own runtime. Instead, scripts execute on Automation Anywhere managed Cloud Service containers, which provide the runtime and a curated set of pre-installed libraries. Generated code references only these validated libraries. This prevents unsupported or arbitrary imports and ensures scripts run reliably.

Co-Pilot for Automators can now leverage event triggers when creating a process in Process Composer. Event triggers were introduced in Process Composer with the .40 release. Previously, Co-Pilot for Automators did not incorporate these triggers during process generation. Now, generated processes can start automatically based on a selected trigger event, aligning process creation with the triggers already available in Process Composer.

Co-Pilot for Automators recognizes phrases that imply parallelism, such as at the same time or simultaneously, and generates the corresponding parallel branches. If the intent is ambiguous, Co-Pilot asks for confirmation before committing. Every parallel branch includes a defined join point where the workflow synchronizes before continuing.

Co-Pilot for Automators now supports the UI Agents package for browser-based automation. Using a slash command, users can describe a browser task in natural language, and Co-Pilot generates a three-action workflow: Start Session, Run, and End Session. The Run action is pre-filled with the starting URL, goal, and output file path. This is restricted to task automation.