I have a question about the robot for the end-user.
I read these blogs below, but I got stuck and I wonder how to publish the package that I created for the user.
From the (1) I read Richard Denton’ s guideline, and I saw something not match with (2). I mean when the end-user creates their robot, and how can I access my Orchestrator with their robot and public my package for them.
Hi Nguyen_Huy
Once you develop your code , In the studio go to ‘Design’ tab , and click on ‘Publish’
This will gives a window asking where you want to publish the nuget package
You can select Custom radio button and give your Local system folder to save the nuget package
OR
If your robot is connected to orchestrator already , the package will automatically will be published to Orchestrator
Now login to Orchestrator in your machine
GO to Packages and upload the Nuget package which you published into your local machine
Now go to processes and create a process and select the package
Now go to Robots
If your End user’s bot already there , now go to Jobs , create job and select your process , select your end user robot and click run
Hi @vinay_reddy, Do I can create my user’s robot* on my Orchestrator ?
*: Does my user’s robot need to have the same Machine Name and Machine Key with my Robot?
One more question: If my robot is connected to orchestrator already, the package will automatically be published to my Orchestrator and if my End user’s bot already there, I just run my end user’s bot with this package without “GO to Packages and upload the Nuget package which you published into your local machine”, or I need to do this step even when package will automatically be published to myOrchestrator?
The user robot tray is connected to your orchestrator… So if he publishes it to your orchestrator you will need to approve upload it in the orchestrator to make it working for all, else he can simply run it through the UiPath tool!!!
Now saying so he can also publish it with another name and play it with the robot tray…
Yes you can access them Like if you have the access for that orchestrator as a user with specific role been created as per this document you will be able to access any entities along with robots
Kindly let your user if they are the admin or if you are the admin you can leverage them with these roles in orchestrator
And
It’s like for an example if the user or may if you are about to execute a process in a machine A from orchestrator that specific Machine A name should be mention here in the orchestrator while creating machines under machine tab
To get the machine name search in Start → uipath robot → then in that robot tray from the side notification at the bottom end of the desktop screen (along with our time zone and notifications) where click on settings of uipath and get the machine name
—and while creating robot for this machine we need to mention the domain name and username
To get that from the same machine under cmd window type as whoami and execute this command
This will show us the domain and username
Along with that mention the password also
The package will be published to orchestrator only when the studio and its machine is connected to orchestrator and that process is published from a studio
So to publish a package we need to publish from a studio
And to publish to a orchestrator that specific studio existing machine must be connected to that specific orchestrator
Only then we can publish that package
That’s all buddy you are almost done
Kindly try this and let know for any queries or clarification
Cheers @Nguyen_Huy
Follow Up Question-
Process was available for BOT on user machine to run. But, when the user executed the process there was an error. Error Code 1100 (Any idea).
Overview -
Developer
Created Assets
File1Export Folder Path
(Location where the files are saved)
File2Export Folder Path
(Location where the files are saved)
URL (Url being used in the process)
User Assets
Created the same asset names but with user defined folder path on his local machine.
Was able to publish and run on Dev machine but the user bot throwing an error.