Running process in Front Office Robot (FOR)

Help
21

Right. At the second trigger the package will already be there.

  1. Robot retrieves available process/version list from the server and displays them in the tray
  2. User triggers P1.Vx
  3. Do I have P1.Vx downloaded?
    Yes: Run
    No: Download and Run

Implementing an actual push would be more complicated but the result is the same (except a small delay at the first run)

1 Like
22

Thanks!

I actually don’t care about doing a push… I was just trying to wrap my head around how it all works so I could use it. This nuance (from the perspective of attended robots) doesn’t seem to be explained in any video or document I’ve come across.

23

Agree :slight_smile:

UiPath - Front Office vs Back Office Robot.pdf (89.0 KB)

06 AM
06 AM2580×1440 665 KB

2 Likes
24

Thanks again!

Here’s one additional nuance I’m curious about now that I understand it:

We are told that Orchestrator will aggregate the Log output of multiple attended (FOR) robots. From what I can see in Orchestrator… each log item has datetime, process, and user. The process & user fields are therefore critical to for an RPA support person to use when trying to assist a human who is having a problem with their attended robot’s performance.

So… that leads me to believe that each human’s computer where an attended robot will run shall be registered into Orchestrator with that human’s own Windows account/credentials.

That’s the only way we would be able to differentiate log items from different humans running attended robots of the same process.

My concerns:

  1. If we must register the human’s computer into Orchestrator using that human’s credentials (so we can differentiate log items)… doesn’t that mean that the human would have to be the person registering their machine to Orchestrator (i.e. so they don’t have to tell an administrator their password)? What if we never had plans to allow our humans to play any role administering/configuring Orchestrator?

  2. What if humans’ passwords are forced change every 30-90 days due to IT policies? Presumably those humans would need to return to Orchestrator every time their password changes so the attended robot can continue to receive package updates, use Orchestrator Assets, and log items, etc.

Am I misunderstanding how the machines running attended robots will connect to Orchestrator?

25

For FOR you don’t need to store the credentials. just register the robot and leave the password blank. Credentials are only used to auto-login a Windows session in the BOR case.

1 Like
26

Excellent! Another hurdle removed. Thanks!

27

Thanks. Looks like ‘Orchestrator’. Can someone from UiPath confirm if ‘Front Office Server’ and ‘Orchestrator’ are same?

28

If you read between the lines in his replies to my questions… Badita already indirectly confirmed it. I was asking Orchestrator/FOR questions, and he was replying how I can satisfy my FOR needs, using Orchestrator.

See also his replies in the other FOR thread.

1 Like
29

Perfect thread :slight_smile: thanks…

30

@badita my original post in this thread was actually meant as idea rather than ‘How-To’. Can we change thread category to ‘Idea’? if not, may be I can re-post my idea in separate thread.

1 Like