A few weeks ago, we launched a public preview of revamped Action Center for Business Users.
Today we are happy to share some new exciting updates to the Action Center preview!
Action Center offering now enables business users to submit business data and trigger un-attended Robots through form-based input. A brand-new option “Processes” was added for users who would like to trigger un-attended automations from a web interface and track processes triggered by them. This makes it super easy for various business user persona(s) to interface with UiPath Robots, all from a web interface.
How to enable new Action Center Services
This service must be enabled at the individual tenant level in your UiPath Automation Cloud account.
- Launch your Automation Cloud (
- Navigate to Admin > Tenants > Edit Services from the three dots menu
- Select the check box Actions and Processes and proceed to save
(no additional licenses to be added)
- Wait until the status changes gets reflected and the status turns to green
- While inviting users to an account, add them to ‘Automation User’ group. Existing users could be edited to be part of ‘Automation User’ group (cloud account > admin > users)
Who is the target persona?
Business users who need to submit some business input/data to trigger un-attended Robot from web interface and track its completion for the processes triggered by them. Action Center provides an out-of-the-box way of on-boarding business users to UiPath to have Human-in-the-beginning (through Processes) and Human-in-the-loop (through Actions)
What are these processes and how do they get listed for a user?
There are two primary ways in which un-attended Robots can be triggered today:
- Submitting some data to a “Queue” created in Orchestrator as a queue item and a process scheduled periodically to read from it or added as a trigger to automatically start when queue items arrive
- Start job with or without providing input parameters against the process created in Orchestrator
Business users will be presented with a cross folder view of all processes that they can trigger. Processes feature for business users is meant to expose both ‘Queues’ and ‘Processes’ as per their access control defined in a corresponding Orchestrator, so that they can submit some data and trigger a robot execution, track its progress and eventually view the results written by the Robot wherever applicable.
How does this work?
With this update, we are re-using existing concepts of process triggering through “Queues” and “Start Job” to a business user friendly interface powered by out-of-the-box generated form based input.
How to bring up forms through Queues
- Create Queue in Orchestrator, attach a Queue Schema to the ‘Specific Data’
- Create a process that reads queue item from this queue and processes this data into downstream systems as per the business scenario
- Ideal to add this process as a queue trigger to the above queue, so that a job gets scheduled as and when a queue item is submitted.
- Manage access control to users through Folder permissions ( Queue [View], Transactions [View, Create])
- Now, this queue should be listed for the end user with options to ‘run’ and ‘view details’ from the “Processes”
How to bring up forms through Jobs
- Create a workflow with input arguments for the main xaml and publish to Orchestrator
- Create a process in the right folder from the above package, provide default values if any
- Manage access control to users through Folder permissions ( Processes [View], Jobs [View, Create])
- Now, this process should be listed for the end user with options to ‘run’ and ‘view details’ from the “Processes”
Business user experience
User logs on to cloud portal, navigate to “Processes”
Click on “Run process” icon and will be presented with a form.
Users fills all mandatory fields and submits, click on refresh to view latest status of this transaction.
Up on completion, user can navigate in to details page to view / copy output
Form based input through Queues
Download the workflow here: Relocation Expenses.zip (27.6 KB)
- Create a queue ’ Relocation Expenses’ & upload RelocationInvoice_QueueSchema.JSON in the workflow zip to the Specific Data
- Create a process trigger for every new queue item
Form based trigger through Jobs
Download the workflow here: DispatchSalesQuote.zip (26.2 KB)
Lined up next in the preview