Bots
The Bots tab in the AutomatR Orchestrator application is a powerful interface that allows you to add new bots, update their configurations, manage and oversee your bot workforce, comprising attended, unattended, and studio bots. This section empowers you to efficiently configure, monitor, and optimize the performance of your automation bots. Let's explore the key sections and functionalities available within the Bots tab:
| Field | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Connection | The Connection column indicates the current status of each bot's connection to the Orchestrator:
| ||||||||
| Name | The Name column displays the individual names or identifiers of each bot. This allows you to quickly identify and distinguish between different bots within your automation workforce. | ||||||||
| Bot Type | The Bot Type column identifies the type of each bot:
| ||||||||
| User Email | The User Email column displays the email addresses associated with each bot. This information helps you identify the users or stakeholders responsible for specific bots, streamlining communication and management. NOTE: This field is applicable only for Attended Bots. | ||||||||
| Instances | The Instances column shows the number of instances or machines on which each bot is deployed. A single bot may be deployed across multiple instances to handle varying workloads. NOTE: This field is applicable only for Unattended Bots. | ||||||||
| Bot | The Bot section in the Bots tab provides essential status information about each bot within your automation workforce. It includes status that help you identify and manage the bots efficiently. Let's explore the key components of the Bot section:
The status - Offline, Ready, and Running - provide crucial insights into the current operational state of each bot within your automation workforce. By monitoring and understanding these statuses, you can effectively manage and optimize your bots' performance, ensuring that they are available, reliable, and productive in executing automation tasks. The status help you quickly identify any connection issues, track bots' readiness for automation assignments, and determine which bots are actively carrying out tasks, providing valuable information for efficient automation workflow management in the Orchestrator application. | ||||||||
| Log Updated | The Log Updated section in the Bots tab provides crucial information about the last time each bot's log was updated. This section helps you identify the most recent tasks completed. The Log Updated column displays timestamps indicating when the log was last updated for each bot. NOTE: This field is not applicable for Studio Bots. |
The Bots tab provides a comprehensive interface for managing and overseeing the bots in your automation workforce. By tracking the bot status, names, bot types, user email addresses, and log updates, you can efficiently optimize your automation processes and ensure seamless coordination between the Orchestrator and your bots. The Edit and Delete options offer flexibility in customizing your bot configurations, while the Refresh Table button keeps you updated with real-time information. The search and advanced search features allow you to quickly find specific bots based on various criteria, enhancing your ability to manage your automation workforce effectively. With the Bots tab, you can achieve enhanced automation efficiency and productivity, empowering your organization to maximize the benefits of automation.
Add Bot
Adding a new bot to the AutomatR Orchestrator application enables you to expand your automation capabilities and include different types of bots for diverse tasks. Follow these simple steps to add a new bot:
Log in to your AutomatR Orchestrator application using your credentials.
Navigate to the Bots tab, typically from the main menu.
On the Bots tab, locate the Add button towards the top-right corner. Click on it to start the process of adding a new bot.
A form will appear, prompting you to enter the necessary details for the new bot:
Name: Provide a unique name or identifier for the new bot. Choose a name that helps you easily identify and differentiate this bot from others in your automation workforce.
Automation Type: From the drop-down menu, select the appropriate automation type for the bot. The available options are Attended, Unattended, and Studio. For more details refer Automation Type section.
Instance (Only for Unattended): Select the instance (the physical machine) where the bot will run the workflow. For adding a new instance, please refer to Instances section.
Credentials (Only for Unattended): Select the user credentials to be used for logging into the Instance (the physical machine) for executing the workflow. For adding a new credential, please refer to Credentials section.
User Email (For Attended & Studio): Enter the email address of the user for which this bot will be allocated. Once you add this, the user can login to Studio / Attended bot for building automations.
Double-check the information you entered for accuracy, ensuring that the bot's name and automation type are correct.
If necessary, make any corrections or adjustments to the details you provided.
Once you are satisfied with the bot's details, click on the Add button to finalize the addition of the new bot.
Upon successful addition, you will receive a confirmation message or notification stating that the new bot has been added to the Orchestrator.
Navigate back to the Bots tab and review the table to ensure that the new bot appears with the name and automation type you provided.
You have successfully added a new bot to your AutomatR Orchestrator application. This new bot is now ready to be utilized for automation tasks based on its designated automation type (attended, unattended, or studio). You can now proceed to configure and assign tasks to the bot to enhance your organization's efficiency and productivity. Remember to update any additional configurations or settings as needed to fully integrate the new bot into your automation ecosystem.
Update Bot
The Edit options in the Bots tab offer flexibility in customizing your bots configurations. The Actions column in the Bots table provides options to interact with individual bot, clicking the Edit option allows you to modify and update the details of a specific bot, such as its name or automation type. This functionality ensures that your bot records remain accurate and up-to-date.
NOTE: These actions cannot be performed when the bots are in use. You can disconnect the bot and can perform the edit action.
In the Actions column associated with the bot, click on the Edit option.
Upon clicking Edit, a form will appear displaying the selected bot's information.
A form will appear, prompting you to enter the necessary details for updating the bot:
Name: Update the name of the bot.
Automation Type: From the drop-down menu, select the appropriate automation type for the bot. The available options are Attended, Unattended, and Studio. For more details refer Automation Type section.
Instance (Only for Unattended): Select the instance (the physical machine) where the bot will run the workflow. For adding a new instance, please refer to Instances section.
Credentials (Only for Unattended): Select the user credentials to be used for logging into the Instance (the physical machine) for executing the workflow. For adding a new credential, please refer to Credentials section.
User Email (For Attended & Studio): Enter the email address of the user for which this bot will be allocated. Once you add this, the user can login to Studio / Attended bot for building automations.
Double-check the information you entered for accuracy, ensuring that the bot's name and automation type are correct.
Once you are satisfied with the bot's details, click on the Update button to finalize the updation of the bot.
Upon successful addition, you will receive a confirmation message or notification stating that the new bot has been added to the Orchestrator.
Navigate back to the Bots tab and review the table to ensure that the updated bot appears with the name and automation type you provided.
You have successfully updated the bot information.
Delete Bot
The Actions column in the Bots tab provides options to interact with individual bots, the Delete option from the Actions column of Bots table allows you to remove the bot from the AutomatR Orchestrator. Use this action when retiring a bot or when it is no longer required in your automation infrastructure.
NOTE: The delete action cannot be performed when the bots are in use. You can disconnect the bot and can perform the delete action.
View Logs
AutomatR Orchestrator's Bots Tab allows users to access and view logs generated by specific bots. Here's a step-by-step guide on how to view logs for a bot:
Navigate to the Bots tab, which displays a list of available bots and related information.
From the Bots table, select the specific bot for which you want to view logs.
Find the Actions column associated with the bot and click on the Logs option.
Clicking on the Logs option opens a new window displaying the selected bot's log information.
The log view provides various details about the bot's activity.
The main section of the log view window displays a table with columns representing different aspects of the bot's logs.
- Bot Name: The name of the bot associated with the log entry.
- Log Level: The severity level of the log entry (Verbose, Debug, Information, Error).
- Time Stamp: The date and time when the log entry was generated.
- Message: The log message detailing the event or action.
- Process: The specific process or workflow related to the log entry.
- Machine/Windows Identity: Information about the machine or Windows identity associated with the bot execution.
Within the log view window, you can utilize filters to narrow down the log information.
Use the Search by Log Level drop-down to filter logs based on their severity. Choose from options like Verbose, Debug, Information, and Error.
Verbose log level provides the most detailed and comprehensive information about the execution of a process. It includes extensive details, such as variable values and step-by-step actions, which is helpful for in-depth debugging and analysis.
Debug log level is used to capture information that is valuable during the development and testing phases. It provides insights into the application's internal workings and helps developers identify issues and track down bugs.
Information log level records important events and milestones during the execution of a process. It offers a higher level of detail than just success or failure, making it useful for monitoring the progress and performance of automation.
Error log level is critical for identifying and addressing issues that require immediate attention. It captures any unexpected behavior, exceptions, or failures in the automation process, allowing users to quickly identify and resolve problems.
Use the Search by Date option to specify a date range for the logs you want to view.
Download Excel
You can download the displayed log information in Excel format.
Click the Download Excel option, which allows you to save the log data locally.
Viewing logs for a bot from the AutomatR Orchestrator Bots Tab is a straightforward process that allows users to gain insights into the bot's activities, troubleshoot issues, and monitor performance. By following these steps, users can efficiently access and filter log information to analyze bot behavior, understand any errors, and make informed decisions for process optimization and improvement.
Automation Type
Automation Types refer to different categories of bots in the AutomatR Orchestrator that serve specific purposes and operate in distinct ways. Understanding the characteristics and use cases of each automation type is crucial for effectively utilizing your automation workforce. Here's a brief overview of the three available Automation Types:
| Type | Description |
|---|---|
| Attended Automation | Attended Automation involves bots that work alongside human operators, providing assistance and support during their tasks. These bots are typically triggered manually by users or through specific events, and they require human intervention to complete certain steps of the automation process. Use Case: Attended bots are best suited for scenarios where human involvement is necessary, such as tasks that involve decision-making, data verification, or handling exceptions that require human judgment. They can be used to augment employee capabilities, streamline repetitive tasks, and increase productivity while maintaining human oversight. |
| Unattended Automation | Unattended Automation refers to bots that operate without human intervention, executing automation tasks autonomously. These bots are designed to run 24/7 and can perform repetitive, rule-based tasks without the need for human interaction. The user needs to add the Instance and Credential once they select the Unatended Automation type. Use Case: Unattended bots are ideal for automating high-volume, rule-driven processes that can be executed with minimal human involvement. They excel in scenarios where tasks are time-sensitive or need to be performed continuously, such as batch processing, data extraction, and report generation. |
| Studio Automation | Studio Automation is not a standalone bot type, but rather a category that includes bots used during the development and testing phase of automation workflows in AutomatR Studio. These bots are used within the Studio environment to design, debug, and refine automation processes before deploying them to Attended or Unattended bots in Orchestrator. Use Case: Studio bots are used by developers and automation experts to create and refine automation workflows using the AutomatR Studio interface. They are crucial for building efficient and error-free automation solutions before deploying them to production. |
Selecting the Right Automation Type:
Choosing the appropriate Automation Type for a given task or process is essential for successful automation implementation. Consider the following factors when selecting the right automation type:
Task Complexity: For tasks requiring human judgment or interaction, Attended Automation is the preferred choice. For rule-based, repetitive tasks that do not require human input, Unattended Automation is more suitable.
Process Volume: If you need to handle large volumes of tasks continuously, Unattended Automation is the most efficient option, as it can run 24/7 without human supervision.
Process Maturity: Studio Automation is essential during the development phase of automation workflows, allowing developers to design, test, and refine the automation processes before deploying them to production bots.
By understanding the capabilities and strengths of each Automation Type, you can design a well-optimized automation strategy that leverages the right type of bots for specific tasks, resulting in increased efficiency, productivity, and cost-effectiveness in your automation initiatives.