Automation Co-Pilot for Business Users v.42 release - Review the fixes and limitations in Automation Co-Pilot for the v.42 release.

Automation 360

Review the fixes and limitations in Automation Co-Pilot for the v.42 release.

Fixes

In Automation Co-Pilot, you can now upload files through forms when sufficient storage is available for the tenant.

Previously, file uploads through forms could fail with a Not enough storage error because the remaining tenant storage was incorrectly reported as a negative value, even when sufficient storage was available.

Service Cloud Case ID: 02316598
When a Child Process or AI Agent step configured with Hide this task from users completes during runtime, the process now proceeds correctly and displays the next applicable step.

Previously, in such cases, users might see a blank page instead of the next process step.
When you select Open request in New Tab and submit a form containing a Select File element, you can now return to the original tab, upload a new file, and submit another request successfully.

Previously, when you returned to the original tab after submitting the request in a new tab, attempting to upload a new file and submit another request could result in an Invalid File ID error.
The OpenedOn meta variable now returns the expected value for Initial, Document Validation, and Form steps. The SubmittedOn meta variable also returns the expected value for the Initial step.

Previously, in such cases, the OpenedOn and SubmittedOn meta variable returned an empty value.
In Co-Pilot Web, forms that contain a Document viewer now display the document and form areas according to the width configured in Form composer.

Previously, the document and form areas were displayed at an equal 50:50 ratio, regardless of the width configured in Form composer.
In Automation Co-Pilot, when a Task Bot fails during process execution, you can now click Activity history to view the Task Bot execution details.

Previously, when a Task Bot failed, clicking Activity history did not open the bot execution details.
Pending tasks now open correctly in the full view when you click Open from an embedded application.

Previously, when you opened a pending task from an embedded application and clicked Open, the task did not expand to the full view.
In Co-Pilot Web, forms that contain a Document Viewer now display the document and form areas according to the width configured in Form Composer.

Previously, the document and form areas were displayed at an equal 50:50 ratio, regardless of the width configured in Form Composer.
The OpenedOn meta variable now returns the expected value for Initial, Document Validation, and Form steps. The SubmittedOn meta variable also returns the expected value for the Initial step.

Previously, in such cases, the OpenedOn and SubmittedOn meta variables returned an empty value.
The check box content now remains blank after form submission, and the element ID is no longer displayed.

Previously, in a Co-Pilot form, when the content for a check box was left blank, the check box element ID could appear after the form was submitted.

Service Cloud Case ID: 02312453
Pending tasks now open correctly in the full view when you click Open from an embedded application.

Previously, when you opened a pending task from an embedded application and clicked Open, the task did not expand to the full view.
In Automation Co-Pilot, when a Task Bot fails during process execution, you can now click Activity history to view the Task Bot execution details.

Previously, when a Task Bot failed, clicking Activity history did not open the bot execution details.
In Automation Co-Pilot, you can now upload files through forms when sufficient storage is available for the tenant.

Previously, file uploads through forms could fail with a Not enough storage error because the remaining tenant storage was incorrectly reported as a negative value, even when sufficient storage was available.

Service Cloud Case ID: 02316598
Approval tasks now expire as configured when followed by If or If steps.

Previously, in Co-Pilot, an approval task with an expiration time configured did not expire as expected when followed by an If or If step. The task remained in the approval stage until it was manually approved or rejected.

Service Cloud Case ID: 02222145
Form can now be resubmitted after validation failure. After correcting the validation errors, you can now resubmit the form without refreshing as the Submit button will always be in enabled state.

Previously, when a form submission failed because of a validation error, the Submit button became disabled. Even after correcting the invalid or missing field values, you had to refresh the form to enable the Submit button.

Service Cloud Case ID: 02327349
When you disable LLM responses in Conversational Co-Pilot, the File upload option no longer appears in the chat interface.

Previously, the File upload option remained available, allowing users to upload files even when LLM responses were disabled.
In the Tasks detail view, the status of a Waiting for approval task now updates automatically after you approve or decline the task.

Previously, the task continued to display the Waiting for approval status until you refreshed the page.
When you select an assigned-task notification in Conversational Automation, the request now opens at the corresponding assigned step in the right pane.

Previously, after viewing the initial step of another request, selecting an assigned task could incorrectly open the initial step instead of the assigned step.
The bot run progress bar now appears centered in Desktop Assistant while an automation is running.

Previously, the progress bar appeared in the right corner because of a UI alignment issue.
Conversational Automation now displays the correct success notification after you submit a validator step in chat.

Previously, submitting a validator step could display an incorrect notification message instead of confirming that the task was submitted successfully.
The table now returns the correct results when users filter date ranges longer than 12 days.

Previously, when users filtered a Date column in a table element for a range longer than 12 days, the table could return no results or incorrect results for certain date formats.
The date filtering now works as expected for the supported date formats.

Previously, filtering a Date column in a table element could return no results for certain supported date formats, even when matching data was available.
The Start step now displays only the applicable input variables and does not display output variables.

Previously, after a request was completed, the Start step displayed output variables with default values for processes that contained only Start and End steps.
Image variable mapping now correctly overrides an existing image in an Image element when you run a process with a Form Task.

Previously, the Image element prioritized the image configured in the form over the mapped input variable, causing the existing image to remain unchanged.
An appropriate error message now appears when users do not have Manager user permission and tries to access the Co-Pilot web page with url/aari/#/manage/process.

Previously, users without the required permissions could see a blank page when they attempted to access a Co-Pilot web page with url/aari/#/manage/process.
Pressing Enter in the text box no longer trigger the button rule.

Previously, when users pressed Enter in a text box element without a configured rule, the form could trigger a button Is Clicked rule and execute the associated action.
The Formula element now displays with consistent styling and alignment when you run a process that contains a form.

Previously, the Formula element displayed differently from other form elements, resulting in an inconsistent user interface.
Conversational Automation now consumes one interaction per user prompt.

Previously, submitting a user prompt in Conversational Automation could consume two interactions instead of one, causing interaction entitlements to be used faster than expected.

Limitations

In some cases, a configured rule in a form might not execute as expected. For example, a File element configured with a visibility rule might become hidden while an uploaded document is loading.

Workaround: If a configured rule does not execute as expected, trigger the rule again.
In Co-Pilot Desktop Assistant, after you complete a process, the Co-Pilot header screen might briefly appear after closing completed Request.
Note: This is an UI issue only and does not affect the functionality.