Running process in Front Office Robot (FOR)

studio

#1

As of now, for one to start FOR, following as options:
a) Launch Studio, wait for System Tray Icon to be visible, launch Process

OR

b) Run C:\Program Files(x86)\UiPath Studio\UiRobot.exe, wait for System Tray Icon to be visible, launch Process

In both options, end user need to follow first step i.e. launching Studio or UiRobot.exe, which can be avoided.

UiRobot.exe can be added ‘HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run’ so that Bot will be always running.


How to efficiently install many front office robots (FOR)
#2

Interesting info.

How do we get the process to appear in the system tray icon?


#3

Hi ,
You just need to publish the workflow and go to uipath system tray Icon and click on available there you see published workflow name .click on it to run .


#4

Thanks.

I have UIPath Studio on my local machine, and when I publish a workflow, it simply gets dumped into a local directory on my computer, then displays an alert showing where it was placed, and says “press control-c to copy”. It never appears in my system task tray.


#5

Did you try to refresh available options of uipath tray .its will take a moment to reflect in the tray .


#6

Yeah I’ve had UIPath studio running for many weeks locally, and have published many times since. Nothing ever has appeared in my system task tray that I have noticed.

Usually I just manually upload the resulting package to Orchestrator on the processes > view packages page… but now I’m trying to learn what it looks like to create a “front office robot”… because that is my next deliverable. Do I need to specify some magic directory for my publish path?

task-tray


#7

Hi ,
You suppose to click on available tab not on running .
Please publish any simple workflow and click on available and then click refresh buttons to reflect on the tray .
It should work😊


#8

AHHHHHHHHH there’s the magic :joy: lol

I thought that “Available” tab was grayed out so I didn’t even bother clicking on it.

You nailed it. I do see my local package in the system task tray’s “Available” tab:

local package


#9

Have nice day and happy automating .:+1:


#10

Do you know how to associate a hotkey to trigger any given process? Is that something we configure with Task Scheduler?


#11

Hi,
As of now there is no such options to run the script using hot keys .
These are the ways to run the process .
1.From UiPath Studio
2.From UiPath Robot Agent
3.From command line
4.Through a REST command
5.Orchestrator


#12

OK that’s good to know. I thought I saw them triggering the process via hotkey in one of their demo videos.

Finally then… is the “front office server” they talk about on their website the same thing as “Orchestrator”? I’d like to be able to push new versions of a package down (from the server) to multiple FOR… but not sure what that process looks like. I’ve successfully used Orchestrator to schedule BOR already.


#13

First thing first orchestrator mainly for BOR.
For FOR you have above 4 choice to run the process and more over it doesn’t make any much sense running FOR from the orchestrator because it’s requires human intervention.:wink:


#14

Running no, but managing package versions does and works the same as for BOR.


#15

Not sure what “front office server” is - where did you read this?

To push new version of a package down (from the server) to multiple FOR using “Orchestrator”:
a) Publish new package (via Studio or using Upload Package option in “Orchestrator”)
b) Go to Process, click manage version and click on ‘Use’ against latest version


#16

Sorry, I beg to differ.

Orchestrator as much as for FOR as much for BOR. Specifically for FOR, we can use Orchestrator for

  • manage package version
  • check Logs
  • use Assets

#17

All true.:+1:
I was just mentioning about when there is a human intervention required for FOR then there is no much sense even if you schedule from orchestartor because process won’t be proceed until user intervene.

Buying Orchestrator for BOR makes a sensible investment. :slight_smile:
At the EOD its left to the user how he elaborate functionality of each component of UiPath.

peace .:v:


#18

Can you please expand on this or point me to any docs which explain the process? I was musing about this in a separate thread… trying to find out from anyone how all the FOR associated with a given process can simultaneously/automatically get a new package.


#19

https://www.uipath.com/automate/front-office-robotic-automation


#20

Thanks! I think I’m starting to catch on.

You left off the steps about how the FOR machines see/get the updated package version… but reading between the lines:

Any given FOR should be registered to Orchestrator… and when this is completed… that FOR user will then see the ORCHESTRATOR-hosted processes (as opposed to the local packages) in their local system task tray.

So in that way… we never actually push new packages down to FOR… the updated package is PULLED when the agent manually triggers the process on their FOR?

FOR Packages