Automation Anywhere Interview Questions & Answers 2026

The Bot Insights is a platform which provides the real time, interactive and the insight details regarding the Business processes. The Bot insight provides the details about the content and productivity data about the bots that has been deployed. Also it gives details about the process, interacted data by the bot and the data that bot has generated. From this data, the analytics are generated and it can be observed with the help of customizable dashboards.

The Activity tab from the Control Room Dashboard has In Progress, Historical, and Insights tab. The In Progress activity shows the bots that are currently running. The bot status has the different status such as Started, Active, Paused, Unknown, Paused for Input, Pending Execution and Queued. Historical Tab : The Historical tab shows the bots that are executed and exported from the Control Room. The status of Historical tab includes the various statuses such as: Completed, Failed, Stopped, Timed out, Unknown, Deploy failed and Pending execution.

The Roles and Permissions are manages in the AA Control Room by using the Role Based Access Control (RBAC). The AAE_Admin role has permissions to create, view, edit, delete and enable or disable user. The AAE_Basic role has the permissions to upload and download Task Bots and other few permissions such as view packages, view and run the bots, register device, view bot store, etc. AAE_Bot Developer has permissions to Run, Import bots and Create folders, Create attributes for credential, View and Manage Packages, View basic information of Users and Roles. AAE_Locker Admin can view all the credentials and lockers. Also they can View basic information of Roles and Users. AAE_Pool Admin can view and manage all the device pools. They can view and manage Bot Runners, Bot Creators, and device pools. Can create device pools and Administer all device pools. AAE_Queue Admin has permissions to manag

The Repository is managed by the by the Role Based Access Control (RBAC). The users will be provided the access as per the requirement and permissions needed. This will be good to manage the control room.

To run the task from Control Room, we should be logged in to the Control Room as Bot Creator or Bot Runner user. The Task can be executed from the Creator user from the Private Repository using command of Run bot. The Task can be executed from the Runner user from the Public Repository using the Run bot option.

The scheduling Tasks in control room refers to the tasks that we can set a specific time to run the task bot on their own. This scheduling has options to set as Daily, Weekly or only on specific day to run. Along with the day, we can set the time to run the bot with different time zones individually.

The Audit Trail refers to the Log or the Activity details that are performed by the bot in the run time. The Audit trail/log gives the information about the each action performed by the bot. If the bot is failed and we need to check up-to which action the bot has processed, so we can easily check it by looking at the Audit log details. Let's Find The Course You Want: Let’s Get Started

The creating Task refers to the Create New tab from the Control Room’s Automation dashboard. For creating the Task Bot, we need to navigate to the Create New and select the Task Bot from the options. This will create a Task bot where we will be performing and adding the steps as per requirement from the end user.

The edit task option is available in the Private Repository only and in the Public Repository, we can only see & Run the code but unable to edit. In the Private Repository, we need to open the code and then we can edit the code as per requirement.

The Run Task option is available in the Private as well as in the Public Repository. Run Task from Private Repository: The task can be executed on the same machine on which the code is being edited. Run Task from Public Repository: The task can be executed on any available runner machine from the Public Repository in the Attended or Unattended mode.

The task can be scheduled from a Bot Runner user login. After login to the Control Room with Bot Runner login credentials, we can navigate to the Schedule Bot Run option and set the tasks to run on the particular days, weeks or months of the year.

The Wait for Condition is the command in which we can delay the bot until a specific condition is True before executing the next action. This includes various conditions such as Application running or not running, Boolean condition, Data Table conditions, Datetime condition, Dictionary condition, DLL Session condition, File condition, Folder condition, Image Recognition, JavaScript condition, List, Number, String condition, etc. Loops: The Loop action is used to repeat the set of actions in a loop until a break occurs. The Loop can be run n number of times or for the CVS/Text file data, for Data-table or Database, for Dictionary, for Email, for data in Excel, for Files and Folders, for List, for Microsoft 365 Calendar, Excel, Outlook and for XML data.

The If Else command is used to execute the set commands only when the condition inside If condition is satisfied. Otherwise, the execution flow will navigate to the Else command and the commands inside Else will be executed. The various conditions under If condition are Boolean, Data Table, Datetime condition, DLL Session, File & Folder condition, Window condition, etc.

In order to generate the random string, we need to use the String package. This command generates a string of combination of uppercase and lowercase alphanumeric characters and it will be assigned to a string variable.

In order to get the system date into the String format, we need to use the Datetime: To string action from the Datetime package. In this conversion, we need to provide the System variable $System:Date$ as an Input and the output is in the form of string. For the output string, the different formats are available in the dropdown menu through which we can select the required one or we can get it in the Custom format as well.

If there is a need to convert the given set of string into the Lower case or Upper case, we can use the Lowercase command and Uppercase command respectively.

The required string can be found or extracted using the Find command from the String package. For reversing the given string, we have to use the Reverse command from the String package. The output is in the String format in both of the cases.

For the Desktop Application Automation, we can use the Open program/file command from the Application package. After opening the application, then with the help of Recorder, Keystroke we can perform the navigation and other operations involved in the process.

The various commands related to Files and Windows are as follows: File: Using the File package, we can automate various file related operations. The various operations can be performed such as Copy desktop file to another location, Create / Delete a file, Copy the file from Control Room to specific location, get the name & path of file, open the existing file, print the file, rename file, and create a shortcut to a target file. Windows: The different tasks related to Windows in Web Automation can be performed such as activating the window, close application window, Minimize / Maximize / Resize / Restore window, and assigning a new window title to a window variable, etc.

The Pause Task command is used to pause the execution of the currently processing task. Delay: The delay is the amount of time a bot waits before moving to the next task. It is a static delay. Wait: Using this package commands, we can add a condition to wait for an application screen to change or the specific window to open / close before moving to the next action. The wait acts as a Dynamic delay. Microsoft Power Automate Course Learn More

In Automation Anywhere, the Database can store variety of data such as sales transactions, product catalogues, customer profiles and inventories. Using the Database package, we can connect to a database; manipulate the stored data by retrieving, deleting, inserting, exporting and updating it to the CSV file. Also we can Begin database transaction and End database transaction.

The Prompt package is used for the operations such as entering the value from user in the run time, requesting a yes or no response, for selecting the one or more files during the bot execution, and to choose the folder during run time. These commands are used in the attended mode run only.

The Record variable will save the data of one row at a time from a Data table variable. The Data table variable will save the data from an entire excel file in the form of rows and columns , and it can be referenced using the Headers or index.

Initially, the entire code will be in the Try Catch block. The input file will be read and then inside the Loop of “For each row in Data Table” , there should be an another Try Catch block , so that any exception occurs, it will be logged and then the bot will continue for the next record without breaking the loop.

Structured Documents: These type of documents will have a fixed layout and the data positions will be predictable. eg. Purchase Orders, Bank Statements Semi-structured Documents: These types of documents will have a repeating patterns but the layouts will be variable. eg. Medical claim forms Unstructured Documents: These types of documents will have a free format of text without any fixed format of layout. eg. Contracts, Letters

In the Document Automation, the Learning Instance holds the information about the different “Form Fields” and “Table Fields” which needs to be extracted from the invoices. It also holds the detailed information about the Field Properties, Field Rules and Document Rules that can be modified as per the requirement for extraction. It also holds the other information such as Confidence score, Custom Aliases for each Form Field and Table Field.

The Confidence Score in Document Automation refers to the accuracy of the required data that we need to extract from a provided document. The value of the confidence score lies between 1 to 100 depending on the input data. If the Confidence score is on higher side, it indicates that there is more accuracy. The Confidence score can be used for validating the extracted data & its accuracy . If the Confidence score is set at a particular threshold value (90%), which means, if the extraction falls below 90%, then it goes for the human validation.

Initially we need to create a Learning Instance by providing the required Form and Table fields. Then using the command "Document Extraction: Extract data" from Document Extraction, provide the name of the "Learning Instance" from the dropdown list in the "Server instance" details . This command can be used in a loop for multiple files in a folder along with standard coding practices.

The extraction logic can be customized using the one or many Field rules combining by using either AND or OR condition . The different field rules can be used such as: equal to, not equal to, contains, starts with, ends with, is empty , etc. In addition, with this, we can use the If Then logic and perform the regex extract, set value, show warning or replace .

Initially, create a learning instance without selecting any template . Then add the form and table fields one by one as per the requirement ( at least one needed for each ). Also add the Aliases in the form and table fields. If required, add the field rules in the learning instance for the particular fields. Also, check for the confidence score for the different fields and update if required.