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

Goal-Based Agent (GBA) output variables are now displayed in the Case view after agent execution completes. Users can review each output variable's name, description (when available), and final value directly within the case. The enhancement supports all output variable types, renders Markdown content for string outputs, and improves readability for large outputs with expandable sections. Additionally, an issue preventing output variable descriptions from appearing in Case view has been resolved.

Case view capability in Automation Co-Pilot | View Goal-Based Agent output variables in Case view

Automation Co-Pilot now provides a more streamlined and informative experience for monitoring process executions, especially those involving Agent-driven workflows. The updated process steps view introduces richer execution details, flexible viewing and filtering options, and improved visibility into parent-child process relationships. Users can quickly identify task status, focus on assigned work, and seamlessly navigate from a parent process to the corresponding Agent execution for deeper insights. Together, these enhancements make it easier to track progress, monitor Human-in-the-Loop (HITL) activities, and troubleshoot complex automation workflows.

Monitor process executions

The Task list experience for Co-Pilot managers and administrators has been streamlined to improve usability and reduce visual clutter. The row selection checkboxes are now hidden by default, allowing all tasks to display consistently without disabled or greyed-out rows. When users choose Edit bulk assignment, the task list enters a dedicated bulk assignment mode where only eligible tasks are displayed for selection. Within bulk assignment mode, selecting a task automatically filters the list to tasks belonging to the same Process and Team, helping users make valid bulk assignments more efficiently. After completing or canceling a bulk assignment, the task list automatically returns to its default view.

Assign multiple tasks

Streamline task management with an Unassigned task filter

Automation Co-Pilot now includes an Unassigned quick filter on the Tasks page, making it easier to find tasks that do not have a contributor assigned. Instead of manually searching for unassigned tasks, users can apply the filter with a single click to instantly view only unassigned work items. The filter works seamlessly with existing filters, enabling users to combine criteria such as task status or date range to quickly locate specific unassigned tasks and streamline workload management.

Filter and search for a task: Preset filters in Table view

Previously, in Conversational Assistant, form elements in the initial step were duplicated when users clicked Expand details after a request was created.

Previously, deleting an active conversation thread in Conversational Assistant removed the thread from Chat history but left the chat window open with stale messages and an active input field. Attempting to send a new prompt resulted in a non-user-friendly error exposing the internal conversation ID.

Previously, conversational automation could display responses, notifications, assigned tasks, and request details from a previous conversation in a newly opened chat when users switched conversations before the prior response completed.

Previously, conversational automation could display an inconsistent or improper Welcome state UI when users clicked the New chat button while a response was still in progress.

Previously, Co-Pilot administrator prevented users from creating new tags if the tag name was a sub-string of an existing tag (for example, creating document when document-automation already existed).

Previously, multi-select drop-down values passed from Approval tasks to Form tasks in V1 processes could render as blank because the selected options were converted from a list to a string format during processing.

Previously, conversational automation users could occasionally receive invalid or unclear responses from RouterLLM when no relevant task or data was available.

Previously, refreshing certain completed form steps in Case view could cause the page to display a blank screen, particularly in workflows where a form step immediately followed a Bot or API Task step.

Previously, parallel processing workflows with Split/Merge nodes could stop execution when conditional branch inputs were empty, preventing fallback and end steps from running.

Previously, Filter tasks using OR (||) conditions on Dictionary currentKey values returned incomplete results by applying only the first matching condition.

Previously, PDF files could not be uploaded through file input variables during process execution in Co-Pilot workflows, preventing users from attaching PDF documents.

Previously, selected check box values were not displayed in the Completed approval stage after approval tasks were finished, limiting visibility into user selections during review and auditing.

Previously, these settings were not retained after editing and saving processes in the Legacy Process Editor, causing errors when reopening the process.

Previously, updated table column data passed through Form-Bot-Form flows in the Process editor was not displayed correctly in subsequent form steps after bot execution.

Previously, forms that used rules to compare date fields could produce incorrect results in certain scenarios.

Service Cloud Case ID: 02303871, 02301677

Previously, in certain long-running processes that uploaded files to storage, expired files could remain stuck in subsequent bot steps and not progress to the next stage.

Service Cloud Case ID: 02299053

Previously, clicking the copy icon associated with the assistant response did not copy the message content to the clipboard for certain messages.

Previously, when business attribute labels contained unsupported special characters, the attributes did not display correctly on the AARI Requests and Tasks pages, resulting in inconsistent behavior.

Previously, when opening public processes in the Process Editor (V2), users could see incorrect variable mapping validation errors for certain conversion methods (for example, String:toFile, Number:toString, Number:toList, Table:toString, File:toRepositoryPath, and Date.Any:asAny).

Previously, month abbreviations could render differently depending on the selected locale.

Previously, when a bot step involving a file upload failed to complete its post-processing (because the storage metadata was not found), the overall request status was correctly set to Success but the underlying step record was not updated and remained in the In Progress state.

Service Cloud Case ID: 02314291

Previously, if a request execution referenced an invalid bot variable or form element in a subsequent step, the request could become stuck without indicating the cause, making it difficult to identify and resolve the issue.

Previously, when a completed Automation Co-Pilot request contained only Start and End steps, the process view displayed only the End step. The Start step was not shown, resulting in an incomplete representation of the executed process.

Previously, uploading a file to a Select file form element could fail with a Missing Required Value: id_oneof error, preventing users from attaching files and completing the process form, particularly in existing processes.

Previously, after a process request was completed, the Start step could appear empty for processes that contained only Start and End steps, preventing users from viewing the input variables used in the request.

Previously, the Soft delete icon did not appear for request creators or Automation Co-Pilot business users unless they were explicitly assigned the Delete request role permission, preventing eligible users from accessing the action.

Previously, selecting Open in new window from a Form or Validator task opened a new chat window instead of opening the associated Form or Validator step with its process context.

Workaround: To fix this issue, use a combination of special characters and alphanumeric characters, or search using a portion of the request title that contains letters or numbers.

For example, an 80/20 layout might render as 50/50.

Workaround: Refresh the browser to continue and view the next process step.

This is an UI issue only and does not affect filtering, requests are correctly displayed for the selected date range.

Workaround: Assign the task to the user who needs to view or complete it.