Review what's changed in Automation Co-Pilot for the v.39 release.

What's new

LLM Responses in Co-Pilot toggle for Co-Pilot administrators

A newLLM Responses in Co-Pilot toggle has been introduced in the Administration > Settings > Automation Co-Pilot for Business Users to give administrators greater control over how AI-generated responses are produced. This setting allows you to choose whether Co-Pilot should rely solely on company-approved knowledge sources or also incorporate general model-based intelligence. This enhancement provides organizations with improved flexibility to manage response accuracy, governance, and compliance requirements.

Manage AI knowledge base for Automation Co-Pilot

What's changed

Customized table view in Co-Pilot web
You can now save and reuse your personalized table views in Co-Pilot web. Your column changes, including Business Attributes, resizing, and sorting, will now stay exactly as you left them even after logging out, switching browsers, or devices. Key enhnacements include:
  • Custom table layouts are automatically saved and restored across sessions.
  • Works for both Requests and Tasks tables.
  • The Restore option is now Clear all customizations, resetting your table to its default layout.
  • No impact on performance — just a smoother, more personalized experience.
Deep-link navigation to Automation Co-Pilot in Microsoft Teams

We have introduced seamless deep-link navigation that allows users to open Automation Co-Pilot embedded in Microsoft Teams directly from an URL. This update enables a more streamlined workflow for all the enterprise users. With this enhancement, you can now click a deep link containing a process request ID (for example, links of the form https://teams.microsoft.com/l/entity/...?...caseId=<ID>) and be taken straight to the waiting task (such as an approval task, a data input or review task) inside the Automation Co-Pilot within Microsoft Teams, automatically landing on the Co-Pilot view associated with the specific request.

Fixes

When a process uses a conditional Go to node to redirect back to a Form task, the selected values in a multi-select drop-down input are now retained. This fix allows that all types of dynamic and custom data are retained —regardless of whether the data originates from previous tasks (bot or form) or is provided as variables.

Service Cloud Case ID: 02285972
You can now complete and submit large forms without needing to re-enter information. The pop-up window now retains your entered data, and updates are submitted successfully without issues.

Previously, when submitting data in a task pop-up window, the window would sometimes minimize or close unexpectedly, causing all entered information to be lost. Additionally, if the session timed out while working on large forms in a separate window, an unauthorized error would occasionally be displayed.

Service Cloud Case ID: 02284788
When the Start node includes input variables, newly created variables also default to Input mode, ensuring consistent behavior.

Previously, Use as output was selected as the default, resulting in an inconsistent user experience.

Validation errors now clear correctly when users enter more than the minimum required characters in Rich Text Editor (RTE) and textbox fields, even when no maximum length is set.

Previously, these errors continued to appear despite meeting the minimum character requirement.
An issue where the Formula field allowed method names (such as sum, mul, div, sub, datediff, dateadddays, dateaddweeks) without any required number or date element is now resolved. The system now correctly prevents saving incomplete formulas, ensuring only valid expressions can be submitted.
When you select the customized table option on the Requests page in Automation Co-Pilot, the creator users no longer encounter an unexpected Access denied message. The system now correctly validates permissions, and the error no longer appears for authorized users.
Processes that use global variables within IF–ELSE conditions now execute successfully without run time errors.

Previously, such processes failed at run time after the initial submit when a global variable was referenced in an IF–ELSE condition, even though the process was saved, published successfully, and the request was created.
All check box options are now consistently displayed in subsequent steps.

Previously selected options are correctly shown as checked, while unselected options remain visible and unchecked, ensuring a consistent and expected form experience.
Font-size selections made in the form properties now correctly appear in both the Form composer and the rendered form.

Previously, font size changes were not applied to number field labels and values in forms.

The Automation Co-Pilot scheduler list now refreshes correctly on every attempt. The loading spinner clears as expected without getting stuck.

Previously, the loading spinner remained visible indefinitely when refreshing the Automation Co-Pilot scheduler list, specifically on the second refresh.
Submitting a form task that includes a table mapped to an input table variable no longer results in an intermittent blank page.

Previously, the form could become unrecoverable until the page was refreshed.
When opening a process that already has an assigned user group, the application no longer displays the Default user group required message for a fraction of a second.

Previously, this message appeared due to an incorrect evaluation of the loading state.
When the conversational automation feature flag is enabled but the required license is not available or has expired, repetitive error logs are no longer generated.

Previously, continuous error logs were generated in the Kloudfuse backend logs.
Users from any team can now successfully run a process from the chat window, even when the process is assigned to multiple teams and the user is not part of the default team.

Previously, if a process was assigned to more than one team and the user belonged to a non-default team, submitting the request in chat window of Assistant tab resulted in an error. Repeated attempts caused the same error, and clicking the submit form button could cause the chat window to crash.

You can now successfully submit form steps containing radio elements with custom variable mappings in the chat window. The radio element correctly displays variable-mapped options when the form is rendered, and the selected value is submitted as expected.

Previously, when a form step included a radio element mapped to a custom variable, the form would not submit if triggered from the chat window in the Assistant tab. At run time, the radio options reverted to the default values defined during form creation, instead of displaying the variable-mapped values. This caused a form validation error and prevented submission.

When you start a process from the Assistant tab that includes an approval step, the inline notification for the approval task assignment is now displayed correctly in the Assistant tab if that approval task step is assigned to logged in user.

Previously, the notification was not shown, which meant that the user automatically assigned to the approval step did not receive the expected notification within the Assistant tab.
When you run a process from the Assistant window that includes a Document Validator step, you now see a single notification in the chat window for each event.

Previously, duplicate notifications were sometimes displayed for the same event instead of a single notification.
You can now submit a prompt from the Automation Co-Pilot Assistant tab without the application crashing when you select text within the prompt and press the Enter key.

Previously, selecting text in the prompt and pressing Enter caused the application to crash, while submitting the prompt using Send worked as expected.
In the Automation Co-Pilot Assistant tab, the scroll position now remains unchanged while you compose a prompt, allowing you to easily reference previous chat content before submitting.

Previously, as soon as users began typing in the prompt field, the view would automatically scroll to the end of the chat window, interrupting the review of earlier messages.

In the Automation Co-Pilot Assistant tab, the task queries return accurate results based on the requested task status. You can now view only the completed or declined tasks when querying by status and task type in the prompt.

Previously, when users queried for completed or declined form, validator, or approval tasks, the response incorrectly included pending tasks assigned to the user.

The task status now remains consistent in the Automation Co-Pilot Assistant tab chat window when running automations, ensuring status consistency across all views.

Previously, when a task was in the queued state, it appeared as Queued in the Show Details view for the request ID, but changed to In progress when you clicked the task name in the chat window.

Automations configured to run By bot only no longer appear in the Automation Co-Pilot Assistant tab.

Previously, if an Automation Co-Pilot administrator edited a process in Manage > Processes and selected the By bot checkbox, the automation was still visible to users in the Assistant tab, even though it was not available in the Automation Co-Pilot Automation tab.
When you use form rules with the Dropdown element, the rule-based behaviors no longer fail during form rendering and form rules now work as expected.

Service Cloud Case ID: 02202529
Table elements now remain non-editable during approval, preventing unintended changes to form data.

Previously, table fields were allowed to be edited on the Approve task screen, even when the form was in read-only mode.
The form now correctly shows the default time when the value is directly passed from the bot to the form during process execution.

Previously, the default value of a Time input passed from a bot's date or time variable was not displayed in the associated form task.
Table rules now apply only to the specific row where the condition is met, and moving rows no longer trigger rule execution on other rows. Row movement behaves as expected without altering data or state in unrelated rows.

Previously, form rules within table elements were getting applied incorrectly when rows were moved up or down.
Underscores are now consistently displayed as spaces in the both Available and Selected column sections and in the table headers, and the formatting persists across page refresh and login or logout.

Previously, underscores were shown as spaces in the Available list but reverted to underscores after applying customization and refreshing.
The mandatory flag is now properly translated into input Required in variable mappings, ensuring users must provide the necessary inputs before submission.

Previously, mandatory fields defined in a form were not enforced as required when the form was used within a process.
The system now displays a warning message when an action is configured without an accompanying If condition, ensuring rule integrity and preventing invalid rule configurations in the form builder.
The file formats in the AI Knowledge → RAG Files table (formats such as PPT/PPTX, DOCX, XLS/XLSX, and XSLT) now appear with the proper, user-friendly labels instead of raw content-type values.

Previously, the AI Knowledge → RAG Files table displayed incorrect file formats.
The system now correctly supports Element IDs with spaces, ensuring AI Agent tasks run without errors.

Previously, AI Agent tasks failed to run when their default Element ID contained a space.

The Rich Text Editor (RTE) now retains its content, correctly displays the warning, and remains editable as configured. Rule execution and data passing for the same element now function as expected.

Previously, RTE fields could become blank and non-editable when bot-passed data triggered a not empty warning rule on form load.

Service Cloud Case ID: 02291662, 02291950, 02292058, 02292426, 02292446, 02292945, 02292733

Limitations

When you create a form with dynamic elements such as Checkbox, Radio Button, Dropdown and Dropdown Multi-Select, and add a button (named visible) along with a textbox, then apply an Is visible condition to the dynamic elements and set a rule to append their values to the textbox when visible, you might encounter the following issue:

When you add this form as the initial start step in a process, save, and run the process, clicking the visible button to display all dynamic elements does not result in their values being appended to the textbox as expected.
When you create a form with dynamic elements such as Checkbox, Radio Button, Dropdown and Dropdown Multi-Select, and add a button (named hidden) along with a textbox, then apply an Is hidden condition to the dynamic elements and set a rule to append their values to the textbox when hidden, you might encounter the following issue:

When you add this form as the initial start step in a process, save, and run the process, clicking the hidden button to hide all dynamic elements does not append the expected values to the textbox as intended.
Business attributes that contain spaces in their labels (example, biz attr) do not appear in the Available columns list on the both All requests and Tasks pages. As a result, these attributes cannot be added to the table for viewing.
When using a form rule that appends the value of a textarea to a Rich Text Editor (RTE), the text might be added twice instead of once. This occurs only when using the textarea’s element value.
When a process updates a request attribute during execution, the All requests page does not reflect the new value after the request completes. The attribute column continues to display the initial value.
When using a form with a multi-select drop-down element in a process, values selected in the Form task might not be passed to the subsequent Approval task, even when variable mapping is configured correctly.
When invoking goal-based agents with large input payloads (such as, extensive JSON passed into multiple variables), the Task page truncates the displayed data. Input fields expand vertically but remain fixed in height, preventing full visibility of the content. The layout does not adjust to available screen width, and no scroll option is provided, limiting user's ability to view complete input data.