Review what's new and changed, and the fixes and limitations in Automation Co-Pilot for the v.38 release.

What's new

Document extraction now built into Process Composer

You can now seamlessly add Document Extraction directly into your process automation flows using Process Composer:
  • Design smarter, faster: Add document tasks right where you need them.
  • Stay flexible: Edit and update your extraction logic as your process evolves.
  • Save time: Eliminate complex integrations and get straight to automating.

Extraction can be done using Task bots (via Bot Runners) or Automation Anywhere Cloud Extraction Service. You can use Document Extraction as a native task in Document Automation generated processes to process data from invoices, forms, or unstructured documents (on any environment).

The following image shows how to access the new Document Extraction task:

New Document Extraction Task

Add Document Extraction Task to a process automation

Support for Calculate Element for forms

We have added support for the Calculate element for process forms. With this update, forms can now contain calculated values that can be displayed dynamically across all Automation Co-Pilot versions that use process forms.
  • Dynamic Formula Rendering: Forms used in Start, Form, or Approval steps within a process now fully support the Calculate element. This means formulas are automatically calculated and their results are shown directly in the form.
  • Field Type Support:
    • Number Fields: Numerical values are calculated and displayed based on the set formula.
    • Date Fields: Dates calculated using supported functions are now displayed.
  • Real-Time Calculation Display: When a request is created from a process that includes a Calculate field, the form will dynamically show computed values based on the formula logic set in Form Composer.

New Calculate element

Using the Calculate element

Enhanced resiliency feature for process-based bot deployments

We have added Resiliency settings to the Process Deployment configuration. This makes automations triggered by Automation Co-Pilot more reliable and able to handle problems better. This update enables Administrators control how bots deal with unexpected pop-ups.

Navigate to Process Setup → Edit Process → Deployment Tab to find the new Resiliency settings section.

The Pop-up handling Ignore unexpected pop-up check box is selected by default for all Task Bots in a process. When this option is selected, the task automation will ignore any unexpected pop-ups during the automation execution.

Resiliency settings - Pop-up handling

Configure deployment settings for process or bot task

Support for virtual desktop in Co-Pilot PiP mode

In addition to the current Virtual window mode, you can now run your attended automations using Co-Pilot in Virtual desktop mode with (picture-in-picture) PiP. This update offers more flexibility and security when working with Microsoft Office and other desktop applications during bot execution. You can have better control over how and where your automations run on the screen:

New Virtual desktop PIP mode

Note: PiP mode (including virtual desktop) is only available to users with a Co-Pilot license.
You can set up this option while the program is running using the Run-time options drop-down menu from:
  • Automation Co-Pilot Desktop Assistant
  • Automation Co-Pilot embedded

PIP drop-down options

How virtual desktop differs from virtual window

Feature Virtual window (PiP) Virtual desktop (PiP)
Session type Child session on same desktop Isolated new desktop session
Security context Inherits parent desktop security Independent desktop security context
Office integration May inherit DRM/permissions limitations Greater flexibility for saving, editing, exporting
Use case Basic interactions Advanced Office or secured desktop automation

Using virtual desktop for picture in picture

Support for new duration attribute value type in Process Composer

Create variables that display a duration using days, hours, minutes, and seconds. You can now easily work with time-based variables, giving you more control and accuracy when handling durations in automated processes. With built-in validation, you can set minimum, maximum, and step values to ensure duration inputs are within the expected range.

Saved task view preferences for Assigned and Requested pages

Automation Co-Pilot for Business Users can quickly find the tasks that matter most to them. With this update, your Assigned Tasks and Requested Tasks tab preferences will now be saved automatically for each user.
  • Assigned Tasks tab: If you select My open tasks, Automation Co-Pilot will remember your selection and automatically display only your open tasks the next time you log in.
  • Requested Tasks tab: If you select Requested by me, Automation Co-Pilot will remember your choice and show only the tasks you have requested by default.
With this enhancement:
  • There are fewer clicks and more focus. You can go straight to the tasks that matter to you without having to reapply filters every time.
  • You get a personalized experience because Automation Co-Pilot remembers your favorite view, making things more efficient.
  • No retraining is needed since both new and existing users can instantly see the most important tasks without having to search or filter manually.

Service Cloud case ID: 02094999

Deep linking for Co-Pilot pages and tasks

We have added deep linking to Co-Pilot. This enables you open specific processes, requests, or tasks directly from a shared URL without extra clicks. Before, clicking a link (for example, from Microsoft Teams, Slack, or email) took you to the Co-Pilot home page, and you had to find your task yourself. Now, deep links take you right to what you need.

  • Direct process access: Open a specific process form using a URL with its Process ID. You can also have form fields pre-filled from URL parameters.
  • Request and task targeting: Link directly to a pending task in a specific request, the latest task in a process, or a completed task for review.
  • Error handling:
    • If a link points to a nonexistent process: You will see a clear error message with a button to return to the Automation List.

      Error message with link

    • If a link points to a nonexistent request or task: You will see a clear error message with a button to return to the Task List.
    • If a link points to an unauthorized process or task: You will be redirected to the Automation or Task List.
  • Teams and collaboration tool integration: Links from Microsoft Teams, Slack, or email now open directly in the right Co-Pilot page, keeping context and saving time.

Embed automations in your application using Automation Co-Pilot

Case view enhancements for agentic process automations

We are introducing new features in case view that bring more clarity and flexibility when working with AI Agents and processes.

  • AI Agents now support a new task type called Human in the loop: This step allows an AI Agent to pause execution and ask for human input before continuing. This ensures that humans stay in control at key decision points, making AI Agents safer, more transparent, and collaborative.

    Human in the loop task

    Task visibility:
    • Completed Human in the loop steps are displayed like Form tasks.
    • Planner tasks remain hidden by default (admins/creators can unhide them if needed).

    AI Agent

  • For all Requests and Recycle Bin pages, we have improved how processes and AI Agents are managed:
    • A new Type column has been added that clearly shows whether an item is a Process or an AI Agent. It supports filtering and sorting for quick access.
    • The Process column has been renamed to Name for consistency.

    New Type column added

What's changed

Improved accessibility in Automation Co-Pilot for embedded applications

To align with modern accessibility standards and enhance usability, we have increased the visual spacing between bots and their associated actions in the Automations list when using Automation Co-Pilot within embedded applications. This update makes it easier to navigate and interact with automations, providing a more comfortable and accessible experience for all users.

Business attributes now available to all customers

We have made it easier for you to take advantage of Business Attributes in Automation Co-Pilot for web. This feature no longer requires an Enterprise Platform license—so now, it is available to all our customers. Whether you are using:

  • On-Premises

  • Cloud

  • Community Edition

You can now start using Business Attributes right away to streamline your automations and improve data consistency across processes. Enjoy broader access and greater flexibility, with no extra setup required.

See Understanding business attributes in Automation Co-Pilot

Override input variables for API Task in GoTo endpoint

Process builders can now override input variables for API Tasks when using the GoTo endpoint. This makes it similar to Bot tasks.

Override input value of the target task

Before, the GoTo endpoints allowed changing input variables for tasks like Bot, Form, Approval, Document Extraction, and Process. If an API Task was chosen, the option to override was not available. This improvement lets builders pass contextual inputs to API Tasks using the GoTo node, making design more flexible and reusable.

Step completion time visible in Process View

We have added back the completion date and time for each step (after it is marked complete) in the Process Step View. This feature was designed to keep the user interface simple and easy to read, without adding clutter. It helps teams see how long each process step takes, providing valuable transparency and traceability. This offers:
  • Enhanced auditability: Easily track when each step was completed.
  • Improved resource allocation: Find bottlenecks and make your workflow based on real completion times.
  • Better team insights: Give your team more visibility into execution timelines.

To adjust the view of the completion date and time in the Process Step View, drag the sliding scroll bar left and right:

Sliding scroll bar for completion date and time

Fixes

In earlier versions, the Open Folder button in the Interactive Forms Folder Element did not have enough space between the icon and the text next to it. This made it look messy and hard to read. Now, there is a clear and even space between the icon and the text, making it easier to read.

Interactive Forms spacing for Open folder
When you create a form with a Number element in Automation Co-Pilot for desktop, numbers longer than 15 digits did not show correctly. This issue occurred even if comma separation was enabled. Now, if the number is more than 15 digits, it will be rounded to the nearest 15-digits precision for desktop forms.
Previously, when a rule was applied to set the value of a Rich Text Editor (RTE) element, the editor content was updated correctly, but the focus did not automatically scroll to the bottom of the content. Instead, the scroll position either remained static or stayed at the top, leading to potential confusion. The editor now correctly auto-scrolls to the bottom, improving visibility and alignment with expected behavior during dynamic content updates.

If a user added a long Element label (for example, a label with more than 200 characters and no spaces) to a form, the label text did not wrap and got cut off visually in both the Form Composer canvas and during form rendering from the process. Now, a label longer than 200 characters without spaces wraps correctly to the next line or is truncated.
A horizontal scroll bar was unnecessarily appearing at the bottom of the Create Request page in the Automation Co-Pilot for web interface. This occurred when users created and attached a form to a process and executed it, leading to overflow behavior and a degraded user experience. The horizontal scroll bar no longer appears.
In Automation Co-Pilot iframe integrations like Salesforce, users could not use hidden variables. When form data was sent using postMessage, any hidden variables in the form were not being passed, which led to incomplete data transfer to the Automation Co-Pilot platform.

Now, the way postMessage data is handled has been improved to make sure hidden variables are correctly parsed and included in the form submission payload. Hidden variables now stay as expected when working with embedded Automation Co-Pilot forms.

Service Cloud case ID: 02222829
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 uploaded a file larger than 4 MB to a form in Automation Co-Pilot, multipart temporary files were created in the Control Room Server's temp file location (C:\window\temp or appdata\temp). This caused the Server's disk space to fill up. Now, these multipart files are automatically cleaned from the temp file location, preventing the Server disk from filling up.

Service Cloud case ID: 02171128

Bot deployments stop trying if the input size is greater than 5 MB (for example, 18 MB). They fail and show an error message in the audit log. This enables future bot deployments to work without problems.

Service Cloud case ID: 02193652
When you run a process with a form that includes either:
  • An image name with Japanese characters.
  • An image file located in a folder with a Japanese name.

The error message: The requestURI was rejected because it can only contain printable ASCII characters no longer appears, and the process runs correctly.

Service Cloud case ID: 02204813

When a form is part of a dependency for a parent bot or process, you can now choose an earlier version of the form to check out without causing an error. Before, an error would occur saying the previous version could not be checked out, and you should contact the admin if the issue continued.

Service Cloud case ID: 02211884
After you create a form and add the image component to create a process, any image with a large width or height that was linked to the form will be fully visible when you run the process. Previously, part of the image was hidden or cut from view in the form.

Service Cloud case ID: 02210232
When the Control Room language was set to anything other than English, the User Group page under Automation Co-Pilot kept refreshing over and over when the deployment resource was empty. This made the page unusable for non-English users when setting up the default deployment resource for an Automation Co-Pilot process. Now, users can choose a default deployment resource even if the Control Room language is not English and the User Group page stays stable no matter the language setting.

Service Cloud case ID: 02222784

Customers can now export Tasks from the Document Automation interface and obtain the assigned task data for offline processing or reporting. Before, when users clicked the Export link (after seeing a Success notification), they were redirected to the Tasks page instead of downloading the expected .CSV file.

Service Cloud case ID: 02223778

If a new process includes 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 no longer see a mapping error for the document element after saving and reopening the process.

Note: This issue did not occur during the first run, when transitioning the process from the legacy Process Composer to the new Next-Gen Process Composer, or when the process is imported.
When you click a hyperlink element in a web form (set up with a valid URL), it used to open in two separate browser tabs instead of just one. This problem has been fixed. Now, hyperlinks in the Web Form Renderer will open in a single browser tab as they should.

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.

Before, users could not run a process if a form had a date element with a default value that was mapped between steps. The process would fail when the date element was mapped with a default value. This problem is now fixed. Users can now run processes smoothly, even when the form’s date element is mapped with a default value, mapped with a variable, or left unmapped.
The Sync files option in the AI Knowledge page of Automation Co-Pilot now remains unavailable until the file sync is complete.

Previously, if users refreshed the page while a sync was in progress, the option would become enabled even though the sync was still ongoing, that could prompt users to start the sync again.

The Sync files option in the AI Knowledge page of Automation Co-Pilot now becomes available immediately after the sync completes.

Previously, the Sync files option remained unavailable for a few seconds and required the user to refresh the page manually.
When you use conversational automation in Automation Co-Pilot and click the default Recommend automations I can run option, you can now view the top 10 automations that are published and assigned to your team. Additionally, typing the automation name in the chat prompt will display the specific automation as expected.

Previously, only a limited number of automations were displayed, even if multiple automations were published and assigned to your team.

Limitations

When using an Automation Co-Pilot Task: Form with rules on drop-down fields, you might notice some problems:
  • If a drop-down has a default list of items, the rules (such as show/hide logic) work fine.
  • If a drop-down gets its list of items from input, the rules might not work right.
  • This problem is more obvious with big drop-down lists (like 400+ items), where setting all values by default is not practical.

Rules might not work when the drop-down is filled with items from input.

Service Cloud case ID: 02202529
When you type a prompt in the Automation Co-Pilot Assistant tab, select text within the prompt, and press the Enter key, the application crashes. Submitting the prompt using the Send button works as expected.

Workaround: Use the Send button to submit the prompt instead of pressing Enter while text is selected.

When you use a list of strings to set the selected options for a Checkbox Group form element, it does not work properly. The Checkbox Group needs a Dictionary<Boolean> structure. In this structure, each key is an option, and the Boolean value shows if it is selected. Right now, if you pass a List<String> directly to the Checkbox field, it will not automatically change into the needed dictionary format.

If you pass a List variable directly as the selected options for a Checkbox Group or Multi-Select Drop-down, the options do not get selected correctly when the process runs. You will not see an error message, but the form will not show the pre-selected values you expect.

Workaround:
  1. Create a List<String> variable with the options you want to pre-select.
  2. Use the .Form:toCheckboxPickedOptions utility method to change the list into a dictionary.
  3. Pass this dictionary as the selected options input for the Checkbox Group.
Limitations from previous releases

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
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.

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 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.
When you create a form with a number element and then:
  • Add a form rule using the less than (<) condition for the number element.
  • Set an action to show warning message if that condition is met. For example: If number < 18, then show warning message.
  • Save the form.
  • Create a process, attach the form, and run the process.
If you enter a number greater than the number set in the less than (<) condition (for example, 20), the warning message displays. The warning message should not display.

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.

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.
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.
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.