Review what's new and changed, and the fixes and limitations in Automator AI for the v.35 release.

What's new

Automator AI settings and permissions available to enable features.
  • Settings are available for admin to enable and disable features (Co-Pilot for Automators and Autopilot) for tenants. Configure Settings
  • Controls to permit access to Automator AI features are available by role permissions. Administrators can configure roles to have access to each feature individually: Co-Pilot for Automators and Autopilot. This supports business needs when allocating a specific workforce with generative AI capabilities. Feature permissions for a role

What's changed

Co-Pilot for Automators is more resilient when generating outputs of a prompt for a process, separating any insufficient input and continuing to render sufficient instruction.

When processing instructions for a scenario, Co-Pilot for Automators generates the output of any sufficient instructions and informs the user of remaining unsuccessful instruction. As a result, you can now interact with Co-Pilot in an iterative style of prompting.

This experience improves collaboration, and it is particularly helpful when entering sophisticated prompts and multiple inputs. Previously, if some instruction was unsuccessful due to a missing entity, the whole prompt was treated as unsuccessful and required a new attempt for a single error.

Additionally, response messages from Co-Pilot now detail the lines in the automation that have been added or updated. Response messages from Co-Pilot for Automators

Example: In the following, the Valid_form file exists and the Invalid_form does not exist. Co-Pilot adds both nodes, but only the Valid_form file is attached, and the user is alerted to the discrepancy.

Prompt: Add the form "Valid_form", then add form "Invalid_form".

Result: Partial success. No match found for form "Invalid_form" in folder "Bots". Please review your automation and attach the file(s).

Enter key sends the prompt from Co-Pilot dialog box, enhancing key entry experience.

Users can send a prompt by simply pressing enter when the cursor is active in the Co-Pilot dialog box, in addition to the unchanged option of clicking the Send button. Previously, the enter key would add a line in the dialog box and CTRL+Enter would send the prompt. These key entry controls have now switched operations (CTRL+Enter adds a line), taking less effort to finish the prompt.

Transform your business process into process automation

Autopilot now transforms business processes identified through Process Discovery into process automation that includes a Task Bot. This enhancement helps you better organize your automations and derive maximum value from them.

Fixes

The operator output is generated reliably when using Co-Pilot for Automators to build if-else conditions in task automation.

Previously, the accuracy of the output was inconsistent.

Creating and mapping entities to a task in Co-Pilot for Automators works as expected.

Previously, editing or saving the process would automatically remove the mapped entities.

The generate automation action now successfully processes BPMN files containing special characters (such as \\, /, ?, |, *, <, >, \, and :) in BPMN objects.

Previously, these special characters would cause the automation generation to fail, requiring manual removal from the BPMN file.

Limitations

When Co-Pilot for Automators is enabled from the settings page and the role permission is not assigned, the user can still access capabilities in the Process Composer.

Updates to the interface