Why do we publish the process and use Assistant to trigger the attended robot? What is the advantages, why dont we just use Studio for such purpose?

Help Orchestrator
,
1

Why do we publish the process and use Assistant to trigger the attended robot? What is the advantages, why don’t we just use Studio for such a purpose?

Also, say if I am developing a process for others, I still need to send them the file containing the Studio, so what is the point of using Assistant?

2

Studio is a development environment, not intended to be used to run automations in production.

1 Like
3

No, you don’t. That’s the point to Assistant. You publish your project to Orchestrator and then they see it in Assistant and can run it without Studio (and a license) without you sending them the code.

1 Like
4

There are sometime you can not install studio because of the licenses then you can install only the robot or use automation express as user then you can trigger your processes in attended mode.

Should be able to connect to orchestrator through machine or url.

1 Like
5

Impressive! Never thought about installing Asistent separately, very inspiring. So the uploaded process can be triggered only using Asistent?

6

Got it! So it acts as a front-deck with better UI which separates users from the back-desk.

7

Why we have to stick with Assistant for running in case of attended automations:

  1. Sometime UiPath studio is not installed on end user machines.
  2. There are code security issues mistakenly or unknowingly they might temper the code, so that’s not a viable option. Also, end users are not very good in operating UiPath which would add an overhead of training the basics of UiPath to the customer before deployment.

You could also trigger it through a batch file too.

8

Yes and it also allows for users to enter values into Process Arguments before running the automation, in case that’s useful to you.

9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.