Splitting the process into three distinct sub-processes - Dispatcher, Performer, and Reporter - aligns with best practices for RPA design, promoting modularity and scalability. The Dispatcher's role would be to initialize the process, such as identifying and queuing work items. The Performer would then take over to handle the core automation tasks (steps 2 to 4), focusing on processing the queued items. Finally, the Reporter would compile and present the results or outcomes of the automation (steps 5 to 7). This structure not only clarifies the process flow but also facilitates easier maintenance and updates, as each sub-process can be modified independently without affecting the others.

UiPath REFramework Guide: Dispatcher-Performer Model

UiPath Best Practices: Framework for Process Design

According to the UiPath Automation Solution Architect Learning Plan, the Solution Architect is responsible for creating the Automation Runbook document, which is a detailed guide for the deployment and maintenance of the automation solution. The Automation Runbook document contains information such as the automation objectives, scope, dependencies, risks, roles and responsibilities, deployment steps, testing scenarios, troubleshooting tips, and support contacts. The Automation Runbook document is created after the Solution Design Document (SDD) and before the deployment of the automation solution.

UiPath Automation Solution Architect Learning Plan

Automation Suite - Alert Runbooks

Activities - Start Runbook

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.Reference:Data Service - Entities - UiPath,Data Service - Queries - UiPath,Data Service - Relationships - UiPath

UiPath Automation Cloud is a cloud-based enterprise automation solution that lets you start and scale your automation from the cloud with SaaS robots and self-hosted robots. It offers security, compliance, governance, and insights for your RPA initiatives. It does not require manual installation and maintenance, as it is delivered as a service. It does not have single or multi-node deployment options, as it is hosted on UiPath's infrastructure. It does not provide major updates twice yearly, as it is updated continuously with new features and improvements.

Complete cloud-based enterprise automation solution | UiPath

Automation Cloud - UiPath Documentation Portal

Automation Cloud - About Automation Cloud - UiPath Documentation Portal

A Solution Design Document (SDD) is a document that describes the technical design and implementation details of an RPA solution. It includes information such as process flow diagrams, exception handling, logging, security, testing, and deployment. An SDD contributes to the ongoing success of an RPA solution by providing a clear and comprehensive documentation of the solution, which can help with maintenance, enhancements, knowledge transfer, and future updates and bug fixes. An SDD also ensures that the solution follows the best practices and standards of RPA development, and that it meets the business requirements and expectations.

SDD Example - Help - UiPath Community Forum

SDD Document Template - Something Else - UiPath Community Forum

Solution Design Documents - UiPath Community Forum

SDD Assistant - RPA Component | UiPath Marketplace | Overview