Automation Co-Pilot for Business Users v.40 release - Review what's new and changed and the fixes and limitations in Automation Co-Pilot for the v.40 release.

This enhancement delivers a consistent discovery and launch experience, enabling business users to interact with AI Agents in the same streamlined manner as Processes.

Goal-based agents in Automation Co-Pilot

Real-time in-progress indicators are now added for API Tasks triggered by dynamic form rules. Users can now see visual feedback (For example, spinners, busy states) on buttons and form fields when background API Tasks are executing, including cascading updates across multiple elements. The affected fields are temporarily disabled during processing and automatically re-enabled upon completion. This enhancement improves transparency, reduces accidental interruptions, and ensures more predictable form interactions during asynchronous operations.

Test Process (API Task in process)

Service Cloud Case ID: 02304723

We have introduced a new Styles tab in the Form Composer, enabling developers to directly customize form appearance using CSS. This enhancement provides greater control over layout and styling, allowing you to meet advanced branding and UI requirements beyond standard visual editing capabilities.

Add custom style to a process automation

Conversational Co-Pilot now includes an Answer mode selector that gives users more control over how requests are handled. In addition to the default Auto mode, users can choose Action to run automations, Company knowledge to search enterprise content, or General knowledge for model-based responses. This enhancement helps users direct requests to the most appropriate source within the conversational experience, ensuring greater transparency and control when Auto selection is not the preferred option.

Select an answer mode

Team managers and administrators can now assign or reassign multiple tasks at a time directly from the Tasks page in Co-Pilot Web. This enhancement streamlines task distribution during peak processing periods, reducing manual overhead and operational bottlenecks. Delivered in response to customer feedback, the feature is expected to significantly improve workload management efficiency and reduce labor waste associated with manual task reassignment.

Assign multiple tasks

You can now view the Amazon Q sync status of each file directly within the AI Knowledge file table. A new Sync status column displays whether a file is Synced, Not synced, or Failed, enabling users to quickly verify indexing status and identify files that require attention. This enhancement improves operational transparency for Amazon Q indexing and allows knowledge managers to quickly detect incomplete or failed ingestions, troubleshoot issues, and maintain reliable search results within the knowledge base.

Manage AI knowledge base for Automation Co-Pilot

Standardized date display across Co-Pilot Embedded and Assistant to use the named month shorthand format, aligning with Co-Pilot Web. Dates on Activity history, Assigned and Requested tasks pages now appear as MMM DD YYYY (For example, Mar 8 2026), replacing the ambiguous numeric MM/DD/YYYY format.

Automation Co-Pilot business users can now create and organize multiple independent conversation threads, making it easier to handle several topics without losing context in ongoing discussions. You can start a new conversation for each topic, switch between threads, and archive or delete threads you no longer need. Each new thread is automatically named using the opening words of its first message, and the chat history displays each thread's last activity time as a relative date (for example, "5 minutes ago"). When a thread receives a notification while you are working in a different thread, the chat history marks it with a New indicator so you can see which conversations have updates waiting.

Conversational automation with Automation Co-Pilot | Multiple conversation management

We have introduced granular request visibility controls for multi-team processes in Co-Pilot, enabling organizations to restrict access to only those users directly involved in a specific request. With this enhancement, process steps can be assigned across private teams while ensuring that users only see requests they participate in, with continued visibility retained if they were involved in earlier stages. Administrators and process owners maintain full oversight of all requests, ensuring governance without compromising data privacy.

Request visibility in multi-team processes

1. Create a form with a Checkbox group element and set default values.
2. Create a Task Bot with list and dictionary output variables.
3. Create a process, add the Task Bot and an Approval task, and assign the created form.
4. Map the list and dictionary variables to the checkbox group in the approval task.
5. Save and run the process.

The Checkbox group elements in the approval task now correctly retain the dynamically mapped values after task submission, rather than reverting to the form’s defaults.

Previously, the inline notification in the Conversational interface was replaced with a static Automation launched successfully message after a page refresh.

Previously, users encountered an error message after submitting a Learning Instance (Document Automation) process with file inputs directly from Automation Co-Pilot chat.

Previously, users opening a form task notification in Automation Co-Pilot would initially see only a partial form, requiring manual scrolling to view the full content.

Previously, some chat messages were not displayed if users submitted multiple prompts in quick succession before receiving a response in Automation Co-Pilot Assistant.

Previously, in the Conversational Assistant where forms with fewer elements rendered within a fixed half-height container in the right pane, leaving the lower section blank and positioning the Submit button midway on the screen.

Previously, pagination controls were not visible on the Recycle Bin page after deleting a large number of requests.

Previously, file upload using File type input variables was not working correctly with public process in Automation Co-Pilot.

Previously, forms containing elements marked as hidden were incorrectly rendered as visible in the chat assistant right pane during automation execution.

Previously, certain tables retrieved through Conversational Assistant (RAG responses) were not rendered correctly in the chat interface.

Previously, users encountered an error message after submitting a learning Instance (Document Automation) process with file inputs directly from Automation Co-Pilot chat.

Previously, the IsEmpty validation rule was not triggered when a TextBox field was programmatically reset to its default (empty) value through a rule action (For example, using button click).

Previously, only selected value is getting displayed on approval task.

With this fix, the Approval task now correctly retains and displays the dynamically mapped Dropdown Multi-Select selections after the Form task is submitted.

Previously, when you created a form with a RadioButtonGroup containing default values and used that form in a Bot task or Approval task, mapping list and string output variables (from a Task Bot or process inputs) to the Available and Picked option fields did not work as expected. After running the process, the RadioButtonGroup continued to show only its default values and ignored the mapped inputs.

With this fix, the RadioButtonGroup now correctly displays the mapped list and string values during process execution.

Previously, when you created a form with a Dropdown containing default values and used that form in a Bot task or Approval task, mapping list and string output variables (from a Task Bot or process inputs) to the Available and Picked option fields did not work as expected. After running the process, the Dropdown continued to show only its default values and ignored the mapped inputs.

With this fix, the Dropdown now correctly displays the mapped list and string values during process execution.

Previously, users encountered failures when starting such automations, or requests were created without loading the required initial form.

Previously, users were unable to view long comments properly in the approval task.

• When the form is in read-only mode.
• After the form step is completed.
• When the RTE element is non-editable, even if the form is in a pending state.

Previously, hyperlinks rendered within RTE elements were not actionable in the Microsoft Teams Co-Pilot environment.

Previously, unsent file attachments in the input area persisted when users switched to another conversation thread or created a new one.

Previously, Orchestrator quartz background jobs could fail continuously after updating due to NULL values in the invocation_source_id field for pre-existing orchestration records, causing workflow reconciliation, expiry checks, and deployment status checks to stop processing.

Previously, users encountered submission errors while running public processes in V1 and V2 when Record variables with Window or Credential sub-types were rendered in the initial step form. In some scenarios, failures occurred only when the variables were selected.

Previously, users did not receive assignment notifications in chat under this scenario, although notifications worked correctly in other cases.

Previously, Bot IDs were displayed in chat during multi-turn automation execution flows when users attempted to run recommended automations.

Previously, the meta.assignedTo.id variable returned an empty value when mapped to form task inputs, preventing assigned user details from being displayed in processes.

Previously, in the Process editor where the Remove items action from the toolbar did not fully update the workflow layout. When deleting a Form task, connector lines were incorrectly retained due to automatic edge re-connection during layout rendering.

Previously, the first attempt to upload a file using a Select file field in an Automation Co-Pilot form could fail without displaying an error. Users had to refresh the page before they could successfully upload a file.

Workaround: Set the target time in the IF block to 12:00 AM to avoid encountering this issue.

Service Cloud Case ID: 02211874

Workaround: To fix this issue, use the original variable mapped in the Approval step such as$list_string_avail$), instead of referencing the Approval input as $&Approval{input}{MultiSelectDropdown0}$.

Workaround: Explicitly include target="_blank" in all the anchor tags within the HTML content.

In the Co-Pilot Admin interface, users might be unable to create a new tag if it is a sub-string of an existing tag. For example, if a tag such as document-automation already exists, attempts to add tags like document, automation, or auto will fail.

In Conversational Automation, users might still be able to interact with recommended automation and access archived chat threads after license consumption limits have been exceeded. This can allow limited interaction with automation listings and conversation history even when the license is over consumed.

Workaround: Refresh the browser page and reopen the chat session if the issue occurs.

Workaround: Navigate to the first page before applying the filter, or increase the number of tasks displayed per page to 400.