Managing Bots

The bot runs a process configuration in a session on the computer where the bot is installed.

If bots should run processes in a hidden session, assign the bot at least one Secure Session.

The number of Secure Sessions that can be assigned and served by the bot depends on the hardware of the computer on which the bot is installed. Please refer to the system and hardware requirements topic to assess the maximum number of Secure Sessions for the bot.

Enabling the same setting via the RPA Bot Configurator, limits but not overwrites this setting.

Assign service times to bots to determine when a bot may execute processes.

Service times are repeatable time intervals that define when a service is available. Assign them to bots to determine when a bot can execute processes. Specify the service time in one time zone. If the bot that you assign the service time to is installed on a computer that uses a different time zone, the service time interval is converted to the bot’s time zone. If you assign the service time to multiple bots in different time zones, all bots execute processes simultaneously. The time intervals might change, depending on daylight saving time.

For example, if you specify a service time that starts at 9:30 AM and ends at 5:30 PM in Buenos Aires time (ART (UTC -3)) and the bot is installed on a computer in Berlin (CET (UTC +1)), the bot executes processes between 1:30 PM and 9:30 PM in Berlin time.

Learn how to manage service times.

Assign process applications to bots that can access them.

You can deploy a process on a bot that has assigned the required applications.

Downtimes are repeatable time intervals that define when an application is unavailable. Processes whose applications are currently down are executed to completion and not restarted until the downtime period ends.

Specify a downtime in the time zone in which it occurs. If the bot that you assign the downtime to is installed on a computer that uses a different time zone, the downtime interval is converted to the bot’s time zone. If you assign the application to multiple bots in different time zones, all bots pause executing processes that use that application simultaneously. The time intervals might change, depending on daylight saving time.

For example, if you specify a downtime that starts at 1:30 AM and ends at 5:30 AM in Tokyo time (JST (UTC +9)) and the bot is installed on a computer in San Francisco (PST (UTC -8)), the bot does not execute processes between 8:30 AM and 12:30 PM in San Francisco time.

Learn how to manage applications.

Update your bots to the latest version to get the newest features, bug fixes, and security enhancements. The bot finishes all processes before updating and resumes them afterwards to avoid data loss.

Alternatively, you can update single bots manually by downloading and installing the newer version from the Download Applications pane in the Home module of RPA Manager.

You can automatically update bots that fullfil the following requirements:

To update one or more bots automatically:

RPA Manager creates an update task for each bot to be updated as soon as possible.

You can view the status of the update task in the details view of each bot in the Bots view of the Bot Management module.

Edit a bot to change its properties. Hostname, IP address, version, and timezone are fixed values taken from the computer the bot is installed on.

After deinstallation or reconfiguration, a bot is still shown in the Bots view. You need to manually remove the bot from the view. Deleted bots are removed from process configurations. Any active processes are terminated.

If you accidentally remove a bot that is running, the bot shuts down and the API Key is deleted on the bot’s computer. You must uninstall and reinstall the bot with a new API Key. In this case, reassign the licenses, name, description, assigned process applications and service times, and tasks.