<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jobin Thekkekara Joy on Medium]]></title>
        <description><![CDATA[Stories by Jobin Thekkekara Joy on Medium]]></description>
        <link>https://medium.com/@jobinthekkekarajoy?source=rss-1c1cc5859047------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OyGIYoXWnztX0jtr5IqG7w.jpeg</url>
            <title>Stories by Jobin Thekkekara Joy on Medium</title>
            <link>https://medium.com/@jobinthekkekarajoy?source=rss-1c1cc5859047------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:39:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jobinthekkekarajoy/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[UiPath Orchestrator — Multi Node Architecture]]></title>
            <link>https://jobinthekkekarajoy.medium.com/uipath-orchestrator-multi-node-architecture-6339d63ab16f?source=rss-1c1cc5859047------2</link>
            <guid isPermaLink="false">https://medium.com/p/6339d63ab16f</guid>
            <category><![CDATA[orchestrator]]></category>
            <category><![CDATA[multi-node]]></category>
            <category><![CDATA[platform-architecture]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[uipath]]></category>
            <dc:creator><![CDATA[Jobin Thekkekara Joy]]></dc:creator>
            <pubDate>Thu, 21 Dec 2023 05:42:06 GMT</pubDate>
            <atom:updated>2023-12-21T05:43:03.249Z</atom:updated>
            <content:encoded><![CDATA[<h3>UiPath Orchestrator — Multi Node Architecture</h3><h4>Introduction to UiPath Orchestrator:</h4><blockquote><em>UiPath Orchestrator is a web application developed by UiPath to streamline the orchestration of robots in the execution of repetitive or rule based business processes. This powerful application plays a vital role in managing resources for automation projects and their utilization by robots. It provides hierarchical structuring and fine-grained role assignments for efficient access control and making it an essential integration point for third party solutions and applications.</em></blockquote><blockquote><em>“One of Orchestrator’s primary strengths lies in it’s ability to effectively oversee your entire fleet of robots”</em></blockquote><p>UiPath offers a range of deployment possibilities for its platform, including single-node, multi-node, high availability, active/passive, and active/active configurations. In a multi-node deployment, UiPath components are spread across multiple machines, enhancing performance, scalability, and resilience for optimized operational efficiency.</p><h3>Basic Understanding on Multi Node Architecture:</h3><p>UiPath Multi-Node Orchestrator is a way of setting up UiPath Orchestrator by spreading its parts across multiple machines. The Orchestrator is like a control center for UiPath robots, handling tasks like automating processes, scheduling, monitoring, and managing robot resources.</p><p>In this setup, different parts like the web application server, database, and message queue are put on separate machines. This setup has some benefits:</p><ul><li><strong>Better Performance:</strong> Sharing the workload across machines improves how well everything works and makes the system more responsive.</li><li><strong>Easy Scalability: </strong>It’s simple to add more machines if you need to handle more automation tasks.</li><li><strong>Always Available:</strong> If one machine has a problem, another can take over, making sure there’s minimal downtime and the system keeps running.</li><li><strong>Stronger Against Issues:</strong> Spreading out the parts makes the system more robust, so if one part has a problem, it’s less likely to affect everything else.</li></ul><p>In a nutshell, UiPath Multi-Node Orchestrator is built to give organizations a strong and flexible system for managing their UiPath robots, especially when they have different automation needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lE9UI9EfTkFDmm4OCQ95MQ.png" /><figcaption>Fig 1.1 UiPath Multi Node Architecture</figcaption></figure><h3>Key Components of Multi Node Architecture:</h3><p>UiPath Multi-Node Orchestrator involves distributing the key components of UiPath Orchestrator across multiple machines or nodes to enhance performance, scalability, and resilience. The key components include:</p><ol><li><strong>UiPath Orchestrator Scale Set:</strong> It is advisable to install the individual Orchestrator applications on dedicated Windows servers. Ensure that all Orchestrator nodes maintain consistent IIS configurations, access rights, and security policies. Additionally, it is recommended to configure a service Windows user account specifically for the UiPath Orchestrator scale set. This account can then be utilized for establishing the database connection.</li><li><strong>Scalable SQL Database:</strong> The configuration of the database server should align with the number of Orchestrator nodes in production. Many cloud databases offer scalability, so it is advisable to collaborate with the database administrator to establish best practices and ensure proper access privileges are set up.</li><li><strong>UiPath Robots:</strong> Operate within an environment that can be configured on either virtual or physical machines. These machines are accessed remotely using Robot accounts. The key distinction lies in the need for this environment to be configured for rapid scalability to accommodate new Robots efficiently. A popular choice for achieving this scalability in the current environment is through the use of Kubernetes containers.</li><li><strong>Elasticsearch (ES) Cluster Environment:</strong> It is advisable to establish a dedicated Windows server to host both the ES and Kibana applications for building this cluster. The primary objective is to provide a scalable solution as the volume of logs generated by the Robots’ executed jobs increases. Given the critical role of logs in maintaining the operational health of UiPath, it is essential to prioritize the setup and maintenance of this cluster for effective support and monitoring.</li><li><strong>High Availability Add-on (HAA) Cluster Environment:</strong> The HA add-on ensures redundancy and stability for your multi-node Orchestrator deployment by providing resistance to failures. In an HAA configuration, if one Orchestrator or HAA node fails, the other nodes are activated, allowing processing to seamlessly “failover” to the remaining nodes in the cluster. This setup also allows for horizontal scalability, enabling the addition of nodes to accommodate an increase in Robot counts. UiPath HAA is essentially the Redis Original Equipment Manufacturer (OEM) version for UiPath. Redis is employed for in-memory data structure storage, specifically for caching, which enhances the application’s performance. It is important to note that UiPath’s support contract exclusively covers the multi-node setup with UiPath HAA. Consequently, it is not merely a nice-to-have component; rather, it is a critical.</li><li><strong>Load Balancer (LB) for Orchestrator Servers:</strong> Load balancers play a crucial role in redirecting traffic to different Orchestrator nodes that result from various client requests. It is advisable to configure a load balancer URL for Orchestrator login to ensure continued access to the application even if a node experiences downtime.</li><li><strong>Load Balancer (LB) for Elasticsearch (ES) Servers: </strong>The same principle is applicable to redirect connections from Orchestrator to ES servers. In cases where there are multiple ES servers, the implementation of a load balancer becomes essential. Additionally, there may be scenarios where numerous ES shards are distributed across different servers, and in such cases, utilizing a load balancer is advisable.</li><li><strong>UiPath Identity Server:</strong> This service offers centralized authentication across all UiPath products and is an integral part of the on-premises Orchestrator installer. It is advised that the enterprise Identity and Access Management (IAM) team take charge of configuring the Identity Server component in alignment with existing enterprise standards.</li><li><strong>Azure Redis Cache: </strong>Multi-node orchestrator deployment use the RESP (Redis Serialization Protocol) for communication, and thus can be configured using any solution implementing this protocol such as Azure Redis Cache. For multi node deployment,it is recommended to use two separate Redis instances.</li></ol><ul><li>Azure Redis Cache Premium with a 6GB cache — the primary node used for session state and user-entity associations</li><li>Azure Redis Cache Basic — used to scale the SignalR service.</li></ul><h3>Installation/configuration of main components:</h3><h3><strong><em>1.Installation on HAA:</em></strong></h3><p>The HAA add-on scripts from UiPath repository is need to be downlaoded and installed on the linux machine.</p><p><strong>Installing the primary node:</strong></p><ol><li>SSH the primary node with root permissions.</li><li>Create the directory where you want to download and extract HAA</li><li>Download the get-haa.sh installation script: Example:wget <a href="https://download.uipath.com/haa/get-haa.sh">https://download.uipath.com/haa/get-haa.sh</a></li><li>Make the get-haa.sh script executable: chmod a+x get-haa.sh</li><li>Install the primary node and ensure that you provide an email address and password for the administrator account. You may use a temporary email address. Additionally, please specify the operating system currently running on the node. Example:sudo ./get-haa.sh -u &lt;email&gt; -p &lt;password&gt; -o &lt;OS&gt; --accept-license-agreement</li></ol><p><strong>Installing the secondary node:</strong></p><ol><li>SSH the secondary node with root permissions.</li><li>Create the directory where you want to download and extract HAA</li><li>Download the get-haa.sh installation script: Example:wget <a href="https://download.uipath.com/haa/get-haa.sh">https://download.uipath.com/haa/get-haa.sh</a></li><li>Make the get-haa.sh script executable: chmod a+x get-haa.sh</li><li>Install the secondary node. Example: sudo ./get-haa.sh -u &lt;email&gt; -p &lt;password&gt; -o &lt;OS&gt; -j &lt;IP_address_of_the_master_node&gt; --accept-license-agreement</li></ol><p><strong>Configuring UiPath.Orchestrator.dll.config:</strong></p><p>To enable High Availability and Add-Node functionality in Orchestrator, configure it to use HAA (High Availability Add-On). Incorporate all HAA nodes into the UiPath.Orchestrator.dll.config configuration file of Orchestrator, utilizing the LoadBalancer.UseRedis and LoadBalancer.Redis.ConnectionString parameters. For instance:</p><pre>&lt;add key=&quot;LoadBalancer.UseRedis&quot; value=&quot;true&quot; /&gt;<br>&lt;add key=&quot;LoadBalancer.Redis.ConnectionString&quot; value=&quot;10.10.20.184:10000,10.10.24.148:10000,10.10.22.114:10000,password=SuperSecret_Password&quot; /&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IDJmTBoX-blUwRhZ" /><figcaption>Fig 1.2 HAA for UiPath Orchestrator</figcaption></figure><p>For more details, refer <a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/haa-installation">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/haa-installation</a></p><p><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/high-availability">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/high-availability</a></p><h3><strong>2. Configuring the Azure Load Balance:</strong></h3><p>Configuring Azure Load Balancer for UiPath multi-node deployment involves several key steps to ensure high availability and load distribution across multiple nodes. Below is a detailed description of the main steps:</p><p><strong>Step 1:</strong>Adding a frontend IP</p><p>In Azure Load Balancer, adding a frontend IP address involves configuring the public or private IP address that clients will use to access the services hosted behind the load balancer. The frontend IP is associated with the load balancer, and it serves as the entry point for incoming traffic.</p><p><strong>Step 2:</strong> Creating the backend pool and add nodes</p><p>Creating the backend pool and adding nodes in Azure Load Balancer involves configuring the set of virtual machines or instances that will receive and process incoming traffic. The backend pool is a collection of these instances, and the load balancer distributes traffic among them based on defined rules.</p><p><strong>Step 3:</strong> Adding health probes</p><p>Adding health probes in Azure Load Balancer is a crucial step in ensuring the availability and health of backend instances (nodes) within the load balancer’s backend pool. Health probes are used to periodically check the status of each backend instance, allowing the load balancer to route traffic only to healthy instances.</p><p><strong>Step 4:</strong> Adding a load balancing rule</p><p>Adding a load balancing rule in Azure Load Balancer involves defining how incoming network traffic should be distributed among the backend pool instances. Load balancing rules help determine which ports on the load balancer should listen for incoming traffic and how that traffic should be distributed among the backend instances.</p><p><strong>Step 5:</strong> Creating a load balancer domain name</p><p>In Azure Load Balancer, there isn’t a specific concept of creating a load balancer domain name directly associated with the load balancer itself. However, when you configure a load balancer to distribute traffic to backend instances, you typically use a domain name associated with the public IP address assigned to the load balancer.</p><p>For more details, refer <a href="https://docs.uipath.com/automation-suite/automation-suite/2023.4/installation-guide/azure-infrastructure-configuring-load-balancer">https://docs.uipath.com/automation-suite/automation-suite/2023.4/installation-guide/azure-infrastructure-configuring-load-balancer</a></p><h3><strong>3. Certificate consideration — during installation</strong></h3><p>There are two essential certificates that Orchestrator necessitates for seamless operations:</p><p><strong>Orchestrator SSL Certificate: </strong>This certificate is vital for establishing secure, encrypted communication between Robots and Orchestrator. While it is highly recommended to use an SSL certificate approved by a Certificate Authority for enhanced security, a self-signed certificate is also a viable option.</p><p><strong>Identity Server Token-Signing Certificate:</strong> This certificate plays a crucial role in user authentication, as it holds the private key. To modify these certificates, the configuration of the Identity Server must be adjusted accordingly.</p><p>Refer the below documentation for more about certficates,</p><p><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/using-a-certificate-for-the-https-protocol">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/using-a-certificate-for-the-https-protocol</a>Conclusion:</p><h3><strong>Why we need to consider UiPath multinode orchestrator instance over single node instance</strong></h3><blockquote>Choosing a UiPath Multi-Node Orchestrator instance over a Single-Node setup provides numerous benefits tailored to scalability, performance, and fault tolerance. Below are key reasons to consider a Multi-Node Orchestrator configuration:</blockquote><p><strong>Scalability:</strong></p><p><strong>Enhanced Workload Handling:</strong> Multi-Node Orchestrator distributes workloads across multiple nodes, significantly boosting the system’s capability to manage a larger volume of processes and robots simultaneously.</p><p><strong>Vertical and Horizontal Scaling:</strong> The option to scale vertically by augmenting resources to a single node or horizontally by adding more nodes offers flexibility aligned with the dynamic growth of automation requirements.</p><p><strong>Improved Performance:</strong></p><p><strong>Load Balancing:</strong> Multi-Node Orchestrator instances implement load balancing, ensuring equitable distribution of tasks among nodes. This minimizes bottlenecks and elevates overall system performance.</p><p><strong>Optimal Resource Utilization:</strong> Distributing processes across multiple nodes optimizes resource utilization, mitigating the risk of resource contention and maximizing efficiency.</p><p><strong>High Availability:</strong></p><p><strong>Redundancy: </strong>In a Multi-Node setup, if one node encounters a failure, the system can automatically redirect the workload to other available nodes. This redundancy enhances system reliability, ensuring uninterrupted operation even in the event of a node failure.</p><p><strong>Fault Tolerance:</strong></p><p><strong>Resilience to Node Failures: </strong>With multiple nodes, the Orchestrator environment becomes more resilient to individual node failures. If one node becomes unavailable, other nodes can seamlessly continue processing tasks, minimizing the impact on overall automation operations.</p><p><strong>Separation of Roles:</strong></p><p><strong>Dedicated Nodes for Specific Functions:</strong> A Multi-Node Orchestrator setup allows the dedication of specific nodes to handle distinct functions such as scheduling, processing, and storage. This segregation of roles enhances the efficiency and maintainability of the Orchestrator environment.</p><p><strong>Geographical Distribution:</strong></p><p><strong>Support for Multiple Locations</strong>: Multi-Node Orchestrator instances can be deployed across different geographical locations, facilitating a distributed approach. This proves beneficial for organizations with global operations or those seeking to optimize automation processing based on regional requirements.</p><h3>More references:</h3><ul><li><a href="https://community.uipath.com/events/details/uipath-uipath-platform-infrastructure-presents-installation-walkthrough-live-multi-node-orchestrator/">Installation walkthrough - Live (Multi node Orchestrator) | UiPath</a></li><li><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/installation-considerations">Installation Considerations</a></li></ul><h3><strong>Conclusion:</strong></h3><blockquote><em>In conclusion, </em>a UiPath Multi-Node Orchestrator instance brings advantages such as increased scalability, improved performance, high availability, fault tolerance, and adaptability to evolving automation needs. This configuration is particularly beneficial for organizations experiencing growth in automation demands, aiming for a resilient, efficient, and robust Orchestrator environment.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6339d63ab16f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UiPath Orchestrator — Single Node Architecture]]></title>
            <link>https://jobinthekkekarajoy.medium.com/uipath-orchestrator-single-node-architecture-44ddfc389058?source=rss-1c1cc5859047------2</link>
            <guid isPermaLink="false">https://medium.com/p/44ddfc389058</guid>
            <category><![CDATA[orchestrator]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[single-node]]></category>
            <category><![CDATA[rpa-platform]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Jobin Thekkekara Joy]]></dc:creator>
            <pubDate>Thu, 02 Nov 2023 02:42:58 GMT</pubDate>
            <atom:updated>2023-11-02T02:42:58.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>UiPath Orchestrator — Single Node Architecture</h3><h3>Introduction to UiPath Orchestrator:</h3><blockquote>UiPath Orchestrator is a web application developed by UiPath to streamline the orchestration of robots in the execution of repetitive or rule based business processes. This powerful application plays a vital role in managing resources for automation projects and their utilization by robots. It provides hierarchical structuring and fine-grained role assignments for efficient access control and making it an essential integration point for third party solutions and applications.</blockquote><blockquote>“One of Orchestrator’s primary strengths lies in it’s ability to effectively oversee your entire fleet of robots”</blockquote><p>For attended automation, Orchestrator ensures centralized management and the accurate delivery of package versions to robots for execution. In unattended automation scenarios, orchestrator allows for immediate or pre-planned execution, thanks to its support for triggers. Orchestrator efficiently allocates work to unattended robots and, when given flexibility in workload distribution, maximizes efficiency and optimizes robot usge to its fullest potential.</p><h3>Orchestrator Architecture:</h3><p>UiPath Orchestrator’s architecture includes three essential layers, each serving a specific purpose in managing and orchestrating robotic process automation (RPA) workflows. These layers are:</p><p><strong>1.Presentation Layer:</strong></p><p>The Presentation Layer is the user interface (UI) component of UiPath Orchestrator. It provides a web-based interface accessible via web browsers, enabling administrators, operators, and users to interact with the Orchestrator. Users can configure robots, create and manage automation processes, schedule tasks, monitor job statuses, and perform various administrative functions through the user-friendly UI. This layer focuses on delivering a visually intuitive and user-friendly experience for interacting with Orchestrator.</p><p><strong>2.Service Layer:</strong></p><p>The Service Layer, also known as the Application Layer, is where the core functionalities and business logic of UiPath Orchestrator are located. It hosts the Orchestrator web application server, which is responsible for handling user requests, executing business logic, and coordinating communication between different Orchestrator components. This layer is pivotal in managing robot schedules, orchestrating automation task execution, and controlling user access to the Orchestrator system. The Service Layer acts as the intermediary between the user interface and the underlying components, ensuring the proper execution of automation workflows.</p><p><strong>3. Persistence Layer:</strong></p><p>The Persistence Layer is responsible for storing and managing data related to the UiPath Orchestrator. It typically uses a relational database SQL Server to store configuration data, settings, and critical information. Key data stored in this layer includes robot configurations, process definitions, job schedules, user access controls, and more. The Persistence Layer is crucial for data storage, retrieval, and management, ensuring that the Orchestrator has access to the information it needs to function effectively.</p><p>These three layers work in harmony to provide a comprehensive and efficient RPA orchestration platform. The Presentation Layer focuses on user interaction and accessibility, the Service Layer handles core functionality and business logic, and the Persistence Layer manages data storage and retrieval. Together, they enable the management, scheduling, execution, monitoring, and reporting of automation processes in UiPath Orchestrator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92TQW8LImKUnS8yfOF-uvA.png" /><figcaption>Fig 1.1 UiPath Orchestrator Architecture</figcaption></figure><h3>Single Node Architecture:</h3><p>The UiPath Orchestrator Single Node Architecture is a configuration where all the components of UiPath Orchestrator are installed and run on a single server or node. This setup is suitable for small-scale or testing environments. Here’s an overview of the architecture and components in a single-node deployment:</p><h3><strong>Components:</strong></h3><p><strong>UiPath Orchestrator Application:</strong> This is the core web application that provides the user interface for managing robots, automation processes, schedules, and other Orchestrator-related tasks.</p><p><strong>Database:</strong> UiPath Orchestrator relies on a database to store configuration data, settings, and information. Commonly, SQL Server is used as the database system.</p><p><strong>Internet Information Services (IIS):</strong> IIS is responsible for hosting the Orchestrator web application and providing the web server capabilities required for user access.</p><p><strong>Robot Machines:</strong> These are the machines where UiPath robots are installed. Robots execute automation tasks and report results back to the Orchestrator.</p><h3><strong>Architecture Overview for Single Node Orchestrator:</strong></h3><p>In a single-node architecture, the Orchestrator Application, Database and IIS are installed on a single server or node. The UiPath Orchestrator web application runs in IIS, allowing administrators and users to interact with Orchestrator through a web browser. The database stores crucial data such as robot configurations, process definitions, schedules, job information, and user access controls. Robot machines execute automation tasks as directed by Orchestrator and report back with execution results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDetDOiLzxyGhnrzywQlqQ.png" /><figcaption>Fig 1.2 Typical Single Node Deployment Architecture</figcaption></figure><p>A single-node architecture is suitable for small-scale implementations, proof-of-concept setups, or testing environments. It may lack the scalability and redundancy features of a multi-node or high-availability setup, making it less suitable for production environments with high automation demands. Security considerations, including firewall rules and access control, are essential to protect the single-node deployment. This architecture simplifies setup and maintenance but may not be sufficient for large-scale enterprise RPA deployments. For production environments and larger deployments, UiPath provides guidance on multi-node and high-availability configurations to ensure robustness, scalability, and fault tolerance. It’s essential to assess your specific requirements and consult UiPath’s documentation and best practices to choose the most appropriate architecture for your needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ck4KhZOG3bAGOwQn7Akyqw.png" /><figcaption>Fig 1.3 Single Node Orchestrator Setup — Example</figcaption></figure><h3><strong>Hardware Requirement for Single Node Installation:</strong></h3><p>To set up a Single Node Orchestrator, you’ll need to ensure that your hardware meets certain requirements. Please note that these requirements might change over time, so it’s essential to refer to the most current documentation or contact UiPath directly for the latest information.</p><p>Here are the general hardware requirements for UiPath Single Node Orchestrator:</p><p><strong>Server Hardware:</strong></p><ul><li>CPU: Multi-core processor with at least 4 cores (recommended 8 cores or more).</li><li>RAM: A minimum of 16 GB RAM (recommended 32 GB or more).</li><li>Storage: A minimum of 50 GB of free disk space (more space for logs and backups).</li><li>Solid-State Drive (SSD): Using an SSD for storage is recommended for better performance.</li></ul><p>In a production environment, it is strongly advised to allocate separate, <strong><em>dedicated servers </em></strong>for each of the following roles:</p><ol><li><strong>Orchestrator Web Application:</strong> Assign a dedicated server exclusively for hosting the Orchestrator web application.</li><li><strong>SQL Server Database Engine:</strong> Set up a dedicated server solely for running the SQL Server Database Engine, which stores Orchestrator’s configuration and runtime data.</li><li><strong>Elasticsearch and Kibana:</strong> Allocate a separate server for Elasticsearch and Kibana, which are used for advanced search and visualization capabilities</li></ol><p>Please note that the above requirements are general guidelines and can vary depending on the specific version of UiPath Orchestrator and any additional features or modules you plan to use. It’s important to consult the official UiPath documentation or contact UiPath support for the most up-to-date and version-specific requirements. Additionally, consider the scalability and performance requirements of your automation projects when planning your hardware setup.</p><p>For more hardware requirement information. refer the below product documentation for version 2023.10</p><p><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-hardware-requirements">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-hardware-requirements</a></p><h3>Software Requirement for Single Node Installation:</h3><p>UiPath Single Node Orchestrator also requires specific software and software configurations. Please keep in mind that software requirements may change over time, so it’s essential to refer to the most current documentation or contact UiPath directly for the latest information.</p><p>Here are the general software requirements for UiPath Single Node Orchestrator:</p><p><strong>Server Operating System:</strong></p><ul><li>Windows server 2012 R2 or higher version</li><li>Compatible Versions: 2012 R2,2016,2019 and 2022</li></ul><p><strong>Database:</strong></p><ul><li>Microsoft SQL Server Standard or Enterprise Edition</li><li>Compatible Versions: 2014,2016,2017, 2019, 2022 Azure SQL Database, Amazon RDs for SQL Server and Google Cloud SQL for SQL Server</li></ul><p><strong>Logging and Visualization:</strong></p><ul><li>ElasticSearch — versions 7.0 to 8.x</li><li>Kibana — versions 7.0 to 8.x</li></ul><p><strong>Browsers:</strong></p><ul><li>UiPath Orchestrator only support evergreen browsers such as Chrome,Edge, Firefox, Chrome etc</li></ul><p><strong>Software Frameworks:</strong></p><ul><li>.Net Framework - version 4.7.2 or higher</li><li>ASP.Net Core Module — version 6.0.x</li></ul><p><strong>Web Servers:</strong></p><ul><li>IIS (Internet Information Services) — version 10 or higher</li><li>IIS Modules — URL Rewrite — version 2.1 or higher</li></ul><p><strong>Virtualization Platforms:</strong></p><p>Any platform capable of creating a Windows Virtual Machine is also suitable. Below are the software and compatible versions:</p><ul><li>Citrix XenDesktop: Version 7.6 or later.</li><li>Microsoft Hyper-V: Version 2016 or newer.</li><li>VMWare vSphere: Version 6 or higher.</li></ul><p><strong>Credentials Stores:</strong></p><p>The following components are not mandatory for Orchestrator usage but rather optional integrations.</p><ul><li>CyberArk — Central Provider 12.6</li><li>Azure Key Vault</li><li>HashiCorp Vault</li><li>Beyond Trust</li></ul><p>For more software requirement information. refer the below product documentations for version 2023.10</p><p><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-software-requirements">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-software-requirements</a></p><p><a href="https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-prerequisites-for-installation">https://docs.uipath.com/orchestrator/standalone/2023.10/installation-guide/orchestrator-prerequisites-for-installation</a></p><h3><strong>Conclusion:</strong></h3><blockquote>In conclusion, UiPath Orchestrator Single Node instance serves as a powerful and centralized hub for orchestrating, monitoring, and managing your robotic workforce. This solution streamlines automation operations, offering the flexibility of a single server deployment, making it an attractive choice for organizations of varying sizes. With the right hardware and software configurations, UiPath Orchestrator Single Node provides a stable and scalable platform to optimize and control your automation initiatives. This centralization of RPA processes and robots enhances efficiency, visibility, and compliance, ultimately contributing to the successful execution of automation projects and digital transformation efforts within your organization.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44ddfc389058" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UiPath Platform — Private and Public Cloud deployment options]]></title>
            <link>https://jobinthekkekarajoy.medium.com/uipath-platform-private-and-public-cloud-deployment-options-295e8202c587?source=rss-1c1cc5859047------2</link>
            <guid isPermaLink="false">https://medium.com/p/295e8202c587</guid>
            <category><![CDATA[private-cloud]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[public-cloud]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <dc:creator><![CDATA[Jobin Thekkekara Joy]]></dc:creator>
            <pubDate>Thu, 26 Oct 2023 02:32:23 GMT</pubDate>
            <atom:updated>2023-10-26T02:32:23.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>UiPath Platform — Private and Public Cloud deployment options</h3><h3>Introduction to UiPath Automation Platform:</h3><p>The UiPath Business Automation Platform is more than just a compilation of standalone products. It is a unified, integrated solution designed to seamlessly and securely integrate with your existing enterprise architecture, regardless of whether your strategy involves SaaS or self-hosting.</p><p>UiPath’s flagship product is the UiPath Automation Platform, a comprehensive solution encompassing a suite of low-code, visually integrated development tools called Studio for process creation. This platform is complemented by client-side agents known as Robots, which execute these processes. Furthermore, the deployment, monitoring, and remote management of these processes are facilitated through a centralized management tool called Orchestrator.</p><p>In addition to the UiPath Automation Platform, UiPath offers a range of other software products, including:</p><ol><li>UiPath AI Center (formerly AI Fabric): This tool efficiently orchestrates and incorporates AI capabilities into business processes.</li><li>UiPath Action Center: A communication tool that facilitates interactions between robots and humans when human intervention or guidance is needed within automated processes.</li><li>UiPath Apps: A low-code application development platform empowering users to create customized applications with ease.</li><li>UiPath Assistant: A launchpad for automations designed to aid computer workers, residing on the desktop and offering easy access to specific automations that simplify their tasks.</li><li>UiPath Automation Hub (formerly UiPath Connect Enterprise): An organizational tool that encourages employees to identify, propose, and track new processes suitable for automation.</li><li>UiPath Document Understanding: Software capable of extracting, interpreting, and processing data from various sources such as PDFs, images, handwriting, and more.</li><li>UiPath Insights: A modular data dashboard designed to provide analytics for processes automated with UiPath.</li><li>UiPath Process Mining (formerly ProcessGold): A tool that uncovers new automation opportunities by analyzing application logs.</li><li>UiPath StudioX: A platform that simplifies coding, enabling workers to create their own robots for streamlining their tasks.</li><li>UiPath Test Suite: A comprehensive solution that automates and centralizes testing processes, ensuring the quality of automations and applications before they are deployed.</li></ol><p>Most of UiPath’s software products are available as native software solutions or through the Software as a Service (SaaS) model, providing flexibility in how organizations choose to implement and leverage these tools.</p><h3>General Deployment Options:</h3><p>Here’s a more organized and concise explanation of the four deployment options:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HW5VemzIhBnmLqGF3iekjg.png" /><figcaption>Fig 1.1 Different Deployment Options</figcaption></figure><p><strong>On-Premises:</strong> In this deployment option, the customer or end user is responsible for managing everything, including networking, operating systems, and servers. Essentially, the entire infrastructure is managed by the customer themselves.</p><p><strong>IaaS (Infrastructure as a Service):</strong> IaaS, which stands for Infrastructure as a Service, is a cloud computing model offered by providers like Azure, AWS, or GCP. Here, the service provider manages responsibilities up to virtualization, while the user takes charge from the operating system layer onward, including applications.</p><p><strong>PaaS (Platform as a Service): </strong>PaaS, or Platform as a Service, provides users with a platform for hosting applications without the need to manage virtual machines or operating systems. Users can simply deploy and utilize the platform to run their applications. Example: AWS Elastic Beanstalk</p><p><strong>SaaS (Software as a Service):</strong> SaaS, also known as cloud application services, offers ready-to-use software applications hosted in the cloud. Users pay a periodic fee to access the complete application through a web browser, desktop client, or mobile app. The SaaS vendor manages all infrastructure aspects, including servers, storage, networking, middleware, application software, and data storage. Users only need to configure the application to meet their specific needs.</p><h3><strong>UiPath Platform Deployment Options:</strong></h3><p>UiPath offers different deployment options for its platform to suit different organizational needs. These deployment options include:</p><p><strong>1.Standalone or On-Premises Deployment: [PRIVATE CLOUD]</strong></p><p>In this option, the entire UiPath platform is installed and hosted on the organization’s own infrastructure, such as their data centers or <strong><em>private cloud</em></strong>. This provides maximum control and security, making it suitable for organizations with strict data governance and compliance requirements.</p><p>From a UiPath perspective, IaaS (Infrastructure as a Service) and on-premises deployments share similarities, primarily because both scenarios involve the utilization of virtual machines (VMs). Whether these VMs are located in your organization’s own data center or within a third-party service provider’s data center, UiPath operates seamlessly without distinction. UiPath’s first offering comprises standalone products, which encompass Orchestrator, Test Manager, Insights, and Action Center. These products are available independently, and you can acquire their MSI installers for deployment on your chosen virtual machine, or even a physical machine if needed.</p><p><strong>2.Automation Suite or Hybrid Deployment:</strong> [<strong>PRIVATE &amp; PUBLIC CLOUD]</strong></p><p>Hybrid deployment combines both <em>on-premises and cloud components</em>, allowing organizations to leverage the benefits of both approaches. This can be useful for organizations with a mix of legacy systems and a desire for cloud scalability.</p><p>The Automation Suite is a comprehensive software package by UiPath that serves as a bundled solution encompassing virtually all UiPath components, with the exception of Process Mining. This suite includes Orchestrator, Test Manager, Task Mining, AI Center, Document Understanding, and more, all conveniently packaged together. It can be hosted on your own servers or deployed on physical or virtual hardware provided by various service providers.</p><p><strong>3. Automation Cloud Deployment:</strong> [<strong>PUBLIC CLOUD]</strong></p><p>UiPath Automation Cloud is a public cloud offering. It is a cloud-based platform provided by UiPath and hosted on public cloud infrastructure. This means that UiPath manages and maintains the cloud infrastructure, and users access the services over the internet without the need to set up or manage their own private cloud infrastructure.</p><p>Automation Cloud, offered by UiPath, is a Software as a Service (SaaS) solution. Unlike traditional software installations, Automation Cloud doesn’t necessitate any installation on your end. UiPath takes care of all management aspects, from infrastructure to updates. All you need to do is register with Automation Cloud, and you can promptly begin utilizing its capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YpVvCT-07l2z0qYg2t6Xlg.png" /><figcaption>Fig 1.2 UiPath Platform Deployment Options</figcaption></figure><h3>When to use Private and Public Cloud:</h3><p>The choice between using a public cloud or a private cloud depends on your organization’s specific needs, requirements, and goals. Here are some guidelines for when to use each type of cloud deployment:</p><p><strong>Public Cloud:</strong></p><ol><li><strong>Cost Efficiency:</strong> Public cloud services are often cost-effective, as you only pay for the resources you use. This can be advantageous for small to medium-sized businesses with limited IT budgets.</li><li><strong>Scalability:</strong> Public cloud providers offer scalability on-demand, making it suitable for organizations with variable workloads and the need to quickly adjust resources as demand fluctuates.</li><li><strong>Quick Deployment:</strong> Public clouds provide preconfigured services, allowing for rapid deployment of applications and services without the need for extensive infrastructure setup.</li><li><strong>Global Reach: </strong>Public cloud providers have data centers in multiple regions, making it suitable for organizations with a global presence or those targeting a broad customer base.</li><li><strong>Reduced Maintenance:</strong> Public cloud providers handle infrastructure maintenance and updates, reducing the burden on an organization’s IT staff.</li><li><strong>Development and Testing:</strong> Public clouds are ideal for development, testing, and hosting non-sensitive applications, as they offer a convenient and cost-efficient environment for these purposes.</li></ol><p><strong>Private Cloud:</strong></p><ol><li><strong>Data Security and Compliance:</strong> Private clouds provide more control and customization, making them suitable for organizations with strict data security and compliance requirements, such as those in highly regulated industries like finance and healthcare.</li><li><strong>Customization: </strong>Private clouds offer greater flexibility and customization, allowing organizations to tailor the infrastructure to their specific needs.</li><li><strong>Performance:</strong> For applications with high performance demands, such as real-time data processing or large-scale analytics, a private cloud can provide dedicated resources to ensure consistent performance.</li><li><strong>Isolation:</strong> Private clouds are isolated from other organizations, providing enhanced privacy and security for sensitive data and applications.</li><li><strong>Legacy Systems: </strong>Organizations with legacy systems and existing data centers can implement a private cloud to extend the life and capabilities of their on-premises infrastructure.</li><li><strong>Hybrid Cloud Needs</strong>: For organizations seeking a hybrid cloud setup, a private cloud can be part of the solution, allowing them to maintain control over sensitive data while leveraging the benefits of public cloud resources.</li></ol><h3>Conclusion:</h3><p>In many cases, organizations adopt a hybrid cloud strategy, combining both public and private cloud deployments to balance cost-effectiveness, scalability, and security based on the specific needs of different workloads and applications.</p><p>Happy Automation with UiPath!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=295e8202c587" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Code Quality through UiPathCustom Workflow Analyzer Rules]]></title>
            <link>https://jobinthekkekarajoy.medium.com/enhancing-code-quality-through-uipathcustom-workflow-analyzer-rules-68cc2f65256b?source=rss-1c1cc5859047------2</link>
            <guid isPermaLink="false">https://medium.com/p/68cc2f65256b</guid>
            <category><![CDATA[uipath-training]]></category>
            <category><![CDATA[custom-code]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[intelligent-automation]]></category>
            <dc:creator><![CDATA[Jobin Thekkekara Joy]]></dc:creator>
            <pubDate>Mon, 09 Oct 2023 03:22:31 GMT</pubDate>
            <atom:updated>2023-10-24T13:55:43.923Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhancing Code Quality through UiPath Custom Workflow Analyzer Rules</h3><h3><strong>The Motivation:</strong></h3><p>In the realm of software development, ensuring the highest quality in our code is paramount. At times, during the meticulous process of reviewing code for a project, we stumble upon certain oversights that could have significant consequences. One such scenario we noticed was the absence of a crucial check in some HTTP requests utilizing the POST method.</p><p>Specifically, we observed that in some instances, developers were not verifying whether the expected HTTP status code was returned by the server in response to their POST requests. This seemingly minor omission can have profound implications. Without confirming the status code of a particular HTTP request, we cannot guarantee that the request successfully reached the intended endpoint and was processed as intended.</p><p>To address this issue and bolster the robustness of our codebase, we are excited to introduce our custom workflow analyzer. This innovative tool is designed to enforce the inclusion of response status checks in every HTTP request within our projects. By doing so, we aim to significantly enhance the reliability and accountability of our code, ensuring that each request not only reaches its destination but also meets the expected criteria for success.</p><p>In this blog post, we’ll delve deeper into the motivation behind our custom workflow analyzer and explore how it can be a game-changer in our development processes. We’ll also highlight the benefits of incorporating response status checks into our HTTP requests and discuss how this simple yet crucial step can elevate the quality and integrity of our code. So, let’s embark on this journey to improve code quality and make our development workflow even more robust with the introduction of our custom analyzer.</p><h3><strong>Introduction to UiPath Workflow Analyzer:</strong></h3><p>UiPath Workflow Analyzer is a static code analyzer as part of UiPath Studio that ensures your automation meets best practices and standards. This static code analyzer checks for inconsistencies without actually executing the project, as opposed to dynamic analyzers which step in during execution.</p><p>To build custom rules, you need the <strong>UiPath.Activities.Api</strong> package from the Official feed. The SDK package must be used as a development dependency in your custom project.</p><h3><strong>Prerequisites:</strong></h3><p>When building custom rules, target the .NET version depending on the version of Studio and the project compatibility:</p><ul><li>Studio 2021.4 and earlier: .NET Framework 4.6.1.</li><li>Studio 2021.10.6 and later: .NET Framework 4.6.1 for Windows-legacy projects, .NET 6 for Windows and cross-platform projects.</li></ul><h3>Workflow Analyzer Key Concepts:</h3><h3>1. Rules and Counters</h3><p>A <strong>rule </strong>represents a requirement that must be met. It can be set to check the inspection object against the rule definition.</p><p>A <strong>counter </strong>represents a check done for revealing the number of times a particular event or condition has occurred.</p><h3>2. Inspection Object</h3><p>There are three different type of Inspection Objects available</p><ul><li><strong>Activity</strong>: it is the smallest inspection object. For example, Variables Naming Convention, Variable Length Exceeded, and File Activities Stats are three out-of-the-box rules that can be set to inspect activities.</li><li><strong>Workflow</strong>: rules or counters may be set to perform checks in just a single project file. High Arguments Count and Empty Sequence are just two predefined rules that have workflow as their scope.</li><li><strong>Project</strong>: checks are performed at the project level, ensuring project reliability is met. Unused Dependencies is a rule applied at the project scope.</li></ul><h3>Implementation Steps and Demostration:</h3><p>This project will be responsible to validate/inspect the HTTP request activity object and returning the inspection result based on the logic implemented.</p><p><strong>Note:</strong> For Demostration purpose, i have implemented only one logical check and it’s outcome is here. Based on your need, you can enhance this implementation or after understanding the key concepts, you can develop a brand new workflow analyzer with relevant scope (Project/ Workflow/ Activity)</p><p><strong>Step 1:</strong> Create a Class Library project on Visual Studio and name it as in the below inline screenshots. You can choose framework version based on requirement. Recommending .Net 6.0 for Windows compatibility projects</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WWIriamwCLcNU1kFHsM8Xg.png" /><figcaption>Fig 1.1 Visual Studio Class Library Project Template</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*Frp09o0pkujdhNJ3a8_VNQ.png" /><figcaption>FIg 1.2 Name your workflow analyzer project</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*Qr3f1ligmrFV2MvcV0GCkQ.png" /><figcaption>Fig 1.3 Choose .Net Framework version based on the requirement</figcaption></figure><p><strong>Step 2:</strong> Implement the IRegisterAnalyzerConfiguration interface with the following method Initialize(IAnalyzerConfigurationService workflowAnalyzerConfigService). The below inline screenshot contains constants to be used through the project as well alone with Interface implemnentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JGpMpUsFkpAXnAr1jLH0Lg.png" /><figcaption>Fig 2.1 IRegisterAnalyzerConfiguration implementationan and constants</figcaption></figure><p><strong>Note: </strong>This methiod offers an injection point to the implementing assembly in order to access <strong>UiPath.Studio.Activities.Api.Analyzer.IAnalyzerConfigurationService</strong> capabilities.</p><p><strong>Step 3:</strong> Create a Static method to build Rule object for specific scope. In this case, scope is set at Activity Level. This static method is already called inside Initialize(IAnalyzerConfigurationService workflowAnalyzerConfigService) implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Wl7oupft0QwOZlPm8ISvMg.png" /><figcaption>Fig 3.1 Static method to create Rule object</figcaption></figure><p><strong>Step 4: </strong>Building the logic which is responsible for inspect each Activity Object and return the InspectionResult object with relevant properties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgTfgFfuFq0qUnG1EpSjDA.png" /><figcaption>Fig 4.1 Logic to Inspect the Activity Object</figcaption></figure><p><strong>Step 5:</strong> Build the project and copy the dll from current project directory to UiPath Workflow Analyzer Rule directory( Ideally <strong>C:\Program Files\UiPath\Studio\Rules\net6.0</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*alWdddfvFJjuBJ255olXwg.png" /><figcaption>Fig 5.1 Copying the DLL file to UiPath’s Rules Local directory</figcaption></figure><p><strong>Step 6: </strong>Close and re-open UiPath Studio to get it reflected on the Workflow Analyzer Window</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2earqgsNIDpBLTyq0sBfsg.png" /><figcaption>Fig 6.1 Newly added Activity level Workflow Analyzer with recommendation message</figcaption></figure><p><strong>Step 7:</strong> Click on Analize Project and Error List Panel will be showing the inspection result if you are not storing the Response status on a variable.</p><p><strong>Note:</strong> “<strong><em>By adding extra logic, we can also check whether we used the Response status variable used further in the code to enusre that the HTTP request returns expected status code</em></strong>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LALL-GvqEZu9p7yCbIGRDQ.png" /><figcaption>Fig 7.1 Analyze Project</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3VzdJMKWe4-BAf1S7xzDEQ.png" /><figcaption>Fig 7.2 Error List in the case of no variable used in the Response status property</figcaption></figure><h3>Debugging Workflow Analyzer:</h3><ol><li>Once you have compiled your rules into a library, *.dll, copy the dll into the path of UiPath Studio. Usually this is <strong>C:\Program Files\UiPath\Studio\Rules\net6.0</strong>).</li><li>Open UiPath Studio to a project you wish to analyze.</li><li>Use the debug option in Visual Studio to attach to a process.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*fZGeXuApA9H-Yl1VS4cYvA.png" /><figcaption>Options to Attach a Process</figcaption></figure><p>4. You should see a process called UiPath.Studio.Analyzer.exe. Select it and click the “Attach” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*0OHzg-qiCxC3bZOW1uWQuA.png" /><figcaption>Attaching UiPath.Studio.Analyzer.exe</figcaption></figure><p>5. At this point you can set a break point in Visual Studio. The rule I am debugging is at the project scope, so use the Analyze Project option in UiPath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*CAshdaR4azH0ZusXGxvqIA.png" /><figcaption>Analyze Project</figcaption></figure><p>6. The debugger should halt on the break point, allowing your to examine the values of all local variables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_oFxnOEqHgvOuBVmOYPmA.png" /><figcaption>Debugging on Visual Studio</figcaption></figure><h3>Conclusion:</h3><p>In the dynamic world of automation, consistency and adherence to best practices are the cornerstones of success. Ensuring that your workflows and automation projects align with industry standards is not just a desirable goal but a critical necessity. UiPath, a leading name in the automation sphere, recognizes this need and provides a powerful tool to make it happen — the UiPath Workflow Analyzer.</p><p><strong>Streamlining Your Workflow Standards:</strong></p><p>The UiPath Workflow Analyzer is your ally in ensuring that your automation projects consistently adhere to established best practices. It’s your compass for maintaining a high level of quality and uniformity across your automation solutions.</p><p><strong>Enforcement with Ease:</strong></p><p>The key to unlocking the full potential of the Workflow Analyzer lies in enabling its enforcement. By configuring this feature in the Design Settings of UiPath Studio, you can effortlessly ensure that your projects adhere to best practices automatically. This enforcement can take place during various critical phases, such as Publish, Run, or Check-In, depending on your workflow requirements.</p><p><strong>Experience the Benefits:</strong></p><p>Enforcing best practices and standards through the UiPath Workflow Analyzer is a game-changer for any automation enthusiast or developer. Here are some compelling reasons to make it an integral part of your automation journey:</p><p><strong>Consistency:</strong> Say goodbye to inconsistencies and haphazard coding practices. With the Workflow Analyzer, your projects will maintain a uniform and structured approach, regardless of team size or project complexity.</p><p><strong>Efficiency: </strong>Save valuable time and resources by addressing potential issues early in the development cycle. The Workflow Analyzer identifies and rectifies deviations from best practices, allowing you to focus on creating efficient automation solutions.</p><p><strong>Reliability: </strong>Automation solutions built with the Workflow Analyzer are inherently more reliable. You can trust that your workflows will consistently meet the standards, reducing the risk of errors and failures.</p><p><strong>Embrace Automation Excellence:</strong></p><p>Incorporating the UiPath Workflow Analyzer into your development process is a pivotal step toward building automation solutions that are robust, efficient, and reliable. It’s your tool for creating a future where automation consistently delivers excellence.</p><p>So, let’s take a proactive approach to elevating the quality of our automation solutions. Enable the UiPath Workflow Analyzer, and together, we’ll embark on a journey of automation excellence. Happy Automation!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68cc2f65256b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing UiPath-Coded Workflow]]></title>
            <link>https://jobinthekkekarajoy.medium.com/introducing-uipath-coded-workflow-94fb5b2b9897?source=rss-1c1cc5859047------2</link>
            <guid isPermaLink="false">https://medium.com/p/94fb5b2b9897</guid>
            <category><![CDATA[hybrid-automation]]></category>
            <category><![CDATA[intelligent-automation]]></category>
            <category><![CDATA[rap]]></category>
            <category><![CDATA[uipath-coded-workflow]]></category>
            <category><![CDATA[uipath]]></category>
            <dc:creator><![CDATA[Jobin Thekkekara Joy]]></dc:creator>
            <pubDate>Sat, 29 Jul 2023 11:12:50 GMT</pubDate>
            <atom:updated>2023-07-29T11:42:15.632Z</atom:updated>
            <content:encoded><![CDATA[<p>Coded workflows are the same as low-code workflows, the only difference being that you build them using separate interfaces. Normal workflows have a visual design interface whereas in Coded workflows have a code-based interface.</p><p>Additionally, you can integrate coded workflows with low-code activities and workflows and use a hybrid automation approach. This enables you to combine the benefits of code-based automation with the visual design of low-code components.</p><p><strong>How to Get Started with Coded Automation:</strong></p><p>The 2023.6 Community release introduces an exciting feature called Coded Automation, which is now available as a Public Preview. This article will guide you through the process of getting started with Coded Automation and explore the various file types you can create.</p><p>Both coded workflow and coded test case automations use the CodedWorkflow base class from the <strong>UiPath.CodedWorkflows</strong> package. This class gives the automation access to necessary interfaces for activity packages (services), based on the installed packages in your project.</p><p><strong>Prerequisites</strong></p><p>· Install UiPath Studio 2023.6.</p><p>· Install the versions of the activity packages, also known as services, supported in coded automation:</p><p><em>System.Activities 23.6-preview<br> UiAutomation.Activities 23.6-preview<br> Testing.Activities 23.6-preview</em></p><p><strong>Creating a New Project</strong></p><p>To begin, you need to create a new Modern or Portable project. Both Visual Basic (VB) and C# are supported as workflow expression languages, providing you with flexibility in your development process.</p><p>Once you have created your project, you can proceed to create three new types of files (Coded Workflow, Coded Test Case and Code Source File) within the Coded Automation framework. Each file type serves a specific purpose and offers unique functionalities as in the below inline screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*CsjSeVK3wfqlE_sUWl0VnQ.png" /><figcaption>Coded File Types</figcaption></figure><h4>Benefits</h4><p>Here are some of the benefits of using coded automations:</p><p>1. <strong>Enhanced productivity</strong> — If you’re familiar with coding or scripting you can leverage your skills and increase your productivity. Working within a familiar coding environment allows you to develop more efficient automation.</p><p>2. <strong>Complexity management</strong> — Coded automations provide a flexible solution for managing complex automation scenarios. By using code, you can implement custom logic, manage exceptions, and create reusable functions.</p><p>3. <strong>Hybrid automation </strong>— You can use coded automations interchangeably with low-code automations. This promotes seamless integration between the two approaches, enabling you to create flexible automation solutions.</p><p>4. <strong>Improved performance</strong> — Coded automations empower you to optimize your automation workflows to enhance performance. By using code, you can implement specific algorithms to make your automation executions faster.</p><p>5. <strong>Readability</strong> — Coded automations allow you to create structured code, resulting in code readability. If you organize your code and document it, you can easily maintain it and share it with other collaborators.</p><h4>Why Choose Coded Automations Over Low-Code Solutions?</h4><p>· Coded automation offers higher productivity and flexibility, allowing developers to handle complex automation tasks with ease.</p><p>· Coded automation has an edge in collaboration, enabling efficient code reviews, bug fixing, and simultaneous work on different parts of the automation project.</p><p>· Coded automation provides structured and organized code, enhancing readability and maintainability compared to convoluted logic in low-code solutions.</p><p>· Coded automation allows fine-tuning for optimal performance, including algorithm optimization and efficient resource utilization.</p><p>· Transitioning to coded automation is easier for developers with coding experience, leveraging existing knowledge and skills.</p><p>· Developers can unlock a new level of productivity, complexity management, collaboration, reviewability, readability, and performance with coded automation.</p><p>· Coded automation empowers developers to create powerful, efficient, and customizable automation.</p><h4>Sample Project:</h4><p>This project will be responsible for login into UiBank web application (<a href="https://uibank.uipath.com/">https://uibank.uipath.com/</a>) and creating a savings account based on the input data.</p><p><strong>Step 1: </strong>Create a new process in UiPath Studio with Windows compatibility and Language as either VB or C#</p><p><strong>Step 2: </strong>Create an object repository based on your requirement as in the below inline screenshot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*TsFyEgQwuS5fSiURp_GaDA.png" /><figcaption>Object Repository for the project (Add or Delete Elements based on the requirement)</figcaption></figure><p><strong>Step 3: </strong>Create the coded workflow logic to log in to UiBank web application and call it on Main.xaml as in the below inline screenshot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bX1tOplbSYHRgs3dmwqIRQ.png" /><figcaption>Fig 1 of 3 Coded Workflow for UiBank Account Login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AxMIIrUp1iQ7h2wua5QXtg.png" /><figcaption>Fig 2 of 3 Coded Workflow for UiBank Account Login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3HUipFU03pMOqQphV3NyBw.png" /><figcaption>Fig 3 of 3 Coded Workflow for UiBank Account Login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADxKt1-_pBd4j8nl37eNtQ.png" /><figcaption>Calling Coded Workflows in Main.Xaml</figcaption></figure><p><strong>Step 4: </strong>Upon a successful UiBank login, invoke the coded workflow for applying for new account and display the newly generated account number</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DH_979qBb78X0WiQSFgqXw.png" /><figcaption>Fig 1 of 2 Coded Workflow for Applying New Account</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GGS3Bo8nHbk0Xc48Wm4MfA.png" /><figcaption>Fig 2 of 2 Coded Workflow for Applying New Account</figcaption></figure><p><strong>Conclusion:</strong></p><p>Coded Automations open doors to Hybrid Automation by enabling the integration of external systems, cutting-edge technologies, and emerging trends. Developers can leverage external integrations and utilize the latest advancements to create more powerful and advanced automation solutions. This code-centric approach offering, developers to unleash their creativity and build highly customized and efficient automation.</p><p>Start exploring the Coded automation and revolutionize your automation journey with UiPath Studio today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94fb5b2b9897" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>