Automation Co-Pilot for Business Users v.34 release
- Updated: 2024/11/12
Automation Co-Pilot for Business Users v.34 release
Review what's new and changed, and the fixes and limitations in Automation Co-Pilot for the v.34 release.
What's new
| To provide an improved
user experience, when you add or resize a new element in a row
of a form created in Process Composer, the form
renders the row and its elements consistently regardless of how
the form was created via the desktop, web, embedded, or mobile
platform. Additionally, each row on a form can contain up to
10 elements with a total combined cell width limited to
100%. When adding or editing elements to a row, if you
exceed either the number of elements in a row, or the
combined cell width is greater than 100%, two new messages
are displayed:
You must adjust the number of elements and/or cell width of an element in the row to proceed. |
When
you add rules to forms in Process Composer, hidden
variables now support all the same
If/Else conditions that are available
for their respective visible form elements, except for the
Has errors condition. This applies to
these specific hidden variable types:
The Has errors condition remains exclusive to visible form elements only. |
What's changed
| When elements in a form have any errors in their property values (such as minimum/maximum, height, and so on), the form Save option will be disabled. In previous Automation 360 versions, the Save option was enabled. If you open an older form that contained errors in their properties, you must resolve the errors before you can save and proceed; otherwise, you can close the form. |
| To better assist users with troubleshooting errors, when they edit a process task in Process Composer, validation error messages now display specific information as to which field needs to be corrected, and any required fields that are missing information are highlighted with a red box. |
| Override
business attributes You can now configure the option to override existing business attributes at specific nodes in a process. This enables you to make dynamic modifications to the process to adapt to changing workflow requirements. |
| Prepared
session for Automation Co-Pilot automation
A prepared (pre-warmed) session is now utilized while deploying Automation Co-Pilot automations that reduces the automation runtime significantly. Service Cloud case ID: 02138574, 02110088 |
Fixes
| Fix for performance issues while running an
Automation Co-Pilot process. Previously, after
enabling a retention policy, the user still experienced an
out-of-memory (OOM) issue with millions of records in the
RIW_STEP_RECORD and
TSK_TASK files. Due to the large number
of records, the system purged the files from the database,
thereby increasing the query performance. Service Cloud case ID: 02125758 |
When a user now creates a new form in Process Composer, the following special characters
are retained (as entered) and are no longer converted to HTML
characters:
Service Cloud case ID: 02126485, 02140633, 02146807 |
| Fix for an issue when a user uploaded Automation Co-Pilot forms and processes files to
their S3 bucket using Amazon cloud storage. The files are now
loaded successfully to the S3 bucket, without generating 500 and
404 errors. Service Cloud case ID: 02134781 |
| For some pages in Automation Co-Pilot (such as the Detailed View of the Requested Tasks list page),
the options at the bottom of the page did not load properly and
were inaccessible previously. This is now fixed so that all
options are visible and clickable. Service Cloud case ID: 02136082 |
When a user added form elements to a form in
Process Composer, if there was a clear
value action set for an element (such as Number,
Checkbox, Date, and Time), the following Is
Empty condition now works properly. Previously,
after clearing the value from the field, the form failed to
update the element with the empty value. As a result, the
following Is Empty condition did not work
properly.Additionally, when a rule was created for an
element with |
| The URL change rule condition now works properly for table elements of a form. When the URL of a table hyperlink changes, all actions defined in the URL change rule conditions will be applied. |
| The font size has been increased and the alignment is now fixed for the Attribute display label field in Process Composer. |
| When a new hidden Date variable is added to a form without specifying a default value, the date set for this variable through a rule does not follow the default format of MM/DD/YY. |
|
When an approval task (which has been assigned to a private team) is moved to a failed status, the task is no longer available to be approved or declined. It remains with a failed status and does not proceed to the next step in the process. |
|
When using the Get Storage File action in a bot to download a file in Process Composer, the process that is initiated by the associated bot no longer fails nor generates a java error. Service Cloud case ID: 02106777, 02125429, 02122302, 02136807, 02138565, 02142422, 02143988, 02145290, 02135652, 02155338, 02153996, 02157810, 02163845, 02169805 |
|
Completed tasks in the Human Task tab in Automation Co-Pilot now show their correct status. Service Cloud case ID: 02145713, 02143999 |
| The scrolling issue for
documents is now fixed in Process Composer and now
works properly. Service Cloud case ID: 02126244 |
| The request and task pages now accurately display the total number of request or task page counter, regardless of the page currently open. Previously, the counter was restricted to 10,000 unless the 100th page was opened. |
| When you create and add a
Bot Task to execute inside a process
automation, the bot no longer stays stuck in the in-progress
status and executes successfully. Previously, the bot execution stuck when you performed the
following steps:
Service Cloud case ID: 02143152 |
| You can add tag names that
include parentheses, example (cases) in a process without any
issues. Previously, tag names containing parentheses could not be added successfully. |
| If you use action inside an API Task, the
action now completes, and the request is created. Previously, the request was not created as the Browse button for selecting a Public process was disabled for API Tasks. |
| When you execute a process that
contains two or more forms in the human task steps and variable
mapping is performed, the element label content of the
subsequent human tasks does not change and retains the element
label to indicate the appropriate form. Previously, the element labels changed to reflect the same label as the initial form. |
| When you create a form with
hidden variables and add an action with hidden variable rule in
the form, the hidden variables are now listed in the expression
for set value option. Previously, hidden variables were not listed in the expression. |
| You can now successfully add the
Dynamic Area element between existing
rows in a form. Previously, the element could only be added at the end or not at all. |
Limitations
| Currently, a user who is logged in as an
Automation Co-Pilot admin without having an Automation Co-Pilot user license is prevented from
running or scheduling a process from a public workspace. A user
who has run or schedule permission and access to the folder of
the process should be able to run or schedule the process.
Workaround: Add the required license. |
| When you create a form that contains Checkbox and Textbox elements, and a rule to set a value, the rule does not trigger the next Human task step to occur. Instead, the rule uses the element values from the form instead of those values derived from the input. |
| When you create a form with a Table element, and create a rule for the Table element to change its table column label, the change element label rule does not work properly for the table and the label remains unchanged. |
| If you created a form with a hidden variable date element, if you try to override the hidden date element on the form in Process Composer by adding static data when you are mapping the variable, then the overridden static data is not passed to the next step in the form. |
| After you delete data from an input field
in Process Composer, the value that was deleted
re-appears in the field. Workaround:
|
| When a user with access to
process in the web application logs into Automation Co-Pilot within the Salesforce
application, logs out of the Control Room
and logs in with a different user who does not have a valid
Automation Co-Pilotlicense, Automation Co-Pilot still displays the automations
list in Salesforce. Instead of showing a license error with a
logout option, the system displays content from the prior
session, even though the user has logged in with different
credentials. This issue occurs because the Automation Co-Pilot window is using session data from
the original session instead of refreshing for the new login.
Workaround: Disable the third party storage partition flag from the browser. See Automation Co-Pilot for Business Users FAQ. |
Updates to the interface
| Automation Co-Pilot |
|---|
| Two elements on the form builder page in Process Composer have been reorganized and renamed.
The BlankSpace form element has been
removed from the Elements section and added to the Layout
section (with a new icon), and the Column
element has been renamed to Row.
|
