Automation Co-Pilot for Business Users v.37 release
- 최종 업데이트2025/07/07
Automation Co-Pilot for Business Users v.37 release
Review what's new and changed, and the fixes and limitations in Automation Co-Pilot for the v.37 release.
What's new
|
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
| When using an embedded automation with Automation Co-Pilot, and click the Open in new window button, the new window might briefly display the embedded page before it opens the request creation page. |
|
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 |
| The request flow now
automatically focuses on the next step when navigating through
human task steps quickly after switching from the unified to the
old editor. Focus properly advances to the next step whether the
process is run from the unified editor or when switching between
editors. Previously, when navigating through human task steps quickly, the request flow did not automatically focus on the next step. |
Limitations
| When you run a 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. |
|
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:
|
