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

The rule-based extraction and the model-based extraction are two different methods of data extraction that target different types of documents. The rule-based extraction is suitable for structured documents that have a fixed format and layout, such as forms, tax returns, or certificates. This method relies on rules (such as regular expressions) and templates (such as position or occurrence patterns) to identify and extract the data of interest from the document. The rule-based extraction ensures high accuracy and speed for already known documents, but it requires manual configuration and maintenance of the rules and templates, and it cannot handle variations or changes in the document format. The model-based extraction is suitable for semi-structured documents that have varying formats and layouts, but contain similar types of information, such as invoices, receipts, or purchase orders. This method relies on pre-trained models (such as machine learning or artificial intelligence models) or custom models (such as user-defined models) to analyze and extract the data of interest from the document. The model-based extraction can handle variations and changes in the document format, and it can learn from feedback and improve over time, but it requires training data and validation, and it may not achieve the same level of accuracy and speed as the rule-based extraction for some documents.  References :

Data Extraction Overview - UiPath Document Understanding

Document Processing with Improved Data Extraction | UiPath

Document Understanding - Machine Learning Extractor - UiPath

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

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 options 1 2

References :

Process Mining Tool - Business Process Mining | UiPath

What is Process Mining - RPA and Process Mining | UiPath

References :

Orchestrator - Queue Triggers

Orchestrator - UI Automation Triggers

Orchestrator - Form Triggers

Orchestrator - Event Triggers

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/ .

Machine Learning (ML) is a subset of artificial intelligence that enables systems to learn from data, identify patterns, and make decisions with minimal human intervention. Unlike traditional programming, where a developer writes the instructions to solve a problem, ML algorithms learn from the data. They improve their performance as the amount of data increases. This learning process involves training an ML model on a dataset, allowing it to learn from the examples provided. Once the model is trained, it can make predictions or decisions based on new, unseen data. This approach is powerful in handling complex tasks where defining explicit rules is challenging.

References:

UiPath AI Center Guide: Introduction to Machine Learning

UiPath AI Fabric: Machine Learning Models

According to UiPath Best Practices, the For Each activity should be used for implementing the Classification Loop in the high-level solution diagram. The For Each activity enables you to iterate through a collection of items and perform an action for each item. In this case, the collection of items would be the invoices from various clients that require processing. The action for each item would be to extract data using the ML model, process the extracted data, update the information in the storage bucket, upload or move the SharePoint files, and add the document path to the processing queue. Alternatively, if the extracted data is not processed, the action would be to create a validation in the Action Center and wait for the SME to review it. The For Each activity is suitable for this scenario because it allows you to process each invoice sequentially and handle any exceptions or validations that may occur. The For Each activity also has a Body property where you can add other activities or invoke workflows that are relevant to the Classification Loop logic.  References :  For Each - UiPath Activities ,  Design Best Practices - UiPath Documentation Portal ,  Automation Solution Architect - UiPath Academy

The Config.xlsx file is a data file that stores the settings, constants, and assets for an RPA project.  It is used to make the project more configurable, reusable, and maintainable 2 . By assigning folders to the assets sheet in the Config.xlsx file, you can easily manage the assets for different environments, such as development, testing, and production.  You can also change the asset values without modifying the code, which reduces the risk of errors and increases the efficiency of the development process 3 .

References :

1 : UiPath ReFramework Configuration File (Config.xlsx) Question - YouTube

2 : How to create Config File and How to Use it in UiPath? - UiPath Community Forum

3 : UiPath Variables - Get variable’s value from a string - UiPath Community Forum

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

Option B is the most suitable approach for the process described above, as it uses the Robotic Enterprise Framework (ReFramework) template with TransactionItem set as DataRow and TransactionData as DataTable. This template provides a robust and scalable structure for transactional processes, with built-in mechanisms for exception handling, logging, retrying, and reporting. By setting the TransactionItem as DataRow and the TransactionData as DataTable, the process can read the invoice numbers from the CSV file and process them one by one in a loop. The template also allows the use of queues to store the transaction data and status, which enables the process to resume from the last successful transaction in case of a system exception. This way, the process can ensure that each invoice number is processed only once in each application, and avoid duplicate or skipped transactions. The template also integrates with UiPath Orchestrator, which provides centralized management, monitoring, and scheduling of the process. The template also supports the use of long-running workflows, which can handle human intervention scenarios using UiPath Action Center. The template also complies with the UiPath Automation Solution Architect best practices and standards, such as naming conventions, modularity, reusability, and maintainability.  References :

UiPath Studio - Robotic Enterprise Framework Template

UiPath Studio - Working with Queues in the ReFramework

UiPath Studio - Long Running Workflow Template with UiPath Tasks

[UiPath Automation Solution Architect - Course Overview]

[UiPath Automation Solution Architect - Best Practices and Standards]

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

Machine Learning (ML) is a branch of artificial intelligence (AI) that enables computers to learn from data and perform tasks that are difficult or impossible to program explicitly. ML models can be trained to recognize patterns, make predictions, and generate outputs based on the input data. ML models can be integrated into automation solutions using UiPath AI Center, a cloud-based platform that allows users to deploy, manage, and consume ML models in their automations.

Among the four business scenarios given, the one that is best automated using ML is to classify emails in appropriate categories based on their subject and body. This is because email classification is a natural language processing (NLP) task that requires understanding the meaning and context of the text, which is not easy to achieve with rule-based or deterministic approaches. ML models can be trained to learn from a large corpus of labeled emails and assign categories to new emails based on their similarity and relevance. This can help automate the email management process and improve the efficiency and accuracy of email handling.

The other three scenarios can be automated using Robotic Process Automation (RPA), which is a technology that mimics human actions to interact with applications and systems. RPA can be used to create support tickets inside a helpdesk platform, calculate hotels inside a spreadsheet, and migrate data from one database to another, by following predefined steps and rules. These scenarios do not require ML models, as they do not involve complex or ambiguous data or tasks.

References :

RPA & AI Integration with AI Center | UiPath

Become an Automation Solution Architect | UiPath Academy

RPA Solution Architect - UiPath Academy

When deploying UiPath products using Standalone or Automation Suite deployment models, the user is responsible for maintaining and scaling the infrastructures and upgrading to newer versions. This means that the user has to provide the hardware and software resources required for the installation and operation of the UiPath products, as well as monitor and optimize their performance and availability. The user also has to ensure that the UiPath products are updated to the latest versions and patches, and that the compatibility and dependencies between them are maintained. (https://docs.uipath.com/installation-and-upgrade/docs/standalone-deployment)

References :

UiPath Installation and Upgrade - Standalone Deployment

UiPath Installation and Upgrade - Automation Suite Deployment

UiPath Academy - RPA Solution Architecture Fundamentals

UiPath Certified Professional Automation Solution Architect

High-volume, repetitive tasks that are predictable and do not require creativity or critical thinking are well-suited for automation with RPA. These tasks often involve routine data entry, data extraction, and rule-based decision-making, which can be efficiently handled by robots. Automating such tasks can significantly improve efficiency, accuracy, and speed, while freeing up human workers to focus on more complex and value-added activities that require human judgment, creativity, and emotional intelligence.

References:

UiPath RPA Guide: Identifying Processes for Automation

UiPath Best Practices: Process Selection

According to the UiPath documentation 1 , 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

In UiPath Orchestrator, using the queue name as an argument for the process is the most efficient way to handle varying data sources for different schedule times. When scheduling the process, you can specify different queue names as input arguments for each trigger (9AM, 1PM, 6PM). This approach allows for a single, flexible process that adapts to different data sources at different times without the need for multiple deployments or manual updates to assets or configuration files.

References:

UiPath Orchestrator Guide: Managing Triggers

UiPath Orchestrator Guide: About Arguments

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

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.

This answer is correct because long-running workflows are processes that require logical fragmentation or human intervention (validations, approvals, exception handling) such as invoice processing and performance reviews. They are handled with a set of instruments in the UiPath suite: a dedicated project template in Studio called Orchestration Process, actions and resource allocation capabilities in Orchestrator. Long-running workflows use a pair of activities to introduce a condition that suspends the main job until the condition is met, and then resumes the job with the obtained data.  The condition can be a job, a queue item, a form action, or an external action 1 2

References :

Orchestrator - Working With Long-running Workflows

Designing long-running workflows - UiPath Documentation Portal

The Unique Key property in the Orchestrator Queue configuration allows you to specify whether the queue items should have unique references or not. A reference is a string value that can be used to identify a queue item. If the Unique Key property is set to Yes, then Orchestrator checks if the reference of the new queue item already exists in the queue, and rejects the item if it does. This way, you can prevent adding duplicate items to the queue and ensure that each invoice is processed only once. If the Unique Key property is set to No, then Orchestrator does not perform this check and allows adding items with the same reference to the queue. This option can be useful if you want to process the same invoice multiple times for different purposes or scenarios.  References :  Managing Queues in Orchestrator - UiPath Documentation Portal ,  Managing Queues in Orchestrator - UiPath Documentation Portal ,  Orchestrator Queue - “unique reference” is enforced - Help - UiPath Community Forum

The main purpose of Workflow Analyzer in UiPath Studio is to evaluate the usage of best practices within the development process, identify design errors, and pinpoint areas for improvement. Workflow Analyzer is a static code analysis tool that scans automation projects for potential issues, inefficiencies, and deviations from best practices. It provides developers with actionable feedback and recommendations, helping to improve the quality, maintainability, and performance of the workflows. This tool is instru mental in ensuring that automations are built to the highest standards, aligning with organizational guidelines and industry best practices.

References:

UiPath Studio Guide: Workflow Analyzer

UiPath Best Practices: Workflow Design

The Solution Design Document (SDD) is a document that describes the technical design and implementation details of an automation solution. It is based on the Process Design Document (PDD) that defines the business requirements and process flow. The SDD should follow a standard template that ensures consistency and quality across different automation projects. However, some customers may have their own template or preferences for the SDD, especially if they have a Center of Excellence (CoE) that oversees the automation governance and best practices. In such cases, the UiPath Automation Solution Architect should use the customer’s template or adapt the default UiPath SDD template to meet the customer’s expectations and standards.

References :

Become an Automation Solution Architect | UiPath Academy

Roles of a Solution Architect in Automation, RPA Setting - UiPath

Template of PDD and SDD - UiPath Community Forum

 Artificial intelligence (AI) is a broad term that covers various technologies that enable machines to perform tasks that traditionally require human intelligence, such as reasoning, learning, problem-solving, and using language.  AI can be classified into different types, such as weak AI, strong AI, and artificial general intelligence (AGI), depending on the level of intelligence and the scope of tasks that the machines can perform 2 .  Some of the common applications of AI include natural language processing, computer vision, speech recognition, machine learning, and deep learning 3 .

References :

1 : Artificial intelligence (AI) | Definition, Examples, Types, Applications, Companies, & Facts | Britannica

2 : What Is Artificial Intelligence? Definition, Uses, and Types | Coursera

3 : What is Artificial Intelligence (AI) ? | IBM

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, a hybrid mode deployment allows you to use the existing on-premise Orchestrator installation and connect it to the cloud-based AI Center and Document Understanding services 1 .  This way, you can leverage the benefits of cloud computing, such as scalability, flexibility, and lower costs, without compromising the security and stability of your Orchestrator 1 .  Moreover, a hybrid mode deployment can be faster and easier than a full cloud or on-premise mode, as it does not require a lengthy approval process or hardware provisioning 2 3 .

References :

AI Center - Hybrid Deployment

Solutions Management - Deploying a solution

Enable Phase | Deployment Options | Solution Architect | UiPath …

Solution architects are responsible for designing automation solutions and choosing the technology stack for the development and operationalization of the solution. They are also responsible for overseeing the development and implementation stages. One of their key responsibilities is to coach developers on the best practices in an RPA project, such as following the UiPath Automation Implementation Methodology, using the UiPath templates and solution accelerators, applying the principles of modularity, reusability, and maintainability, and ensuring the quality and performance of the automation code. Solution architects should conduct frequent and thorough code reviews to enforce a high standard of the developed workflows and to facilitate knowledge transfer in the project team.

References :

Become an Automation Solution Architect | UiPath Academy

Roles of a Solution Architect in Automation, RPA Setting - UiPath

Studio - Automation Lifecycle - UiPath Documentation Portal

The key difference between Attended and Unattended Automations in UiPath is the level of human involvement and interaction required for the automation to run. Attended Automations are designed to assist human users with their tasks, such as filling forms, validating data, or providing guidance. They are triggered by the user and run on the user’s machine, usually in the foreground. They are best suited for smaller, fragmented tasks that need human input or decision making. Unattended Automations are designed to perform complex and repetitive tasks without human intervention, such as processing invoices, generating reports, or updating databases. They are triggered by a schedule, an event, or an API call and run on dedicated machines, usually in the background. They are best suited for large-scale, batch-mode tasks that need high reliability and scalability.

References :

Overview - Attended Vs. Unattended Automation

Attended Or Unattended RPA? Advantages for Both Solutions

Robot - Attended Vs Unattended Robots

This architectural approach is best for this scenario because it leverages the UiPath Platform capabilities to automate the end-to-end process of invoice processing. It uses the UiPath Email activities to connect to various mailboxes and retrieve the invoices as attachments. It then uses the UiPath Document Understanding framework to classify, extract, and validate the relevant information from the invoices, such as invoice number, date, amount, vendor, etc. It also uses the UiPath SAP activities to connect to the SAP system and input the extracted data into the appropriate fields and transactions.  This approach is scalable, reliable, and efficient, as it does not require any manual intervention or third-party service.  References : UiPath Automation Solution Architect Learning Plan, Module 4: High-Level Solution Design 1 ; UiPath Automation Suite - Invoice Processing 2 ; UiPath Academy - Roles of a Solution Architect in Automation, RPA Setting 3 .

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 Repository 1 2

References :

Studio - About Object Repository - UiPath Documentation Portal

Object Repository | UiPath UI Library | UiPath Academy

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

In UiPath ' s documentation regarding the Dispatcher and Performer model, it is emphasized that the Dispatcher is responsible for adding items to the queue, while the Performer processes these items. An accurate split between Dispatcher and Performer tasks is crucial for efficient process design. The given estimation table should clearly distinguish tasks that add items to the queue (Dispatcher) from those that process items from the queue (Performer). Mixing or inaccurately assigning these tasks can lead to inefficiencies and confusion in process execution. (Source: https://docs.uipath.com/orchestrator/docs/about-queues-and-transactions )

 According to the image, ‘E3L’ is a component that connects the Storage Bucket and the SME Validation Action. This implies that ‘E3L’ is responsible for retrieving the documents from the storage and sending them to the SMEs for validation. This is an example of a Human in the Loop (HITL) scenario, where human intervention is required to complete the automation process.  Therefore, ‘E3L’ can be considered as a Human in the Loop Performer, which is a role that enables human interaction with the automation solution 1 .

References :  Human in the Loop

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

The primary responsibilities of an RPA Solution Architect include designing and planning RPA solutions that automate business processes to improve efficiency and productivity. This role involves understanding the business requirements, identifying automation opportunities, designing the solution architecture, and ensuring that the planned solution aligns with both technical and business goals. Solution Architects play a crucial role in bridging the gap between business needs and technical solutions, ensuring that the RPA deployments are successful and deliver the intended value to the organization.

References:

UiPath Role Guides: Solution Architect

UiPath Best Practices: Role of a Solution Architect

 Package Explorer is a feature that enables you to view the contents of any package version uploaded to Orchestrator. You can access it from the Packages page, by clicking the  Explore  button next to the package name. Package Explorer displays a graphical representation of the entry .xml file of the package, as well as the variables, arguments, and imports that are part of it. You can also view the properties of each activity, such as selectors, text, or output variables. Package Explorer can help you troubleshoot errors, compare different versions of a package, or inspect the logic of a package without opening it in Studio.

References :

Package Explorer

New package Explorer options with 2019.10 Beta

OCR is a technology that converts scanned images of text into machine-readable text. It can be used to extract text from printed or handwritten documents, such as invoices, receipts, forms, etc.  OCR is useful for simple text extraction tasks, such as converting printed books into digital formats, or extracting data from structured documents with fixed layouts 2 .

Document Understanding is a framework that leverages OCR and other technologies, such as machine learning, natural language processing, and computer vision, to analyze and understand the meaning and structure of documents. It can be used to extract data from semi-structured or unstructured documents, such as contracts, resumes, emails, etc.  Document Understanding is suitable for more complex tasks that require a deeper understanding of document content and context, such as sentiment analysis, natural language understanding, document classification, etc 1 .

References :

1 : Document Understanding - UiPath Documentation Portal

2 : OCR - UiPath Activities

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.

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

UiPath Apps is a low-code application development platform that enables you to build and share enterprise-grade custom applications that deliver engaging user experiences.  Using UiPath Apps, you can quickly build custom business applications that connect to data in any underlying cloud or on-premises system using the power of automation 1 . Apps built with UiPath App Studio provide rich controls for data access and update as well as conditional logic for complex business needs.  The underlying UiPath RPA platform provides advanced workflow and business logic capabilities to automate your entire end to end business process 2 .  Apps can be designed to run in multiple form factors such as a full-page console, a sidebar, or any other size for either desktop or mobile devices 1 .

References :  1 :  Apps - Introduction - UiPath Documentation Portal   2 :  Introducing UiPath Apps: A Robot-Powered Low-Code Platform

UiPath Apps is a low-code application development platform that enables you to build and share enterprise-grade custom applications that deliver engaging user experiences. Using UiPath Apps, you can quickly build custom business applications that connect to data in any underlying cloud or on-premises system using the power of automation. Apps built with UiPath App Studio provide rich controls for data access and update as well as conditional logic for complex business needs. The underlying UiPath RPA platform provides advanced workflow and business logic capabilities to automate your entire end to end business process.

References :

Apps - Introduction - UiPath Documentation Portal

Introducing UiPath Apps: A Robot-Powered Low-Code Platform