Studio vs Back Office Robot

orchestrator

#1

I’m reading Orchestrator User Guide, and I found that I can register UiPath Stuio as a robot and run the workflow from orchestrator.

Would it be true that Studio has more capabilities on top of Back Office Robot?
Or, are the any functionalities that only Back Office Robot has??

(I’m wondering because Back Office Robot license should be more expensive than Studio, but it seems Stuio has more functionalities, for example, it enables us to design workflow while BOR doesn’t.)


#2

I’m talking about following explanation, it’s on page 29 in “UiPath Orchestrator User Guide 2016.2”.

Note: If you register Studio as a Robot to Orchestrator, but do not provide the correct credentials in the Username and Password fields, you cannot run workflows.


#3

Hi,
main difference
FOR:Triggered by User on same user machine
BOR: Triggered,Manager,Controller and scheduled using Orchestrator (From anywhere at anytime even with system locked)
Both are developed on Studio only.

So now u know why BOR bit expensive than FOR.:wink:


#4

Thank you for the quick response!
It’s really understandable for me who never tried BOR yet.

How about the difference between Studio and BOR?
Based on the explanation I quoted above, it seems Studio (or maybe BOR functionality which is enabled once Stuiod license is activated?) can be triggered by using Orchestrator, too.

If it can be managed, controlled and scheduled uisng Orchestrator, then I think Stuio should be expensive than BOR, but BOR is much expensive in the price list I got from UiPath JP.
I’m confusing if I should purchase BOR or Studio…


#5

Both are designed on Studio it self.
Only thing separate them is how you run/designed your workflow using user assistance or unattended using orchestartor.
Orchestrator is mainly for BOR.
using FO in a standalone environment is a license terms violation. FO can be used and triggered only by an agent that shares the same desktop.



#6

hmm…I think in my case I shouldn’t use FOR as you mentioned, since I want to use UiPath in a standalone environment.

What if I use Studio (for development & running workflow) and Orchestrator only? (no FOR or BOR)
might be license terms violation?

I know Stuio is designed to develop worklflow and it might not be for production environment use, but it can be executed by using orchestrator so I thought I might not need BOR or FOR if I have Studio license…


#7

I might have figured out, I guess stuio can be triggered as DevTest type robot?? :slight_smile:

Quoted from page 28 in “UiPath Orchestrator User Guide 2016.2”

Type
The type of Robot. This can be only DevTest, BackOffice or FrontOffice. It is possible to filter the page according to the Robot type.


#8

If you use only studio then you need to run and schedule by user.
You can use orchestrator http://demo.uipath.com/ for scheduling .
PS: Only learning purpose .
@badita might give you in brief about license terms. :slight_smile:


#9

Thanks a lot!!
My company FW prevent me to access the demo site. I’ll try once I get home!
Of course just for learning purpose :smiley:


#10

That will be a license agreement breach. Studio is for development and you are allowed to run it as robot for testing/development purposes but not in production.


#11

Thank you for the clear explanation, we’ll purchase appropriate licenses!

(I just don’t let others know we can run Studio robot from orchestrator, then they don’t have choice except for BOR XD)


#12

You can let :slight_smile: We can’t prevent this


#13

Thanks, I might do later, maybe after others understand UiPath betters :grin:


#14

Hi Badita,

As per the info in the post https://forum.uipath.com/t/usual-orchestrator-errors-faq-troubleshooting/2716 , posted by Andrei_Pop, will we not receive “Permission missing: Remote Execution” error in Orchestrator if we use FOR to run the task.


#15

I think that applies to FOR license and not Studio.


#17

I have a system with FOR in it and I want the FOR to run a workflow which was created in another system(The system with UiPath Studio), how to run that workflow using FOR.


#18

deploy it via orchestrator and start it from tray.


#19

Thanks :slight_smile:.