Glossary
In the world of AutomatR Studio, it's helpful to understand key terms and concepts to navigate and leverage the software effectively. Here's a brief glossary of essential terms:
A
AutomatR Bot: A software component responsible for executing automation workflows created in AutomatR Studio.
AutomatR Orchestrator: A cloud-based platform for managing, monitoring, and scheduling automation tasks performed by AutomatR Bots.
Automation Workflow: A sequence of actions, decisions, and data manipulations designed in AutomatR Studio to automate tasks or processes.
Attended Bot: A type of AutomatR Bot that works alongside humans, requiring user interaction.
AI and Machine Learning Models: Integration of artificial intelligence and machine learning into automation workflows for decision-making and data analysis.
API Integration: The connection of AutomatR Bots with external systems and applications via APIs for data exchange and task execution.
Arguments: Variables used to pass data between different parts of an automation workflow, such as from one workflow to another.
AutomatR AI Fabric: A platform for building, deploying, and managing AI models for use in automation workflows.
Agility: The ability to quickly adapt and modify automation workflows in response to changing business requirements.
Automation Pipeline: A sequence of automation tasks that are executed in a specific order to perform a complex business process.
Advanced Recorder: A feature in AutomatR Studio that allows for the recording and automation of more complex user interactions.
API Automation: The use of APIs to connect and automate interactions with external systems, applications, and web services.
Audit Compliance: Ensuring that automation workflows meet regulatory requirements and auditing standards.
Automated Testing: The practice of using RPA to automate software testing processes, ensuring the functionality and quality of applications.
Audit Trail: A chronological record of actions and events within an RPA system, used for accountability, compliance, and troubleshooting.
AutomatR Activities: Pre-built components used to build automation workflows in AutomatR Studio, such as "Click," "Type Into," "Get Text," and many others.
Asset: A secure storage mechanism in AutomatR Orchestrator for managing configuration data, such as API keys, database connections, and other variables.
Asset Value: The actual data or information stored within an asset in AutomatR Orchestrator, such as a connection string or a password.
Advanced Recorder: A feature in AutomatR Studio that allows for the recording and automation of more complex user interactions and application scenarios.
Automation Chain: A sequence of automation tasks that are linked together to achieve a larger business process or workflow.
Annotation: A comment or description added to activities in AutomatR Studio to provide context and explanations within automation workflows.
Authentication Token: A security token used to verify the identity of a user or system during interactions with external services or APIs.
Automated User Provisioning: The process of automatically creating and managing user accounts, access rights, and roles for RPA tools and platforms.
Automated Regression Testing: A type of testing in which RPA is used to re-run previously executed tests to ensure that changes have not introduced new issues.
Automation Test Environment: A separate environment used for testing and validating RPA workflows and updates before deploying them to production.
B
Bot: An alternative term for a AutomatR Bot, often used informally.
Business Process Mapping: The visual representation of a business process, often used as a foundation for creating automation workflows.
Business Analyst: A role involved in defining, documenting, and analyzing business processes to identify automation opportunities.
Bot Performance Analytics: Metrics and insights that help measure and optimize the performance of AutomatR Bots.
Back-End Automation: Automation tasks that occur in the background, often involving data processing and system integrations.
Bot Management: The practice of monitoring, configuring, and maintaining AutomatR Bots for optimal performance and resource utilization.
Business Continuity: A set of practices and strategies to ensure that RPA and other critical business operations can continue in the event of disruptions or disasters.
Batch Processing: The processing of data or tasks in batches, often used in data-driven RPA tasks that involve large volumes of data.
Business Process Reengineering (BPR): The redesign and optimization of business processes before automating them with RPA.
Bot Experience (BotX): The user experience (UX) and design considerations when building and deploying attended RPA solutions.
Business Process Outsourcing (BPO): The practice of contracting third-party organizations to perform specific business processes, which can be enhanced through RPA.
Business Continuity Planning (BCP): The development of strategies and procedures to ensure the continuous operation of RPA processes in the face of disruptions.
Bot Directory: A catalog or repository where information about all deployed RPA bots, including their status and usage, is maintained.
Batch Automation: The practice of automating repetitive tasks that are performed in batches, such as bulk data processing.
Bot Credentials: Securely stored authentication details that allow RPA bots to access systems, applications, and data sources.
Background Process: An automation task in AutomatR Studio that runs without a visible user interface, often used for batch processing and data manipulation.
Blob Storage: A service for storing large amounts of unstructured data, often used in RPA for archiving documents and data.
Business Rules Engine: Software or components that automate decision-making in RPA processes based on predefined business rules and logic.
Bot Runner: A component in AutomatR Orchestrator responsible for executing automation processes on Bots.
Bot Security Model: A framework that defines and enforces security policies for RPA bots to protect sensitive data and operations.
Bot Store Certification: The process of validating and certifying RPA bots and automation components for quality and security.
Bot Queue Management: The administration and monitoring of queues in RPA processes to ensure tasks are processed efficiently.
C
Credentials: Secure storage for username-password pairs and other sensitive data used in automation workflows.
Citrix Automation: Automation of tasks in virtual desktop environments using Citrix technology.
Custom Activity: A user-defined or third-party activity created to extend the functionality of AutomatR by adding new actions or features.
Cognitive Automation: The use of artificial intelligence, natural language processing, and machine learning to enhance the decision-making capabilities of automation.
Custom Workflow Activity: A custom-built activity that encapsulates a sequence of actions and can be reused within automation projects.
Cloud Orchestrator: AutomatR Orchestrator hosted in a cloud environment, providing scalability and accessibility from anywhere.
Cognitive Services: AI-based services that enable applications to understand and interpret natural language, images, and other forms of data.
Compliance Reporting: The generation of reports and documentation to demonstrate adherence to regulatory requirements, often relevant in RPA for audit purposes.
Change Management: Strategies and practices for smoothly transitioning to new automated processes and workflows within an organization.
Cognitive RPA: A type of RPA that incorporates cognitive computing, such as natural language processing and machine learning, for more intelligent automation.
Containerization: The use of containers (e.g., Docker) to package and deploy RPA components and dependencies consistently across different environments.
Chatbot Integration: The incorporation of chatbots or virtual assistants into RPA solutions to enable human-like interactions and support.
COE (Center of Excellence): A dedicated team or unit within an organization responsible for managing and optimizing RPA initiatives.
Condition: A logical statement in AutomatR Studio that determines whether specific actions or activities should be executed based on predefined criteria.
Credentials Activity: An activity in AutomatR Studio used to securely manage and pass login credentials and other sensitive data in automation workflows.
Computer Vision Activities: A set of AutomatR activities that enable Bots to interact with and understand user interfaces even when no selectors are available.
Continuous Integration (CI): A software development practice where code changes are automatically integrated and tested, commonly used in RPA development.
Code Reusability: The practice of writing and organizing code in a way that allows for easy reuse of components and functions across different projects.
Custom Dashboard Widget: A customizable element on a dashboard in AutomatR Orchestrator, displaying specific data or insights relevant to an organization's needs.
Change Management in RPA: The processes and procedures for implementing changes and updates to RPA workflows, ensuring minimal disruption.
D
Debugging: The process of identifying and fixing errors or issues in automation workflows.
Data Scraping: The process of extracting structured data from web pages, applications, or documents for use in automation.
Debug Console: The user interface within AutomatR Studio for monitoring and troubleshooting automation workflows during debugging.
Desktop Automation: The category of automation that focuses on interacting with applications and systems on the desktop or user interface level.
Data Table: A data structure used to store, manipulate, and analyze tabular data in automation workflows.
Distributed Automation: The deployment of automation tasks across multiple machines or Bots to distribute the workload and enhance scalability.
Dynamic Data: Data that can change frequently, requiring automation to adapt to varying values or conditions.
Development Pipeline: A structured process for designing, building, and testing automation workflows before deployment.
Decision Trees: A visual representation and logic structure used in RPA to make decisions based on a series of conditions.
Dependency Management: The process of identifying and managing the relationships and interdependencies between automation tasks and components.
Disaster Recovery Planning: Strategies and procedures to ensure the availability and continuity of RPA operations in the event of catastrophic events.
Data Cleansing: The process of identifying and correcting errors or inconsistencies in data before using it in RPA tasks.
Data Transformation: The process of converting data from one format or structure to another, often used in RPA for data integration.
DevOps Automation: The integration of RPA into DevOps practices, enabling the automation of software development, testing, and deployment processes.
Data Extraction Template: A predefined structure or pattern used by RPA bots to extract data from documents, emails, or web pages.
Data Encryption: The practice of encoding data to protect it from unauthorized access and ensure its security during RPA processes.
Dynamic Selector: A selector in AutomatR Studio that uses variables or wildcards to identify and interact with changing or dynamic UI elements.
Debugger: A feature in AutomatR Studio that allows developers to step through and troubleshoot automation workflows, identifying and resolving issues.
Database Automation: The practice of automating tasks related to database management, such as data extraction, loading, and transformation (ETL).
Data Validation: The process of ensuring the accuracy and integrity of data used or produced in automation workflows.
Data Extraction Framework: A structured approach or methodology for extracting data from various sources, such as documents or databases, using AutomatR.
Data Scrubbing: The process of cleaning and enhancing data to ensure its quality and accuracy in automation workflows.
Data Connector: A software component or utility used to establish connections and access data from external sources, databases, or APIs.
Document Object Model (DOM): A hierarchical representation of the structure and content of a web page or application, used in web automation.
Data Masking: The practice of disguising sensitive data in a way that protects privacy while still enabling processing in automation workflows.
Data Source Activity: An activity in AutomatR that connects to and retrieves data from various sources, including databases, web services, and APIs.
Data Dictionary: A comprehensive repository of data definitions, metadata, and descriptions used to ensure consistency in data handling.
Data Encryption Key: A cryptographic key used to encrypt and decrypt data in RPA processes to ensure data security.
Data Extraction Pattern: A predefined template or structure used to extract specific data from documents, forms, or web pages in RPA.
Dynamic Load Balancing: A strategy in RPA for distributing automation tasks among available Bots based on current workload and capacity.
Data Ingestion: The process of collecting and importing data from various sources into an RPA workflow for analysis and processing.
Dynamic Task Assignment: The allocation of automation tasks to Bots based on real-time availability, skills, and priority.
Data Migration Automation: The use of RPA to automate the migration of data from one system or platform to another.
Data Transformation and Mapping: The process of converting, reformatting, and aligning data to make it compatible for use in RPA processes.
E
Element Exists: An activity in AutomatR Studio that checks the presence and visibility of a specific user interface element in an application.
Excel Automation: Automating tasks involving the creation, manipulation, or extraction of data in Microsoft Excel spreadsheets.
Error Handling: Strategies and mechanisms for managing and resolving errors and exceptions that may occur during automation workflows.
Edge Computing: The practice of processing data and running automation tasks closer to the data source, rather than in a central data center.
Environment: A configuration in AutomatR Orchestrator that allows you to manage and group Bots and processes with specific settings and variables.
Exception Handling Strategy: A predefined plan for dealing with errors or exceptions that may occur during automation processes.
Exception Reporting: Generating reports or notifications when exceptions or errors occur in RPA processes for quick resolution.
F
Flowchart: A visual representation in AutomatR Studio that displays a sequence of actions, decisions, and flow control logic within an automation process.
Front-End Automation: Automation tasks that involve interacting with user interfaces and applications visible to end-users.
Feature Flag: A configuration setting in RPA software that allows selective enabling or disabling of specific features or functionalities.
Form Automation: The automation of data entry and processing within digital forms and web-based applications using AutomatR.
Form Designer: A tool or component for creating and customizing digital forms for automation purposes.
H
Hotkey: A keyboard shortcut used in automation to trigger specific actions within applications.
Hybrid Cloud Deployment: A setup where a combination of on-premises and cloud resources are used for hosting AutomatR Orchestrator and Bots.
High-Density Bot: A Bot deployment model that allows multiple Bots to run concurrently on a single machine, suitable for maximizing resource utilization.
Hotfix: A minor software update or patch that addresses specific issues or bugs in AutomatR Studio or Bot.
Hot Desking: A workplace setup where employees do not have assigned workstations, often relevant when configuring attended Bots.
Hyperautomation: A strategic approach that combines RPA with advanced technologies like AI, machine learning, and analytics for end-to-end automation.
High-Availability Orchestrator: A configuration that ensures the continuous operation of AutomatR Orchestrator by using redundant servers and resources.
Hyperconverged Infrastructure (HCI): An integrated system combining computing, storage, and networking resources, often used for RPA infrastructure.
Human-in-the-Loop (HITL): An RPA scenario where human intervention is required at specific points in the automation workflow.
I
Invoke Workflow: An activity that allows you to call and execute a separate automation workflow within the main workflow.
Incident Management: The process of handling and resolving issues, errors, or exceptions that occur during the execution of automation tasks.
Intelligent Process Automation (IPA): A combination of RPA and AI technologies to automate complex, cognitive tasks.
Intelligent Character Recognition (ICR): A technology that converts handwritten text or printed characters into machine-encoded text, used in data extraction tasks.
Image Recognition: The capability to identify and interact with visual elements, such as icons or buttons, within applications or web pages.
Intelligent Automation: The combination of RPA and artificial intelligence (AI) technologies to perform tasks that require understanding, learning, and decision-making.
Infrastructure as Code (IaC): The practice of defining and managing RPA infrastructure (e.g., virtual machines) using code and automation scripts.
Input Dialog: An activity in AutomatR Studio used to collect user input through a pop-up dialog box during the execution of an automation process.
Invoke Code: An activity in AutomatR Studio that allows you to write custom code or scripts in languages like C# or VB.NET within an automation workflow.
Invoke PowerShell: An activity in AutomatR Studio used to execute PowerShell scripts within automation workflows for advanced system interactions.
Input Validation: The process of verifying and ensuring that user input or data used in automation workflows is accurate and safe.
Image-Based Automation: The practice of automating tasks in RPA based on the recognition and manipulation of images and visual elements.
J
Job Schedule Template: A predefined configuration for scheduling and running automation jobs in AutomatR Orchestrator.
K
KPI (Key Performance Indicator): Metrics used to measure the success and effectiveness of automation projects, such as task completion time or error rates.
L
Log File: A record of events, actions, and errors generated by automation workflows, used for troubleshooting and auditing.
Low-Code / No-Code: A development approach that enables users to create automation workflows with minimal coding or programming skills.
Long-Running Task: An automation task that extends over a prolonged period, possibly involving tasks that span hours or days.
Logical Data Mapping: The process of defining how data flows and is processed within an organization, often used in RPA projects.
Low-Level Automation: Automation at the technical level, involving tasks like data extraction, system interactions, and script execution.
Legacy System Integration: The process of connecting and automating tasks within older, often outdated, software systems.
Low-Code Integration: The practice of integrating RPA with other systems and applications using low-code or no-code development tools.
Library: A reusable collection of custom activities and workflows in AutomatR Studio that can be shared and used across multiple projects.
Library Management: The practice of creating, updating, and publishing libraries in AutomatR Studio for code reusability and collaboration.
Logical Operator: A symbol (e.g., AND, OR, NOT) used to combine and manipulate conditions and expressions in AutomatR Studio.
Long-Running Process: An automation workflow that executes for an extended duration, typically handling complex or time-consuming tasks.
M
Monitoring Dashboard: A user interface in AutomatR Orchestrator that provides real-time insights into the performance of automation jobs and Bots.
Metadata: Information about data, files, or processes that is used for tracking and managing automation tasks.
Multitenancy: The capability of AutomatR Orchestrator to support multiple organizations or tenants within a single instance, each with its own isolated resources and configurations.
Machine Learning Model Training: The process of teaching AI models to make predictions or decisions based on historical data.
Machine Learning Algorithm: A set of rules and statistical methods used by machine learning models to make predictions or decisions.
Master Data Management (MDM): The practice of managing and ensuring data accuracy, consistency, and reliability across an organization's systems and applications.
Multi-Tenancy Support: The ability of RPA platforms to serve multiple clients or organizations from a single instance, each with separate configurations and data.
Multi-Bot Synchronization: The coordination of multiple Bots to perform tasks in a synchronized and organized manner, often used in parallel processing scenarios.
Machine Template: A pre-configured virtual machine image that can be used to deploy Bots in a standardized manner.
Maintenance Mode: A state in AutomatR Orchestrator where Bots and processes are temporarily paused for maintenance or updates.
Message Box: A dialog box in AutomatR Studio that displays information, prompts, or alerts during the execution of an automation workflow.
Machine Learning Model Integration: The incorporation of machine learning models into AutomatR workflows to enhance data processing and decision-making.
Manual Intervention Point: A designated stage in an automation workflow where human input or decision-making is required.
Message Queue: A communication mechanism that allows different components in a system to send and receive messages, often used in automation for task queuing.
Multi-Environment Configuration: The ability to manage and deploy automation projects across different environments, such as development, testing, and production.
N
NoSQL Database: A type of database used for storing unstructured or semi-structured data, often integrated with RPA for data handling.
O
Orchestrator Assets: Secure storage in AutomatR Orchestrator for managing and accessing configuration data, credentials, and other sensitive information.
Object Repository: A centralized storage location for managing and reusing user interface elements and selectors in automation workflows.
Optical Character Recognition (OCR): A technology that converts printed or handwritten text into machine-readable data, often used for document processing.
Orchestrator API: A set of endpoints and functions that allow external systems to interact with the AutomatR Orchestrator platform.
Orchestrator Jobs: Individual instances of automation tasks that are executed and managed within AutomatR Orchestrator.
Orchestrator Tenant: A separate, isolated workspace within AutomatR Orchestrator that allows organizations to manage their automation processes and resources independently.
Orchestrator API Key: A secure authentication key used to authorize external systems or applications to interact with AutomatR Orchestrator via API calls.
Orchestrator Queue Trigger: A mechanism in AutomatR Orchestrator that initiates the processing of queue items based on specified conditions or events.
Orchestrator Credential Store: A secure storage mechanism in AutomatR Orchestrator used to manage and access credentials for use in automation processes.
OCR Engine: Optical Character Recognition (OCR) software that enables the recognition and conversion of text from scanned images or documents into machine-readable text.
Orchestrator API Endpoint: A specific URL where external systems or applications can interact with AutomatR Orchestrator using API calls.
Orchestrator Process Set: A logical grouping of similar processes within AutomatR Orchestrator for ease of management and monitoring.
Orchestrator Global Variable: A variable that can be accessed and modified across all processes within AutomatR Orchestrator.
Orchestrator Dashboard: A customizable interface in AutomatR Orchestrator that displays key performance indicators and insights on automation processes.
Orchestrator Permissions: Permissions and access control settings that define who can perform specific actions and operations in AutomatR Orchestrator.
Orchestrator Resource Pool: A logical grouping of Bots and resources within AutomatR Orchestrator for efficient management.
Orchestrator Tenant Admin: An administrator responsible for managing the resources and settings within a specific tenant in AutomatR Orchestrator.
P
Package: A collection of reusable automation components, including activities, libraries, and custom code, which can be easily shared and imported into projects.
Production Environment: The environment where fully tested and stable automation workflows are executed as part of routine operations.
Process Mining: The practice of using data logs and event data to analyze and optimize business processes, often used in conjunction with RPA.
Predictive Analytics: The use of data analysis and statistical algorithms to predict future outcomes or trends, often applied in RPA to make informed decisions.
Parallel Processing: The simultaneous execution of multiple tasks or processes within an automation workflow for increased efficiency.
Process Complexity Analysis: The evaluation of a business process to determine its suitability for RPA based on factors like decision-making and rule complexity.
Process Efficiency Metric: A key performance indicator (KPI) that measures the effectiveness of RPA processes in terms of time saved or costs reduced.
Process Discovery Bot: A specialized Bot that's used for the initial identification and documentation of processes for automation.
PDD (Process Design Document): A comprehensive document that outlines the details of a specific process to be automated with RPA.
Pattern-based Automation: An approach in RPA where patterns or regularities in data and processes are identified and used to automate tasks.
Process Mapping Tool: Software used to visually represent and document business processes, making it easier to identify automation opportunities.
Post-Implementation Review (PIR): An assessment conducted after an RPA project is deployed to evaluate its success, identify issues, and plan for improvements.
Q
Queue: A container in AutomatR Orchestrator that holds work items, facilitating job scheduling and management.
Queue Items: Individual work items within a queue, representing specific tasks or data.
Queue Trigger: An event-driven mechanism in AutomatR Orchestrator that initiates the execution of automation jobs when new items are added to a queue.
Queue Prioritization: The process of assigning priorities to queue items, determining the order in which they are processed by Bots.
Queue Item Status: The state of a queue item, indicating whether it is new, in progress, successful, or has encountered an error.
Queues Management: The process of creating, populating, and managing queues in AutomatR Orchestrator to control the order and processing of items.
Queue Item Priority: A designation that determines the importance and order of processing for items within a queue.
R
Resource Utilization: Monitoring and managing the use of system resources by AutomatR Bots to ensure efficiency and performance.
ReFramework: A pre-built template for creating automation projects with a standardized structure, error handling, and logging.
RPA (Robotic Process Automation): The technology and approach of using software robots (AutomatR Bots) to automate repetitive, rule-based tasks.
Reusability: The ability to use components, workflows, or activities in multiple automation projects, promoting efficiency.
ROI (Return on Investment): A measure of the financial benefits gained from implementing RPA, often expressed as a ratio of cost savings to initial investment.
Root Cause Analysis: The process of identifying the underlying reasons for errors or issues in automation tasks.
Role-Based Access Control (RBAC): A security model that restricts system access and permissions based on user roles and responsibilities.
Robotic Desktop Automation (RDA): A form of RPA that focuses on automating tasks directly on an employee's desktop or computer.
Robotic Process Orchestration (RPO): The coordination and management of multiple automation processes, often spanning across departments or systems.
RPA Governance: The framework and policies for managing RPA initiatives, including roles, responsibilities, and compliance.
Robotic Service Orchestration (RSO): The practice of integrating RPA with service-oriented architecture (SOA) to automate complex business processes.
RPA as a Service (RPAaaS): The delivery of RPA capabilities as a cloud-based service, allowing organizations to access and use RPA tools and resources remotely.
Robotic Process Monitoring (RPM): The continuous tracking and analysis of RPA operations and performance to detect and address issues.
Robotic Process Optimization: The iterative process of refining and improving RPA workflows to achieve greater efficiency and accuracy.
Robotic Process Discovery (RPD): The use of software tools to automatically identify and analyze business processes for potential automation opportunities.
Robotic Automation Framework (RAF): A standardized set of guidelines and best practices for designing and building RPA solutions.
Resource Allocation Algorithm: An algorithm used to assign RPA tasks to available bots and resources, optimizing workload distribution.
Robotic Process Governance: The practices and policies for ensuring RPA adherence to legal, ethical, and regulatory standards.
Resource File: A file in AutomatR Studio used to store variables, arguments, and other resources that can be reused across multiple automation projects.
ReFramework Template: A robust and standardized template in AutomatR Studio for building automation projects with enhanced error handling, logging, and recovery capabilities.
Revert to Snapshot: A feature in AutomatR Orchestrator that allows you to return a virtual machine to a previously captured state for testing or recovery.
Real-Time Dashboard: A visual display of live data and key performance indicators (KPIs) to monitor the status and performance of automation processes.
Role-Based Dashboard: Customized dashboards in AutomatR Orchestrator that provide specific views and insights based on user roles and responsibilities.
Real-Time Analytics: The monitoring and analysis of automation process data as it occurs, providing immediate insights and alerts.
Resource Allocation Policy: A set of rules and guidelines for distributing automation tasks to available Bots and resources.
Recurring Schedule: A scheduling mechanism in AutomatR Orchestrator that allows automation processes to run at specified intervals or on a regular basis.
Robotic Workforce: The collective term for the Bots and virtual workers that perform automation tasks in an organization.
Requeue: The action of placing a failed or retried queue item back in the queue for further processing in RPA.
RPA Productivity Metrics: Metrics used to evaluate the efficiency and productivity of RPA, such as tasks completed per hour or cost savings.
Robotic Automation Solution: An end-to-end automation system that combines RPA, AI, and other technologies to address specific business challenges.
RPA Center of Excellence (CoE) Charter: A formal document that outlines the mission, goals, and guidelines for an organization's RPA Center of Excellence.
Recovery Strategy: A plan for addressing and recovering from failures, errors, or interruptions in RPA processes.
S
Studio Bot: A Bot used for development and testing within AutomatR Studio.
Selectors: String expressions used in AutomatR Studio to identify and interact with user interface elements in applications, websites, and systems.
State Machine: A design pattern in AutomatR Studio for creating automation workflows that can switch between various states or stages, often used for complex processes.
Scalability: The ability to easily expand or reduce the number of Bots and resources to accommodate changing workloads and demands.
Screen Scraping: The process of extracting data from the visual display of an application, often used for automating legacy systems.
State Transition: In state machines, a change from one state to another based on specific conditions or triggers.
Scaling Out: Increasing the number of Bots or resources to accommodate growing automation workloads.
Scripting: Writing code or scripts, often in languages like VBScript or JavaScript, to extend automation capabilities.
Screen Recorder: A tool in AutomatR Studio for capturing user interactions and generating automation workflows.
SLA (Service Level Agreement): A formal agreement that defines the expected performance standards and response times for automation processes.
Schedule Trigger: A mechanism in AutomatR Orchestrator that initiates the execution of automation jobs at specific times or intervals.
Swarm Robotics: A concept in automation where multiple Bots work collaboratively and intelligently to achieve a common goal.
Stakeholder Buy-In: The process of gaining support and commitment from relevant individuals or departments for RPA initiatives.
Self-Healing Automation: Automation that can detect and correct errors or exceptions during execution without human intervention.
Service Desk Automation: The use of RPA to automate tasks related to IT service desk operations, such as incident resolution and user support.
State Activity: An activity in AutomatR Studio used within a state machine to represent a specific state or stage of an automation process.
Source Control: The use of version control systems (e.g., Git) to manage and track changes to automation projects in AutomatR Studio.
SQL Query Activity: An activity in AutomatR Studio used to interact with databases by executing SQL queries and retrieving or modifying data.
Script Task: An activity in AutomatR Studio that allows the execution of custom scripts or code using languages like VB.NET or C#.
State Transition Matrix: A visual representation in AutomatR Studio that depicts the flow and possible transitions between different states in a state machine workflow.
Stateful Bot: A Bot in AutomatR that can maintain state information between automation tasks, enabling complex, multi-step processes.
Session Variables: Temporary variables used to store data for the duration of an automation session, often for quick data retrieval.
T
Test Automation: The practice of using automation tools to perform software testing, ensuring the functionality and quality of software applications.
Triggers: Automation rules or events that initiate the execution of workflows or tasks in response to specific conditions.
Test Data: Data used specifically for testing automation workflows, ensuring that they operate correctly under various conditions.
Time Series Analysis: A technique used in RPA to analyze historical data and identify patterns or trends for informed decision-making.
Task Scheduling: The process of setting specific times for automation tasks to run, optimizing resource allocation and performance.
Task Automation: The practice of using RPA to streamline and automate specific tasks or processes, reducing manual effort.
Transaction Logging: The recording of detailed information about each step or transaction performed in an automation workflow, used for auditing and debugging.
Triage: The process of categorizing and prioritizing issues, errors, or incidents encountered during RPA operations.
Test Automation Framework: A set of guidelines, practices, and tools for structuring and managing automated testing processes in RPA projects.
Try-Catch: A structure in AutomatR Studio used for error handling, allowing you to catch and manage exceptions in automation workflows.
Task Dependency: The relationship between automation tasks, where one task depends on the completion or outcome of another.
Test Data Generation: Creating realistic and diverse datasets for testing RPA processes, ensuring that different scenarios are covered.
Task Synchronization: The coordination of multiple automation tasks or Bots to work in parallel or in sequence to achieve specific goals.
U
Unattended Bot: A type of AutomatR Bot that operates independently and performs scheduled tasks without human intervention.
UAT (User Acceptance Testing): The final phase of testing before deploying automation workflows into a production environment, involving validation by end-users.
Unattended Execution: The operation of Bots that perform automation tasks without direct human interaction, often used for background processes.
Unattended Automation: Automation that runs without human intervention, often scheduled or triggered based on specific conditions.
V
Version Control: The management of changes and updates to automation workflows, ensuring traceability and collaboration.
VBO (Value-Based Outcome): A performance metric that measures the value or impact of automation initiatives on the organization.
Variable: A storage container in AutomatR Studio used to store and manipulate data, making it accessible throughout the automation workflow.
Variable Scope: The context or range within which a variable is accessible and can be used within an RPA workflow.
W
Workflow Activities: Pre-built building blocks used to create automation workflows, including actions, conditions, and loops.
Work Item Assignment: The allocation of specific tasks or queue items to individual Bots for execution.
Workload Management: The process of optimizing resource allocation and task distribution to ensure efficient performance of automation workflows.
Workflow Automation: The automation of a sequence of tasks, steps, or processes to streamline business operations.
Workflow Orchestration: The coordination and management of multiple automation workflows, often involving dependencies and triggers.
Workload Balancing: The allocation of tasks and processes to Bots or resources to ensure even distribution and efficient execution.
Web Automation: The practice of automating tasks involving interactions with web browsers and web-based applications, often used in AutomatR Studio.
Web API Automation: The practice of automating interactions with web-based APIs to exchange data and perform tasks.
Workflow Branching: The use of conditional logic to create multiple paths within an automation workflow, allowing different actions based on specific conditions.
X
XPath: A language used to navigate and query elements within XML documents and web pages, commonly used for element selection in AutomatR automation.
XAML: The file format used by AutomatR Studio to save automation workflows, containing a structured representation of the workflow logic.
XML Configuration File: A file in XML format used to store and manage configuration settings for AutomatR automation workflows.