UiPath-ASAPv1 UiPath Automation Solution Architect Professional v1.0 Exam Questions and Answers

A development Specification Document (DSD) is a critical document for a smooth implementation of an RPA project. It should contain the automated process details and focus on two main categories: runtime guide and development details1. The runtime guide should provide information about how the robot will run, such as the input and output files, the configuration settings, the error handling, the logging and reporting, the credential management, and the Orchestrator usage. The development details should provide information about how the robot was built, such as the packages, the environment, the source code repository, the workflow components, the reusable components, the invoke tree, the custom logs, and the background versus foreground automation.

References: 1: Studio - Automation Lifecycle - UiPath Documentation Portal

 In a long-running context, a job can be suspended when it is waiting for human validation or intervention. This means that the job is paused until a human user performs an action, such as approving or rejecting a document, providing some input, or resolving an exception. A suspended job can be resumed by the user or by the orchestrator, depending on the configuration of the process. A suspended job is different from a stopping or stopped job, which means that the job is being terminated or has been terminated by the user or by the orchestrator. A suspended job is also different from a running job, which means that the job is executing normally without any interruption or delay. References: Long-Running Workflows - UiPath Documentation Portal, Managing Jobs - UiPath Documentation Portal, Long Running Workflow - UiPath Activities

According to the UiPath documentation and the UiPath Academy course, unattended automation is best suited for back-office processes that do not require human intervention or supervision, such as data processing, report generation, file management, etc. Unattended automation can run in the background, on a different machine than the user, and can be scheduled or triggered by events12. The high-level solution diagram you provided shows a process that involves extracting data from an input file using a machine learning model, updating information in a storage bucket, uploading files to SharePoint, and adding the document path to a processing queue. These tasks do not require any user interface interaction or human input, and can be performed by an unattended robot without any disruption to the user’s work. Therefore, unattended without UI interaction is the recommended type of automation for this scenario.

References:

• Attended, Unattended and Hybrid - UiPath1
• UiPath Automation Solution Architect | UiPath Academy2

According to the UiPath documentation1, App Builder is a feature of UiPath Apps that allows a user to create forms and components for user interfaces in applications. App Builder is a low-code app development tool that enables users to design and publish custom apps using drag-and-drop controls, data bindings, conditional logic, and automation workflows. App Builder also provides a preview mode to test the app functionality and appearance before publishing. Users can create apps for various form factors and devices, such as desktop, mobile, web, or sidebar. App Builder also integrates with UiPath Studio, UiPath Orchestrator, and Data Service to leverage the power of automation and data management in the apps. References: 1: App Builder - UiPath Documentation Portal

The single-node deployment option is recommended for evaluation and demo scenarios because it is simpler and faster to set up and requires less resources. It involves installing the Automation Suite on a single server node, which hosts both the cluster management services and the UiPath products and shared components. This option is not suitable for production use, as it does not provide high availability, scalability, or fault tolerance. It also does not support special workloads that require GPU capabilities, such as Task Mining analysis and Document Understanding pipelines. References:

• Automation Suite - Deployment architecture - UiPath
• Automation Suite - Supported use cases for single-node and multi-node installations - UiPath

UiPath Process Mining is a technique to analyze, improve, and track processes. It uses the data already stored in systems and applications to automatically show how processes are really executed. It also uses AI-powered process modeling techniques and flexible dashboarding experience to reveal process bottlenecks and optimization opportunities. It can be used in any industry and any functional area, and it can be deployed in various options12

References:

• Process Mining Tool - Business Process Mining | UiPath
• What is Process Mining - RPA and Process Mining | UiPath

Storage buckets provide a per-folder storage solution for RPA developers to leverage in creating automation projects1. In the diagram, the Storage Bucket is used for updating information and uploading/moving unprocessed files. This is related to the classification data that is created and validated in the Action Center by the SME (Subject Matter Expert). The classification data is used to train the machine learning model that extracts data from the documents2.

References:

• About Storage Buckets
• UiPath Apps (Storage Bucket). Introduction

This answer aligns with UiPath's emphasis on ensuring that automation solutions adhere to compliance standards and safeguard against security vulnerabilities and data privacy concerns, as outlined in UiPath's documentation and best practices for automation development.

Long-running workflows are processes that require logical fragmentation or human intervention (validations, approvals, exception handling) such as invoice processing and performance reviews. UiPath provides a dedicated project template in Studio called Orchestration Process, which enables the use of a set of activities to handle these scenarios. The Orchestration Process template allows the workflow to be suspended and resumed based on certain conditions, such as the completion of a job, a queue item, a form task, or an external task. The template also integrates with UiPath Action Center, which is a feature that enables human intervention in long-running unattended workflows. The Orchestration Process template is the recommended option for designing and developing long-running workflows in UiPath Studio. References:

• Orchestrator - Working With Long-running Workflows
• New Component - Long Running Workflow Template with UiPath Tasks
• Long Running Workflow Template for Task Creation - UiPath Marketplace

When designing an RPA solution, it's important to focus on maintainability, modularity, scalability, efficient exception handling, and comprehensive error reporting. These principles ensure that the automation solution can be easily updated, extended, and maintained over time. Modularity allows for parts of the solution to be reused across different projects, while scalability ensures that the solution can handle increased workloads as necessary. Efficient exception handling and error reporting are crucial for identifying and resolving issues quickly, ensuring the reliability and stability of the automation.

References:

• UiPath Best Practices: Automation Best Practices
• UiPath Studio Guide: Project Organization

The interaction between UiPath Studio and the UiPath Robot Service performs the function of executing or debugging a process. UiPath Studio is the design tool that allows users to create, edit, and test automation workflows. UiPath Robot Service is the component that runs the automation workflows on the machine. It communicates through an inter-process communication channel with Studio, the UiPath Assistant, and Robot Command Line Interface to receive and process information, and then to provide the necessary instructions to the Robot Executor. When a user wants to execute or debug a process from Studio, the Robot Service receives the command and launches the Robot Executor in the appropriate mode and session. The Robot Executor then performs the actions defined in the workflow and sends back the status and logs to the Robot Service, which in turn relays them to Studio. References:

• Robot - Robot Service - UiPath Documentation Portal
• Studio - Debugging - UiPath Documentation Portal
• Robot - Executing Processes - UiPath Documentation Portal

To access Automation Cloud, you do not need a dedicated infrastructure, an on-premises installation, or an offline access. You only need an internet connection with TLS and a compatible web browser. Automation Cloud is a cloud-based platform that delivers the full UiPath Platform, including SaaS robots and self-hosted robots, in under a minute, from any of six regions around the world. You can access it from any supported browser, such as Google Chrome, Microsoft Edge Chromium, Mozilla Firefox, or Apple Safari. Other browsers that are not listed, older versions of the listed ones, or mobile browsers are not supported and may cause errors or malfunctions. References: Automation Cloud - Software requirements - UiPath Documentation Portal, Complete cloud-based enterprise automation solution | UiPath

 According to the UiPath documentation1, Automation Ops is a component of the UiPath platform meant for creating, deploying, and managing Robotic Process Automation (RPA) governance policies in UiPath Studio, UiPath StudioX, and UiPath Assistant. You can use a single, simple web portal to manage and implement governance rules based on user profiles, such as defining the acceptable feeds, packages, widgets, and activities, restricting the applications and URLs that can be automated, and assigning roles and responsibilities for reviewing and approving the automation projects. Automation Ops also integrates with Git repositories and CI/CD pipelines to provide source control and automation delivery capabilities. Therefore, the correct answer is D. Configure and deploy governance policies, as this is one of the main functionalities of Automation Ops. References: 1: Automation Ops - UiPath Documentation

The correct flow from a high level design standpoint in UiPath Test Manager1 is:

Step 1 = Create Project Step 2 = Create Requirement Step 3 = Create TestCase Step 4 = Create TestSet

According to the UiPath documentation and the Test Manager Overview Demo1, the high level design flow in UiPath Test Manager1 involves the following steps:

• Create Project: A project is a container for all the testing artifacts related to a specific application or process. You can create a project in Test Manager by giving it a name, a description, and a type (RPA or Application). You can also import a project from another source, such as Jira or Azure DevOps 2.
• Create Requirement: A requirement is a statement of what the application or process should do or achieve. You can create a requirement in Test Manager by giving it a name, a description, and a custom attribute. You can also import a requirement from another source, such as Jira or Azure DevOps 2.
• Create TestCase: A test case is a set of steps or actions that verify a specific requirement. You can create a test case in Test Manager by giving it a name, a description, a type (manual or automated), and a custom attribute. You can also import a test case from another source, such as Studio or Task Capture 2.
• Create TestSet: A test set is a collection of test cases that are executed together as part of a testing cycle. You can create a test set in Test Manager by giving it a name, a description, a type (manual or automated), and a custom attribute. You can also import a test set from another source, such as Orchestrator 2.

References:

• 2: UiPath Test Manager - UiPath Documentation Portal
• 3: Task Capture - UiPath Test Manager - UiPath Documentation Portal
• 1: Test Manager Overview Demo - Test Automation Case | UiPath

According to the UiPath Automation Solution Architect Learning Plan, a good flowchart should have consistent design elements, clear logic, and appropriate symbols for each step. The flowchart in the question lacks decision points, which are usually represented by diamond shapes, and does not explain how to handle different scenarios or exceptions. For example, what happens if the email is invalid, the CRM login fails, or the user information is incorrect? Without decision points and explanations, the flowchart is incomplete and ambiguous.

References:

• RPA Solution Architect Learning Plan
• Importance of Solution Architecture
• Flowchart Tips - Five Tips for Better Flowcharts
• Keep it simple & follow these flowchart rules for better diagrams
• Ultimate Flowchart Tutorial

The UiPath Automation Suite is designed to offer a comprehensive solution that includes all server products, shared capabilities for seamless integration with enterprise systems, a unified end-user

This answer is correct because the Object Repository allows for creating and reusing UI taxonomies inside and across automation projects. By referencing Library B, which contains the Object Repository for application C, process A can reuse the UI elements defined there without creating a new Object Repository or using selectors. This way, process A can benefit from the centralized management, reusability, and reliability of the UI elements in the Object Repository12

References:

• Studio - About Object Repository - UiPath Documentation Portal
• Object Repository | UiPath UI Library | UiPath Academy

The use case of the diagram is Invoice Processing. The diagram represents a typical workflow in a document processing scenario using UiPath RPA tools. It shows the process starting from document collection from emails and SharePoint folders, processing attachments, classifying documents, and handling exceptions until the final step of invoice type classification.

The workflow involves various components of UiPath such as queues in Orchestrator for managing work items, actions by Subject Matter Experts (SMEs) for validation, and use of the Storage Buckets for storing information. It also shows the handling of different document types and exceptions, which is typical in invoice processing scenarios where not all documents are standardized and may require human intervention.

References: UiPath Automation Solution Architect materials which include best practices for setting up workflows and queues, document processing, classification, validation, and exception handling, all of which are relevant to Invoice Processing scenarios. These are covered in the UiPath Academy's Automation Solution Architect course and in the official UiPath documentation at https://docs.uipath.com/ .

In UiPath Apps, dynamic messages can be created using expressions. The String.Format function can be used within a VB expression to dynamically insert the user's name into a message displayed on a label control, based on the input from a textbox.

High Availability (HA) in the context of UiPath Orchestrator is a setup designed to ensure that the system remains available and operational, even in the event of hardware failures, software crashes, or other unexpected issues. HA is achieved by implementing a multi-node Orchestrator deployment, where multiple instances of Orchestrator are run in parallel. This setup provides redundancy, meaning if one node fails, the others can take over, ensuring continuous operation. The key benefit of HA is its ability to resist failures and maintain stability, which is crucial for critical enterprise operations relying on RPA.

References:

• UiPath Orchestrator Guide: High Availability
• UiPath Orchestrator Guide: Setting Up High Availability

According to the UiPath documentation, making an ML Skill public allows it to be accessible via an endpoint from outside of UiPath environment. This means that you can call it without the need to go through a robot connected to the specific tenant1. To do that, you need to select Modify current deployment in the ML Skill Details page > Update skill window, and enable the Public skill option. This will generate an API Key and URL that you can use to connect to the ML Skill from a different tenant1.

References:

• AI Center - Managing ML Skills
• What are the steps in moving a ML Skill to a new Tenant?
• AI Center ML Skill export question
• UiPath tenant move for AI Center

UiPath Orchestrator offers several deployment options to cater to different organizational needs for scalability, reliability, and disaster recovery. These options include single-node deployments for smaller or less critical environments, multi-node deployments for increased throughput and redundancy, and High Availability (HA) deployments that ensure the Orchestrator remains operational even in the event of failures. For organizations requiring robust disaster recovery solutions, UiPath provides options for High Availability with Disaster Recovery in both Active/Passive configurations, where one data center is on standby, and Two Active Data Centers, where both data centers are operational, providing seamless failover capabilities.

References:

• UiPath Orchestrator Guide: About Deployment Options
• UiPath Orchestrator Guide: High Availability and Disaster Recovery

The estimation table in the image shows the breakdown of hours required for different sub-processes and components in a UiPath automation project. The criteria that are taken into account are the number of sub-processes, the number of applications used, the integration and functional tests, and the contingency. The number of clicks in the application(s) is not a relevant criterion for the estimation, as it does not reflect the complexity or the effort of the automation. Moreover, the number of clicks may vary depending on the selectors, the UI elements, and the data inputs.

References:

• UiPath Automation Solution Architect Course, Module 3: Estimation and Planning
• Roles of a Solution Architect in Automation, RPA Setting, section: The importance of solution architecture

According to the UiPath documentation and the UiPath Academy course, there are four types of feeds that can be used to deploy a package in Orchestrator:

• Tenant feed: This is the default feed for all tenants in Orchestrator. It is hosted on the Orchestrator server and can store both processes and libraries. It can be accessed by all users within the tenant12.
• Folder feed: This is a feed that can be configured for a specific folder in Orchestrator. It can store only processes and can be accessed only by users within the folder. It can be useful for isolating packages for different environments or projects13.
• Personal workspace feed: This is a feed that can be configured for a personal workspace in Orchestrator. It can store only processes and can be accessed only by the user who owns the workspace. It can be useful for testing and debugging packages before publishing them to other feeds14.
• Custom feed: This is a feed that can be configured by adding an external source, such as Azure DevOps, Artifactory, MyGet, etc. It can store both processes and libraries and can be accessed by users who have the credentials for the external source. It can be useful for integrating with third-party tools or services1 .

References:

• Automation Ops - Orchestrator Feeds - UiPath Documentation Portal1
• Queues and Transactions - UiPath Documentation Portal2
• Folders - UiPath Documentation Portal3
• Personal Workspaces - UiPath Documentation Portal4
• External Feed For Packages - UiPath Community Forum

According to the UiPath documentation1, the Jobs History widget is a component of the Automation Cloud UI that shows the executions you initiated and their status. You can use this widget to monitor the progress and outcome of your automation jobs, such as successful, failed, stopped, or pending. You can also filter the jobs by date range, status, or process name. The Jobs History widget also provides a link to the Orchestrator service where you can view more details and manage your jobs. References: 1: Jobs History Widget - UiPath Documentation Portal

UiPath Unassisted Task Mining is a cloud-based service that collects and analyzes employee desktop data to identify tasks with high automation potential. The Admin Portal and Analyzer are web applications that are used to manage and review the Unassisted Task Mining projects. They are delivered as part of the UiPath Automation Cloud, which is built and hosted on Microsoft Azure. Microsoft Azure is a cloud computing platform that provides various services and solutions for building, deploying, and managing applications and data. UiPath Automation Cloud leverages Microsoft Azure’s security, scalability, and reliability features to offer a seamless and secure user experience. (https://docs.uipath.com/task-mining/automation-cloud/latest/user-guide/unassisted-task-minining-introduction)

References:

• Unassisted Task Mining - Introduction - UiPath Documentation Portal
• UiPath Automation Cloud - Introduction - UiPath Documentation Portal
• Microsoft Azure - Overview

When a task is assigned to a user in UiPath Action Center, its status changes to "In Progress." This status indicates that the task has been acknowledged by the user and is currently being worked on. Action Center is designed to facilitate human-in-the-loop scenarios, where human intervention is required to complete tasks that cannot be fully automated. The "In Progress" status helps track the progress of these tasks, ensuring that they are moving towards completion.

References:

• UiPath Action Center Guide: Managing Actions
• UiPath Action Center Guide: Task Statuses

UiPath Action Center is a platform that enables human-robot collaboration for unattended automation. It allows users to provide inputs to robots, handle business process exceptions, and initiate unattended processes through form-based input and file upload. Action Center also offers a central portal where users can track and monitor complex workflows across business units, tasks, people, and robots.

References:

• Action Center - Introduction
• Human Robot Collaboration - Unattended Automation
• Action Center - UiPath

Option D is the correct answer because it shows the scheduling option using the “Advanced” option. This option allows the user to specify a cron expression that defines the exact time and frequency of the process execution. The cron expression for this scenario is 0 0/15 7-18 ? * MON-FRI *, which means the process will run every 15 minutes starting at 0 minutes past the hour, from 7 AM to 6 PM, on every weekday. The other options are incorrect because they do not match the required schedule. Option A uses the “Hourly” option, which will run the process every hour at 15 minutes past the hour, not every 15 minutes. Option B uses the “Daily” option, which will run the process once a day at 15 minutes past 7 AM, not every 15 minutes. Option C uses the “Weekly” option, which will run the process once a week on Monday at 15 minutes past 7 AM, not every 15 minutes. References: UiPath Automation Solution Architect Learning Plan, Module 5: Operationalization1; UiPath Automation Suite - Scheduling Processes2; UiPath Academy - Roles of a Solution Architect in Automation, RPA Setting3.

When UiPath Robots are deployed in Service Mode, they operate as a Windows service. This configuration allows the Robot to execute jobs assigned via Orchestrator independently of any user session on the machine. The Robot in Service Mode does not require a user to be logged in to the machine to start and execute processes, enabling unattended automation scenarios. This capability is particularly useful for automations that need to run at scheduled times or be triggered by specific events without human intervention.

References:

• UiPath Robot Guide: Robot Service Modes
• UiPath Orchestrator Guide: About Jobs

Scalability is the ability of a system or a process to handle growing amounts of work or demand in a graceful manner. Scalability impacts the design of a UiPath automation flowchart because it determines how well the automation can cope with increased process volume, complexity, or variability. A scalable flowchart design should consider the following strategies:

• Modularization: Breaking down the process into smaller, reusable, and maintainable components that can be easily modified or replaced if needed. Modularization also facilitates testing, debugging, and error handling.
• Parameterization: Using variables, arguments, configuration files, assets, or queues to store and pass data that can change depending on the process execution. Parameterization allows for flexibility and adaptability of the automation to different scenarios or environments.
• Optimization: Reducing unnecessary or redundant steps, activities, or data in the flowchart to improve the performance, efficiency, and reliability of the automation. Optimization also involves choosing the best methods or techniques to achieve the desired outcome, such as using selectors, data scraping, or computer vision.
• Orchestration: Managing the resources, schedules, triggers, and dependencies of the automation to ensure that it runs smoothly and effectively. Orchestration also involves monitoring, logging, and reporting the status and results of the automation, as well as handling exceptions and alerts.

References: Enhancing UiPath Solutions’ Design Scalability, Roles of a Solution Architect in Automation, RPA Setting, Studio - Flowcharts.

The "EditGrid" component in UiPath Apps is designed to enhance data interaction within an app. It allows users to view, edit, and manage data in a tabular format directly within the app interface. This functionality is crucial for apps that require data manipulation, as it enables end-users to make real-time updates and changes to the data without the need for external tools or interventions. The EditGrid fosters a more dynamic and interactive user experience, making it easier to handle data-intensive tasks within UiPath Apps.

References:

• UiPath Apps Guide: EditGrid Component
• UiPath Forum: How to Use EditGrid in UiPath Apps

UiPath AI Center is a platform within the UiPath Automation Suite that enables the deployment, management, and monitoring of artificial intelligence (AI) models in conjunction with RPA workflows. AI Center allows users to bring AI capabilities into their automation processes, facilitating the use of machine learning models to enhance decision-making, data processing, and task execution within automations. This integration of AI with RPA opens up new possibilities for automating complex processes that require cognitive capabilities, such as natural language understanding, prediction, and classification tasks.

References:

• UiPath AI Center Guide: About AI Center
• UiPath AI Center Guide: Deploying and Managing Models

UiPath AI Center is a service that allows users to deploy, manage, and consume machine learning models within RPA workflows in Studio. Users can bring their own models, use the pre-built models provided by UiPath, or select third-party models from the UiPath Marketplace. The UiPath Marketplace is a platform where users can find and install ready-made components, such as activities, workflows, connectors, dashboards, and machine learning models, that are integrated with UiPath products. The Marketplace offers models from various third-party integration platforms, such as AWS, Azure, Google Cloud, IBM Watson, and more. References: RPA & AI Integration with AI Center, AI Center - About AI Center, UiPath Marketplace

The Isolated option for the Invoke Workflow File activity allows the invoked workflow to run in a separate Windows process, which can help with isolating a faulty workflow from the main workflow. However, this option requires that the arguments passed to the invoked workflow are serializable, meaning that they can be converted into a binary format that can be transferred across processes. Simple types, such as integers, strings, booleans, etc., are serializable by default. Reference types, such as arrays, lists, dictionaries, etc., are serializable if they implement the ISerializable interface or have the [Serializable] attribute. Class types are serializable if they meet the same criteria as reference types. Data Row is an example of a non-serializable type that cannot be used as an argument for an isolated workflow. References: Invoke Workflow File, Using Arguments, What is the the use of “isolated” property of invoke workflow, How to pass arguments to Isolated Workflow.

UiPath Automation Cloud offers a range of services designed to support and enhance the automation lifecycle, including Data Service, Test Manager, and Orchestrator. Data Service provides a no-code data modeling and storage solution that enables easy data management and integration within automations. Test Manager supports the planning, execution, and management of automated testing, ensuring the quality and reliability of RPA solutions. Orchestrator is the central component for deploying, managing, and monitoring RPA bots and processes, providing the infrastructure for enterprise-grade automation management.

References:

• UiPath Automation Cloud Guide: Services Overview
• UiPath Data Service Guide: Introduction to Data Service
• UiPath Test Manager Guide: Introduction to Test Manager
• UiPath Orchestrator Guide: About Orchestrator

For UiPath license estimation, two key best practices include assessing the number and complexity of processes to determine the required types of robots (e.g., Attended, Unattended, Studio, StudioX) and evaluating concurrent robot usage during peak workloads. Understanding the complexity of the processes helps in choosing the right type of robots that align with the tasks' needs, ensuring efficient automation. Concurrent usage assessment is crucial for optimizing resource allocation, especially during peak periods, to maintain high efficiency and productivity without overprovisioning resources. This strategic approach to licensing can significantly enhance the scalability and cost-effectiveness of RPA initiatives.

References:

• UiPath Licensing Guide: Robot Types and Licensing
• UiPath Best Practices: License Management

 UiPath Data Service is a cloud-based data platform that enables users to store and manage structured and relational data for their RPA projects. Entity Records are the basic units of data in Data Service, which consist of fields and values that represent a specific object or concept. Users can create custom Entity Records to store data that is relevant to their automation scenarios, such as customer information, order details, invoice data, etc. Users can also use suitable queries to retrieve and manipulate existing Entity Records as needed, such as filtering, sorting, aggregating, updating, or deleting data. Users can also leverage the relationships between Entity Records to access related data across different entities, such as joining, expanding, or embedding data. References: Data Service - Entities - UiPath, Data Service - Queries - UiPath, Data Service - Relationships - UiPath

In UiPath Orchestrator, calendars are used to define working and non-working days for robots. To accommodate non-working days, such as weekends or holidays, a user can create a new calendar and manually mark these days. Additionally, for ease and efficiency, a .csv file containing all non-working days can be prepared and uploaded to Orchestrator. This feature is particularly useful for planning and scheduling unattended robots, ensuring that they operate according to the organization's working calendar.

References:

• UiPath Orchestrator Guide: Managing Calendars
• UiPath Orchestrator Guide: About Calendars

 UiPath Automation Hub is a collaborative tool that helps users discover and manage automation opportunities and process improvements, prioritized by impact and ROI. It also facilitates collaboration across SMEs, developers, and the CoE, and provides a central repository for process documentation and reusable components.

References:

• Automation Hub - Automation Pipeline Management | UiPath
• Automation Hub - Introduction
• UiPath Automation Hub Overview | UiPath Academy

In UiPath Data Service, an "Entity" represents a data model that defines the structure of data stored within the service, similar to a table in a relational database. Entities are used to model and manage business data in Data Service.

 UiPath Apps is a platform that enables users to build and share enterprise-grade custom applications that connect to data in any underlying cloud or on-premises system using the power of automation. Users can create apps using a web browser, a rich library of drag-and-drop controls, and automations from the UiPath Platform. UiPath Apps supports APIs, legacy applications, and data sources that are not easily programmable. Users can also run their apps on any device, and integrate them with other UiPath products such as UiPath Assistant, UiPath Automation Hub, and UiPath Process Mining. References: Apps - Introduction - UiPath, Introducing UiPath Apps: A Robot-Powered Low-Code Platform