Automation Co-Pilot for Business Users v.39 release

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 new LLM 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

Real-time workflow visibility in Assistant through interactive process steps view

A new interactive process steps or task sequence view is now available directly within the right pane of the Assistant tab, giving business users real-time visibility into workflow progress without leaving the conversation. Users can now see all workflow steps—along with their status, assignee, timestamps, and related metadata—and seamlessly switch between individual task forms and the full workflow overview. The view updates automatically as the workflow progresses, improving clarity, reducing navigation friction, and enhancing overall user experience within the Assistant.

Visibilité sur le flux de travail intégré

Automation Co-Pilot modern conversational experience

We've introduced a completely redesigned Automation Co-Pilot conversational interface, delivering a faster, more intuitive, and GenAI-powered assistant experience --- all built on a modern React-based Assistant UI framework while retaining the existing backend intelligence. This update significantly enhances usability, performance, and extensibility - delivering a market-ready, GenAI-powered Automation Co-Pilot experience that improves productivity, accelerates workflows, and positions the platform for continued innovation.

Expérience conversationnelle moderne Automation Co-Pilot

Agentic process automation configuration in Automation Co-Pilot
The Automation Co-Pilot experience (across Assistant, Web, and Embedded) has been enhanced to configure, manage, and deploy agentic automations. It allows the users to run AI Agents from Assistant, Web or Embedded similar to the way they are able to do the Process runs. Additionally, it improves visibility by providing clear insights into agentic automations and their configurations within Automation Co-Pilot. This enhancement includes:
  • A new By user option is available for AI Agent configuration. When you select this option, it enables end users to trigger and execute AI Agent directly from Automation Co-Pilot Web or Assistant.
  • The landing page now includes process type visibility, allowing users to identify and configure agentic process automations more effectively.

Configurer un processus ou un AI Agent dans la 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 enhancements 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.

Activer le lien profond pour accéder à Automation Co-Pilot dans Microsoft Teams

Enhanced markdown rendering for structured responses in Automation Co-Pilot+ Conversational experience

Automation Co-Pilot+ Conversational experience now supports rich response rendering in markdown, enabling more structured outputs directly within the chat interface. Knowledge based responses will now be automatically formatted by the model that generates the response, making use of headers, styling and tables to better structure the output. All the interactions are preserved within the conversation context and history, with responsiveness and accessibility maintained across supported content types.

Automatisation conversationnelle avec Automation Co-Pilot

Improved user search in Automation Co-Pilot Teams

The user search capability is now enhanced when adding users to Teams to improve discoverability in enterprise environments. A new All columns default selector has been introduced in the sesrch bar. The All columns option enables cross-column search across Name, Username, and Email. If the entered value matches any of these attributes, the corresponding user record is returned. It allows administrators to successfully locate users even when First Name and Last Name fields are not populated. This update delivers a more intuitive and resilient search experience in Automation Co-Pilot Teams.

Créer une équipe et attribuer des rôles aux membres de l\'équipe

Service Cloud Case ID: 02291547

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, 02227135, 02278410, 02227135
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
Process tasks now automatically advance to the next step upon successful completion of the current step, as expected.

Previously, process execution after completing a task required manual page refreshes to proceed.

Service Cloud Case ID: 02294656
Request tasks now load without erroneous error messages and can be viewed and processed as expected.
Previously, the Automation Co-Pilot web task list view where opening a valid request task could display an Invalid Task ID error in the Automation Co-Pilot user interface.
Note: This issue occurred only for hidden tasks (tasks configured to hide after completion).

Service Cloud Case ID: 02291383
The request creator or eligible user is now correctly auto-assigned when processes were associated with Private teams, ensuring smoother task execution and eliminating the need for manual assignment.

Service Cloud Case ID: 02291545
The date picker now correctly supports this format, allowing users to select dates as expected.

Previously, users were able to select a date but it was displayed in an incorrect format.

Service Cloud Case ID: 02292395
Users can now properly reset or clear textbox values when IsEmpty validation or warning rules are configured, ensuring expected form behavior and accurate data entry.

Previously, a textbox default value was not cleared when a warning rule (For example, “if empty, show warning”) was configured for the field. Empty rule outputs were incorrectly discarded, preventing intentional value resets from being applied.

Service Cloud Case ID: 02293437
The Document viewer element now displays an appropriate error message when an invalid or corrupted PDF is uploaded, preventing indefinite loading and providing clear feedback to the user.

Previously, the Document viewer element continued to load indefinitely when an invalid, corrupted, or 0KB PDF file was uploaded.

Service Cloud Case ID: 02188321
Users can now open requests by clicking anywhere in the request row, including the status column, improving usability and restoring expected navigation behavior.

Previously, in Automation Co-Pilot Web where users were unable to open a request by clicking anywhere within the request table row. Requests could only be opened by selecting the Request Title hyperlink.

Service Cloud Case ID: 02291130
Users can now clearly view selected options in the multi-select drop-down, reducing confusion and preventing unintended form submissions.

Previously, in Automation Co-Pilot Web where the multi-select drop-down continued to display the placeholder text (Select) even after one or more values were selected.
When you run a process that includes a form with a Select file element from the chat interface in the Assistant tab, the form now automatically adjusts within the chat window even if the selected file name exceeds 100 characters.

Previously, forms opened in a fixed-width canvas inside the chat window, which caused layout issues when long file names were uploaded.
When a user views recommended automations in the Automation Co-Pilot Assistant tab and clicks an automation that was previously listed but has since been deleted from the public repository, the system now displays a clear error message.

Previously, a blank response was shown and no error message was provided.
The Automation Co-Pilot UI no longer allows users to run AI Agents with optional or non-selectable inputs. The UI is enhanced such as agents cannot be executed in the standalone mode with altered input configurations, ensuring consistent and expected runtime behavior.

Previously, input variables could be unchecked when running an agent—an unsupported behavior that led to unpredictable execution results.
Users can now reliably apply the Is Visible condition to dynamic check box and radio button elements in forms without rule execution failures.

Previously, in dynamic form scenarios, rules configured with the Is Visible condition for check box and radio button elements were not triggering as expected during process execution. As a result, configured actions (For example, appending text to a textbox when the element becomes visible) were not executed after the form was rendered.
Users can now reliably apply the Is Hidden condition to dynamic form elements without rule execution failures.

Previously, in forms containing dynamic elements (Checkbox, Radio Button, Dropdown, and Dropdown Multi-Select), rules configured with the Is Hidden condition were not executing when elements were programmatically hidden.

The Automation Co-Pilot Web now restores visual consistency of the Date and Time picker with the established UI design, ensuring a consistent user experience across forms.

Previously, in Automation Co-Pilot Web where the Date and Time picker UI displayed inconsistent background colors compared to previous releases.
Users can now reliably submit steps and progress through processes without manual refresh. Step transitions occur automatically upon completion, restoring expected execution flow and preventing business disruption.

Previously, users were occasionally unable to proceed to the next step after submitting a form or bot step, requiring a manual page refresh. Also, process steps did not automatically move forward after completion.

Note: In rare cases, the application might appear temporarily unresponsive, or bots might not immediately reflect recent updates due to session or synchronization delays. Users might need to manually refresh the page to see the latest changes.
Recommended action: In such cases, restart the browser to ensure:
  • The application loads correctly.
  • Bots receive the latest updates.
  • Session-related inconsistencies are cleared.
It helps to resolve temporary synchronization or session state issues.
Users can now successfully submit a form after removing an uploaded file (Image/File element). The element state is correctly updated, allowing the process to proceed to the next step as expected.

Previously, after navigating back to the original form step using the Go To action, users were able to delete the uploaded file but submitting the form failed because the element state was not properly refreshed.

Service Cloud Case ID: 02199787
The uploaded files are now correctly retained and displayed when a hidden Select File field is dynamically shown during form rule execution.

Previously, in such cases, an uploaded file was not displayed in a Select File element if the field was configured as hidden and later made visible using form rules.

Service Cloud Case ID: 02292056
Users can now open and interact with requests created by bots in Automation Co-Pilot without experiencing application crashes. The fix stabilizes process step rendering and improves reliability for bot-generated requests.

Previously, the Automation Co-Pilot application was crashing when a user attempted to open the initial step of a request created by a bot, specifically when the step contained mapped variable inputs (String, List, Date, Number) rendered through form elements such as textarea or textbox.
The Get Storage File action now correctly references Document Workspace Storage when configured, instead of defaulting to an incorrect storage property. Additionally, it restores reliable document retrieval for bots using Document Workspace Storage and prevents process failures caused by empty or corrupted PDF downloads.

Previously, bots leveraging Document Automation with the Process Composer – Get Storage File action began failing when retrieving files from Document Workspace Storage. This action returned an empty (~1 KB) PDF file that could not be opened, despite the document being present in storage.

Service Cloud Case ID: 02287363
The intermittent file loading spinner no longer appears during file submission or when accessing completed steps, ensuring a smoother conversational experience.

Previously, In Conversational automation, users briefly observed a file upload or loading spinner (2–3 seconds) after submitting the initial step following a file upload, and again when clicking on a completed step.
The Time field now correctly displays the user-selected time in the form step after bot execution, ensuring accurate time value persistence across Form-Bot-Form interactions and eliminates confusion caused by time zone-related discrepancies.

Previously, when passing a time value from a form to bot and back to a form within a process, the Time field in the subsequent form step displayed the system-generated time rather than the user-selected time entered in the initial form.
Processes containing Credential-type input variables now execute successfully, and requests are created without errors.

Previously, requests were not created when running a process that included Credential-type input variable configured through a form (For example, password element).
Requests are now created successfully, and processes containing Window output variables execute without preprocessing errors.

Previously, users were unable to run processes from Automation Co-Pilot Web if the process contained a Window output variable.
Unnecessary refresh calls no longer occur when other processes task steps are updated within the same shared environment users, ensuring that embedded users remain stable while interacting with task steps without interruption.

Previously, embedded users within the process workflow execution would see repeated reload, at task steps especially when other users in shared team interacted with their own tasks

Service Cloud Case ID: 02302039

Limitations

Create a form using a Dropdown Multi-Select element with default values such as a, b, c. Build a process, add a Form task, and override the Dropdown Multi-Select default options with new values p,q,r. Then, add an Approval task and map the form task’s Dropdown Multi-Select variables to the available and picked options.

When you save and run the process, and the process reaches the form task step, select q from the available options and submit the task. You will notice that the Dropdown Multi-Select elements in the approval task do not retain the dynamically mapped values after task submission. Instead, it displays an empty element with no value.
When you create a form with a RadioButtonGroup element that includes default values, then create a Task Botwith list and string output variables and use that form in a Bot task and an Approval task within a process. In the Available and Picked option fields, you can map the Bot task's list variables and string variables or Process input list variables and string variables to the RadioButtonGroup. After you save and run the process, the form does not display the mapped values. The RadioButtonGroup continues to show only its default values and ignores the mapped inputs.

When you import a process that contains a Filter task where the Value to filter field is mapped to a Dictionary or Record variable, the process editor displays an error after import. The variable mapping in the Value to filter field changes to Any type, causing the incorrect mapping.

Workaround: After importing the process, manually remove the Any type mapping from the Value to filter field to ensure the process runs successfully.
When you create a form with a Dropdown element that includes default values, then create a Task Botwith list and string output variables and use that form in a Bot task and an Approval task within a process. In the Available and Picked option fields, you can map the Bot task's list variables and string variables or Process input list variables and string variables to the Dropdown. After you save and run the process, the form does not display the mapped values. The Dropdown continues to show only its default values and ignores the mapped inputs.
When you create a form with a Dropdown element, build a process using that form, and override the default Dropdown values with new ones in the Available options field, then add an Approval task and map the Form task output variable to it, and subsequently create another Form task where you map the approval task's Dropdown input variable (using any:asany variable expression) to the Available and Picked options fields.

When you save and run the process, the Form task does not retain the dynamically mapped values from the approval task. Instead, it reverts to the form’s default configuration, resulting in the loss of the mapped values.
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.
Forms configured with the date format do not allow users to select a date, preventing proper form input. This limitation results in user inconvenience and impacts workflows that rely on this date format.

Service Cloud Case ID: 02292395
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.

In forms, when a TextBox field is programmatically reset to its default value (empty) through a rule action (For example, through a button click), the associated IsEmpty validation rule is not triggered automatically.
Automations orchestrated using the V2 engine cannot be executed when triggered from the Conversational Assistant interface.
When using the Open request in New Tab option in a form that contains a Select File element, users might encounter an error if they attempt to resubmit the same step from the original tab.