Automation Co-Pilot for Business Users v.37 release
- Updated: 2025/09/17
Review what's new and changed, and the fixes and limitations in Automation Co-Pilot for the v.37 release.
What's new
| Human-agent collaboration with
conversational automation interface Transform the way work gets done with the conversational interface of Automation Co-Pilot. This new capability unifies fragmented knowledge access and workflow execution into a single, intelligent experience, available as standalone or embedded in any application. With simple natural language
prompts, users can now retrieve accurate, source-linked
information from across enterprise systems and documents,
and trigger automated processes; reducing manual effort,
accelerating outcomes, and improving productivity. Key
capabilities include:
|
Form Builder updates New options have been introduced in the Advanced behavior section of the Rich Text Editor property panel in Form Builder to enhance the chat interface experience for Form Builders and Business users. These options include:
|
What's changed
| To help users avoid displaying incomplete messages in a saved
End point: End Process step in Process Composer, the following
new help text has been added:
Service Cloud case ID: 02138056 |
Fixes
|
Approver users who were given the Automation Co-Pilot Admin role saw an incorrect assignment drop-down list on task forms. The list showed members of the Approver's team, even though the task was already assigned to the request creator. This problem has been fixed. Now, Approvers should only see the task form according to their visibility rights via the Automation Co-Pilot Admin role. There should be no assignment drop-down, ensuring clarity and proper task ownership. |
|
Customers could not see the following columns in the
Co-Pilot Request View and the
Co-Pilot Task View screens:
Created,
Updated, and
Tags. These fields used to be
visible but were not showing up anymore. The problem was due
to different date formats coming from the backend. One
format, ( Service Cloud case ID: 02228925, 02229740, 02229695, 02229824, 02229156, 02230150, 02229824, 02229156, 02231350, 02233027 |
|
Some customers reported they could not open existing Automation Co-Pilot
processes in edit mode after updating to Automation 360 v.37. When
they tried to open them, it took about 20 minutes and then
failed with an error. New processes created in the same
version were unaffected. The problem was due to a missing
attribute ( Service Cloud case ID: 02224980 |
|
Some Cloud and On-Premises customers saw an error message, Unexpected problem occurred, when they tried to view or edit certain processes. This issue stopped the affected processes from opening correctly. We have fixed the conversion logic to make sure Step Override variables are detected properly. Now, the affected processes open successfully in the Editor without any errors. Service Cloud case ID: 02226489, 02229872 |
| Administrators can now increase
the knowledge base index capacity to the maximum purchased units
in the interface. If the capacity is updated through API, the
interface now correctly reflects the available value when
edited. Previously, the interface allowed only one-unit increment, and the plus button was disabled thereafter, preventing users from setting the full licensed capacity. |
|
When you use an embedded automation with Automation Co-Pilot, and click the Open in new window button, the new window now correctly opens the initial task form instead of going to another window. |
|
When an initial Form's element variable was mapped to the next Form's task element, the Form's element's label was missing in the Form's step. This issue has been fixed, and now all labels are visible. Service Cloud case ID: 02213709 |
| When third-party storage partitioning was turned on for embedded deployments where Co-Pilot was accessed using the using Co-Pilot Chrome Extension or directly embedded into applications such as ServiceNow or Salesforce, the action of opening the task in a new window did not always work right. This happened if the Local Storage was on a different domain. Users might have noticed behaviors such as the navigation would not advance to the next step in a process, or the window might crash. Now, opening a new window works correctly. |
| As part of the Co-Pilot use
case lifecycle involving command-based file uploads, the upload
begins with a bot waiting in a queue. Sometimes, a background
job that cleans up storage might start while the bot is waiting.
This can lead to the file's metadata being deleted too early,
before the upload is complete. To fix this, the metadata
expiration time for Co-Pilot storage requests has
been extended from expiring immediately to lasting 24 hours.
This change makes sure the metadata stays available during the
entire upload process and stops requests from getting stuck in
the In-Progress status. Service Cloud case ID: 02151231 |
| When you access Automation Co-Pilot on the web as an Admin, you can now see the User group column in the Requests tab. Before, the User group column was not visible in the Requests tab. |
When you access Automation Co-Pilot on the web to create a new process
with a table:
|
|
When an HTTP package head request is sent to the package download server, the server connects, but it does not receive a response. This causes processes to stall or fail in Automation Co-Pilot. To prevent processes from waiting indefinitely when the package download server is down, an extra sixty seconds and three retries have been added for each package head request. Service Cloud case ID: 02183712, 02185699 |
| When you use third-party partitioning storage with the PixieBrix extension turned on, you can now move to the next step in the process flow on a Request Creation page. This happens when you click Submit from a new window. |
|
When using Co-Pilot integrated with PixieBrix, if you created a second user in the Control Room, it caused the existing integration to break. To avoid breaking the integration, the following was implemented:
Service Cloud case ID: 02001495 |
|
When you start a process using Automation Co-Pilot for the web, and the form includes a table element with several rows that have drop-down lists, the form rules now properly load the dependent drop-down values when the form is opened for the first time. Selecting a value from the parent drop-down list instantly updates the related child drop-down values as expected. Service Cloud case ID: 02192041 |
| Automation Co-Pilot now lists automations only for
users with a valid license when integrated within Salesforce.
The new window serves content from the same session, ensuring
that users without a valid Automation Co-Pilot license see a license error and a
logout button instead of accessing the automation
list. Previously, the new window served content from a different session that allowed an unattended Bot Runner user without an Automation Co-Pilot license to see the automations list in Salesforce. |
| When you run a
process, task step progress updates in Automation Co-Pilot now refresh
automatically upon successful completion in the new Teams
application, when switching between tabs while the process is in
progress (such as moving from Automation Co-Pilot to chats or calendar and
back). Service Cloud case ID: 02172040, 02216536 |
| When you map a Number or Table element to a field in the next task of a form, the values from these elements now show up correctly in their matching fields in the following task. This makes sure the automation works properly and gives the right results. |
Limitations
When running
multiple automations with forms that include a select file element
in conversational automation chat window, users can only upload a
file in one automation at a time.
Workaround: Submit the first automation after uploading a file to enable file selection in the second automation. |
| When you use
conversational automation in Automation Co-Pilot and
click the default Recommend automations I can
run option, you might see only a limited number of
automations listed even if multiple automations are published and
assigned to your team. Workaround: To access other automations, type the automation name directly into the chat prompt. |
| When you refresh the
page after initiating a file sync in the AI
Knowledge page of Automation Co-Pilot, the Sync files option might become
enabled even though the sync is still in progress. As a result,
users might be prompted to start the sync
again. Workaround: Do not refresh the page while a file sync is in progress. Please wait until the sync completes before performing any additional actions. |
| When a user with the
Manage AI Knowledge permission uploads
files to the AI Knowledge page in Automation Co-Pilot and clicks Sync
files, the Sync files option
remains unavailable for a few seconds after the sync completes.
Workaround: Refresh the page manually to make the Sync files option available. |
| When a process is
assigned to a team and you navigate to the embedded interface
(/copilot) of Automation Co-Pilot page, the
Automations tab does not display the
assigned automations to the user with AAE_Robotic
Interface User role , even if the user is part of
the same team. An error message is shown when the
Automations tab is
accessed. Workaround: To view the assigned automations, contact Automation Anywhere Support. |
|
An issue affecting some Automation Co-Pilot processes became more noticeable for users updating to Automation 360 v.37. In earlier versions, when remapping bots and forms in a process, only the last remapping was saved, while previous re-mappings during the same edit session were not kept. Workaround: To fix the issue, manually remap all affected bots and form references in your Automation Co-Pilot processes. Once these re-mappings are completed and saved in Automation 360 v.37, the issue will not happen again for those processes. Make sure to check all process dependencies after remapping to ensure they are correct. Service Cloud case ID: 02225314 |
|
Customers cannot export Tasks from the Document Automation
interface right now. When users click the
Export link (after seeing a
Success notification), they are taken
back to the Tasks page instead of downloading the expected
This problem happens when there are more than 1000 task records. If there are fewer than 1000, the download works fine. Service Cloud case ID: 02223778 |
|
When a process is triggered from Automation Co-Pilot that includes element values, the process is expected to capture the form element's values including the hidden variables and map them according to rules defined in Process Composer. After updating to Automation 360 v.37, the hidden variables are not being captured and pass for processing the process rules. However, this is limited to only the hidden variables in the form. |
|
If a new process has a form with a document element, and this element is mapped to a Select a File field in the form or to a file variable, you will see a mapping error for the document element after saving and reopening the process. Note: This problem does not happen during
the first run, when changing the process from the legacy Process Composer to the new
Next-Gen Process Composer,
or when the process is imported.
|
|
When you create a form with a number element and then:
|
| When you run an Input Variable based process using Automation Co-Pilot and try to upload a file using a file variable as the input, the file does not upload properly in Automation Co-Pilot and generates an error. |
|
After updating Automation 360 from a version earlier than 28 to version 36, existing forms are showing duplicate Submit buttons. In earlier versions, only process-level buttons were shown. But the newer version displays both process-level and form-level buttons, causing duplication. Workaround: To stop the duplicate button from appearing, enable the Make field hidden setting for the form-level button. However, if you have many forms, this workaround requires manual updates for each one, which can take a lot of time. Service Cloud case ID: 02211874 |
| When you map a form using variable mapping from a previous step in the process, the element labels disappear in subsequent and completed steps. While the data passes correctly, the labels do not display as expected for the elements. |
| When a hidden table element is made visible using form rules, it does not render at full width as expected. Instead, the table appears with incorrect width styling, instead of its default 100% width display. This issue only occurs when visibility is controlled with form rules. The table renders correctly without the use of rules. |
| Limitations from previous releases |
|---|
| When you check-in a bot to the folder with the name System, the bot version is not displayed correctly. |
| When you perform bulk package update for List
package, an Any variable
that is used as List, returns the
Undefined type. Workaround
|
| Currently, a user who
is logged in as an Automation Co-Pilot admin without
having an Automation Co-Pilot user license is prevented
from running or scheduling a process from a public workspace. A user
who has run or schedule permission and access to the folder of the
process should be able to run or schedule the
process. Workaround: Add the required license. |
| When a
user with access to process in the web application logs into Automation Co-Pilot within the Salesforce application,
logs out of the Control Room and logs in with a different user who
does not have a valid Automation Co-Pilot license, Automation Co-Pilot still displays the automations list
in Salesforce. Instead of showing a license error with a logout
option, the system displays content from the prior session, even
though the user has logged in with different credentials. This issue
occurs because the Automation Co-Pilot window is using
session data from the original session instead of refreshing for the
new login. Workaround: Disable the third party storage partition flag from the browser. See Automation Co-Pilot for Business Users FAQ. |
Updates to the interface
| Form Builder |
|---|
Two new options have been added to the
Advanced behavior section in the
Rich Text Editor property panel in
Form Builder, and Make field uneditable has been renamed
to Make field read-only:
|
