In the current public preview, we’re empowering users to trigger and monitor unattended automations without needing to navigate the complexities of Orchestrator, build an app, or create a complex tool especially if business users run these automations (customer stories have been validating this need).
Now, in the future versions, Assistant Web should live up its name and become the primary cloud-based assistant product for business users. It should integrate seamlessly with Autopilot for Everyone to enhance productivity, streamline automation, and facilitate running and progress monitoring.
So I’m sitting at my desk, using my computer… and dreading some repetitive work I must do. Luckily I remember there’s an automation for that.
So do I:
Click near the clock to open Assistant and run the automation
or do I…
Open my browser
Sign into Automation Cloud
Click on “More”
Click on the Assistant tab
Run the automation
Which one seems like a time saver?
What am I missing?
How will Autopilot integration change this interaction?
Also… if the assertion is that this makes it easier for business users to run an unattended automation:
Much like the original desktop assistant… the STOP button for web Assistant is actually a mislabeled KILL button (this really should be changed on both), and I guarantee this will cause undesirable results when used on an unattended automation that was designed to elegantly terminate using a SHOULD STOP activity
Imagine 20+ business users and having to upgrade their Assistants to a newer version. Business users may not be tech savvy, so the amount of coordination, the dependencies on their local PC’s configuration, the guidance, the handholding and overall the (unnecessary) overhead of keeping the software current will all be gone with the web version. As they get used to it, they will also luckily remember to Sign In to Automation Cloud using a bookmark link, just like they do with the rest of their mostly-online routines.
There has long been value & scale in having vast fleets of business users able to run attended automations on their own local computers.
Your response above kind of implies that this new web assistant is a better way for business users to run Attended automations with no messy software on their local machines.
If that was your meaning, they will still need to have the UiPath software installed locally if the web assistant-triggered automation is intended to run on their local computer.
If you’re instead implying that this is a paradigm shift to having business users manually triggering unattended (remote) automations instead of attended (local)… now the COST for your program just increased, because all those business users’ automation demands will be directed to an array of higher cost robot VDIs using unattended licenses instead of their own local, less expensive local computer’s attended licenses.
There’s also usually more to the logistical story for unattended automations. Orchestrator usually pairs up processes with specifically configured users & VDI machines, and schedules them according to reasonably well thought out robot VDI capacity, and the SLA needs of the given process, not to mention knowing which input parameters to configure so it runs properly, etc. I’m having a hard time imagining how all those unattended nuances will be addressed using one simple web Assistant start button for “business users” who can’t be bothered with Orchestrator nuances.