- Release notes Cloud Action Center
- December 2020
- General Availability
- Public Preview
- Getting started
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait For Job And Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Wait For Form Task And Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task And Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Get App Tasks
- Add Task Comment
- Update Task Labels
- Create App Task
- Wait For App Task And Resume
- Configure task timer
- Actions
- Processes
- Notifications
- Audit
General Availability
9 November 2020
Action Center enables support for long-running unattended workflows that require human intervention as workflow execution is fragmented and can be suspended and resumed at a later time after human input is provided.
This release graduates key features in handling end-to-end business processes, integrating Action Center directly in our Automation Cloud portal and reducing the need for business users interacting with Orchestrator at a minimum. Different business user personas can interact with Action Center through a web interface that is now exposed in the Automation Cloud portal.
The two facets of Action Center are represented by the Processes and Actions sections in Cloud Portal, both accessible from the side navigation menu provided they have been enabled on your Automation Cloud tenant.
See below the highlights of this release.
Triggering Unattended Processes Through Forms
The new Action Center offers a way for business users to launch unattended processes directly from the Automation Cloud portal and provide inputs to Robots, which are subsequently used for successful process execution. They can trigger unattended processes through forms (including file upload) and track the executions.
Classification Station Actions
Classification Station is a new feature that enhances human-robot collaboration by allowing humans to review and correct document classification and splitting results. It can be used both as an attended activity (through Present Classification Station) as well as integrated into Orchestrator’s Action Center by leveraging Long-Running Workflows (through Create Document Classification Action and Wait for Document Classification Action and Resume).
Modern Folder Support
A notable addition in this release includes Action Center support for modern folders. If up until now you were restricted to only using it in classic folders, from now on, you can take advantage of all Action Center goodies regardless of the folder type.
We also added a new page exclusively for the Action Admins in your company, such that they are easily able to allocate and assign actions to any Action User from a centralized location.
Intermediate Save
Beginning with this release, you no longer have to fill in form fields in one go. Simply save the form at any point, and the progress is saved for you to get back to it later on.
Add File Attachments to Actions
As of now, business users can upload files in action forms to facilitate agent verification scenarios such that the Robot can proceed with downstream processing.
The particularities of the upload (e.g., single or multi-file upload, minimum and maximum allowed file size) are configured at design time in Studio, using the Form Designer incorporated in the Create Form Task activity (UiPath.Persistence.Activities activity package v1.1.8+).
PDF Viewer Support
Form actions bring support for PDFs so you can have a look at your PDF files directly from the portal.
Safe JavaScript Executions in Actions Forms
Action Center now allows for JavaScript-based advanced validations and conditions logic.
The documentation for Action Center services residing in Automaton Cloud can be found in the official Action Center guide.
For the time being, actions can also be managed in Orchestrator services as a way to help you smoothly transition to the new paradigm.
To reflect this, Action Center documentation can be found in the Orchestrator guide as well. However, we recommend taking advantage of the new experience, as after the transition is complete, Action Center will be removed from Orchestrator, and so will be the documentation.
- In Orchestrator, create a new queue and name it Relocation Expenses.
- Provide a default value for the
BucketNamein the queue schema file. The schema can be found in the.zipas the JSON schema For this workflow, the bucket's name is ActionsTest. - In Orchestrator, upload the queue schema file for the Specific Data field of the queue.
- Create a queue trigger for every new queue item that is added to the Relocation Expenses queue.
- Upload the PDF to the storage bucket using storage bucket activities.
- Pass the uploaded file path to the form
data through an attribute name having
_storageas a suffix (e.g.,pdf_storage). - Refer the attribute name (e.g.,
pdf_storage) in the HTML Element control using an<embed>tag. For example:<embed href={{ data.pdf_storage }} width="600px" height="500px"></embed>. - Do not check the RefreshOnChange property.
-
Navigate to Edit JSON, search for
"refreshOn"field, and set the value to the form data attribute (e.g.,pdf_storage') and then save.Important: If you use** UiPath.FormActivitiyLibrary v1.1.10**, notice that Component JSON doesn't list the"refreshOn"option. However, you can manually add the"refreshOn"key and set its value as mentioned above.
- In the property of a form element, go to the Logic tab, then add Advanced Logic.
- Select JavaScript for writing data validations and advanced condition expressions.
-
This JavaScript interpreter does not support DOM APIs. Hence, objects such as fetch, window, browser are not exposed.
