Before Starting with Robot View

Before starting with robot view, get acquainted with the following Robot Status, Robot Action, Robot Status Action Mapping, Agent Actions, Scheduling and Listening methods.

Following diagram explains you about the steps involved in creating bot and its various statuses in Robot View tab:

Robot Status

In Control Tower, the robot can be in any of the following status:

Status	Description
Available	A robot in available status is present in the common pool from where it is assigned to a Control Tower user with relevant access.
Setup	A robot assignee takes the ownership of the robot in setup status using valid credentials and sets it up to perform required processes.
Running	A robot in running status is ready to execute the incoming process requests.
Stopped	A robot in stopped state cannot execute the incoming requests.
Error	A robot in error state is no longer able to pick up the requests for automation. Error state of a robot is due to the following reasons. If the robot farm machine on which it is deployed, is not responding. If ‘n’ consecutive request execution fails.
Total Robots	Total Robots status implies the total number of robots created in the Control Tower.

Robot Actions

Following table shows various actions of robots which the robots can perform.

Action	Description
Assign	A robot can be assigned to a control tower user. Only the robot assignee can take the ownership of the robot and schedule the robot.
Release	Release the robot to the available pool if the robot is not needed anymore.
Start	Start the robot to execute the incoming process automation robots.
Stop	Stop the robots if execution of automation requests is not required.
Upgrade	Upgrade the robot to download the latest executable and settings from the server. To upgrade the robots, see Update Management section in the Control Tower.
Disconnect	Disconnect the robots from the profile queues by using disconnect option.
Connect	Connect the robot to the profile queues by using the connect option.
Edit	Edit the robot to modify the robot name or the associated tags.
Reset	Click User can reset the authentication credentials used to take the ownership of the robot. Only the robot assignee can reset the authentication credentials for taking the ownership of the robot.
Delete	Click Delete to delete a robot.
Robot Configuration	Allows you to change the robot configurations such as robot’s log level mode. Select the preferred log level mode from following: All Critical Error Information Off Click Save to save the robot configuration; or click Cancel to discard the changes.
More	Allows you to reset the robot schedule. Click More > Reset to reset the robot schedule.
Ascending order	Enables you to arrange the robot list view in ascending order.
Descending order	Enables you to arrange the robot list view in descending order.
Grid View	Enables you to view the robot list in a grid view.
Filter	Enables you to filter and view the robot list as per your preference.

Robot Status – Action Mapping

Following table shows the actions that can be performed by the user with relevant access in the particular status of Robot View. For example, in the Available Status, logged-in user with valid access can assign the robot to self or other, edit or delete the robot details.

	Assign	Release	Start	Stop	Connect	Disconnect	Edit	Delete	Reset	Robot Configuration
Available	✓	x	x	x	x	x	✓	✓	x	x
Set-up	x	✓	x	x	x	x	✓	x	x	x
Running	x	x	x	✓	✓	✓	✓	x	x	x
Error	x	x	x	✓	x	x	✓	x	x	x
Stopped	x	✓	✓	x	x	x	✓	x	✓	✓

Robot Scheduling

Schedule a Robot to execute processes of a particular profile for a specific period on a daily or weekly basis.
Create a schedule either while setting up the robots or while the robot is in the stopped status. Schedules are in multiples of 30 minutes. Consider the following examples of the schedules:

Everyday 00:30 – 03:30 from 20th August 2017 to 19th August 2018
Every Monday, Wednesday, and Friday from 13:00 – 18:00 from 9th January 2017 to 30th June 2017

Conflicting schedules for a robot cannot be created. An example of conflicting schedule is as following.

Everyday 00:30 – 03:30 from 20th August 2017 to 19th August 2018
Every Monday from 02:00 – 03:00 from 21st August 2017 to 20th September 2017

In the above example, the schedule on 21st August 2017 from 02:00 – 03:00 Hrs. is conflicting with the previous schedule. Define the time-zone to execute the schedule. Multiple profiles can be assigned to the same robot.

Listening Method

A listening method defines the order in which process requests from various profiles are listened to and are executed by the robot. Multiple profiles can be assigned to the same robot. If a robot is listening to multiple profiles in the same schedule, then assign a listening method.

There are three listening methods available under a schedule such as:

Listening Method	Description
First come first serve	The profiles are executed in the order of their arrival. Profiles coming first will be picked on First come first serve basis. Configuration - First Come First Serve on basis of requests: For FCFS mode to be running based on the timestamp of the request, irrespective of the profile. The changes have to be done in respective Robot(s) RoboSE.exe.config the field <add key="isTrueFCFS" value="false" /> need to be updated to <add key="isTrueFCFS" value="true" />
Round robin	The process requests are executed one by one from each profile queue. The order of the execution is configurable.
Priority	The process requests are executed as per the priority of the profile. The priority order of the profiles is configurable.