I read through some posts in the forum about setting up and licensing of FOR and BOR.
From what I understand, no matter I use Studio, FOR or BOR license, the software installation is same, I need to install UiPath Studio which will install Robot service as well.
Besides, there are two kinds of process file format, XAML and NUPKG, one is plain text one is encoded, that makes the things like security more complicated.
As I know, I can only execute NUPKG from Robot service and XAML in Studio, and there is a deprecated function to run XAML by Robot.ext through Windows Scheduler.
But I still have some questions:
- If I am working on machine installed with FOR, can I open the UiPath Studio, create/edit/delete and execute any process/package? (Someone from Zendesk told me process in FOR is read-only, I don’t understand what does it mean) Or I can just execute the packaged process using the Robot Service?
- I know BOR is unattended, but what if I logged in to check some system statuses, can I do what i mentioned in point 1? If scheduled job from Orchestrator launches when I logged in BOR, will it affect the bot execution?
- Can I execute XAML in FOR & BOR using the Robot.exe? Given I want to use the deprecated Scheduling by Windows Scheduler.
- In Orchestrator, there is a license management page, and when we register Robot to Orchestrator it asked for the type of robot (Free/FOR/BOR). Is Orchestrator controlling the license or the initial license activation when install UiPath Studio controlling the license type?
- In deployment scenario that I will have only FOR. Is it appropriate to use 1 Studio license for both Development AND Testing + 1 FOR license for production? Or I should have one Studio for development + 1 FOR for Testing + 1 FOR for Production? What is the different between these two setup?
Sorry to make it too lengthy. There will be great if someone can make up some example or illustrative diagram for different licensing scenarios.