1. UiPath - Introduction to the RPA Developer Role - Giri
Installing UiPath Studio
-Community Edition Always free. Upgrade to Enterprise any time. 2 Studios for designing automation 3 Robots Cloud-hosted Orchestrator Forum-only support UiPath Academy access -Enterprise Server Edition On-premises enterprise deployments for large businesses. Unlimited Studios for designing automation Unlimited Robots On-premises Orchestrator Premium Support Scale as you grow Self managed updates UiPath official training partners -Enterprise Cloud Edition Cloud enterprise deployments for businesses of any size. Currently in Preview. Unlimited Studios for designing automation Unlimited Robots Cloud-hosted Orchestrator Premium Support Scale as you grow Always up to date Centralized user access management Secure and compliant UiPath official training partners
Automation Complexity
-Number of Screens RPA works by programming the robot to perform tasks at screen level (when the screen changes, the logic has to be taught). The higher the number of screens, the more elements have to be captured and configured prior to the process automation. -Types of Applications Some applications are more easily automated (such as the Office suite or browsers), others heavily increase the automation effort (Mainframe, for example). And the more different the applications are, the number of screens will increase, as well (see previous point). -Business Logic Scenarios An automation's complexity increases with the number of decision points in the business logic. Basically, each one could multiply by two the number of scenarios. -Types and Number of Inputs As previously stated, standard input is desirable. Yet there are cases in which one standard input (such as an invoice) has to be configured for each supplier that will be affected by the automation. Moreover, non-standard input can be of different complexity grades, with free text being the most complex.
Process Fitness
-Rule-based The decisions made (including data interpretation) in the process can be captured in a pre-defined logic. The exception rate is either low or can be included as well in the business logic. -Automatable and/or repetitive process We can differentiate 4 types of processes: Manual & non-repetitive: the process steps are performed by humans and can be different every time the process is executed Manual & repetitive: the steps in the process are performed by the user, and at least some of them are the same every time Semi-automated & repetitive: some of the repetitive steps have already been automated (using macros, Outlook rules, and so on) Automated: there are processes that have been already automated using other technologies than RPA Processes that need to stay manual or are non-repetitive, due to the high exception rate or factors that cannot be integrated in a business logic, aren't good candidates for automation. -Standard input The input in the process should either be electronic and easily readable or readable using a technology that can be associated with RPA (such as OCR). A good example is an invoice having the fields pre-defined. -Stable Processes that have been the same for a certain period of time and no changes are expected within the next months are good candidates for automation, provided they meet the other criteria as well.
The automation first three-pronged approach:
1.A Robot for Every Person Just as Bill Gates envisioned a world with a PC for every desktop, UiPath envisions a world with a robot for every person. When every worker has a robot to help with mundane tasks, it frees employees to use time for higher-level work. Workers feel less stressed and become happier and more productive.. 2.Open and Free Collaboration In business, cooperation and competition are deeply co-dependent. Technologies, too, can work together, and can also work with people. Ideas can mix, mingle, and make magic. By facilitating these unions, whether through our community, our partners or through a combination of both, UiPath creates an environment to nurture automation first and to accelerate human achievement. 3.Robots Learn Skills We're enabling robots to learn new skills through AI and machine learning. To help humans, robots not only must do the grunt work, but they need to be able to act intelligently. With AI and machine learning, robots can extend the scope of work they complete beyond rules-based-action to judgment tasks.
The Robot
Executes the workflows and instructions sent locally or via Orchestrator. There are two types of robots: • Attended - is triggered by user events, and operates alongside a human, on the same workstation • Unattended - run unattended in virtual environments and can automate any number of processes
UiPath Studio
Helps you design automation workflows visually, quickly and with only basic programming knowledge. Studio is where the automated processes are built in a visual way, using the built-in recorder, drag & drop activities and best practice templates.
Who will you be working with?
Here are some of the roles you will most often be in contact with in RPA implementations: Solution Architect - Is in charge of defining the Architecture of the RPA solution. The Solution Architect translates the requirements captured by the functional analysts, creating the architecture and design artifacts. They lead, advises, and is responsible for the developers' team delivery. Business Analyst - Is responsible for mapping of the AS IS and proposed TO BE processes. Business Analysts hold knowledge of the business process that gets automated, general business process theory and RPA capabilities. They are responsible with listing the process requirements for automation, clarifying the inputs and expected outputs, creating RPA documentation (Process Design Documents, Process maps. Implementation Manager/Project Manager - Forms and manages the RPA team, does resource planning and teams availability, in order to hit automation goals. Most of the times the PM is the Single Point of Contact (SPOC) for questions, RPA initiatives, or parallel RPA product projects. RPA Developers - On complex projects, several developers will collaborate to automate all processes. Infrastructure & IT Security admin - With good technical and security skills, they are responsible for setting up and maintaining hardware & software resources for UiPath product installations. They set up accounts for all the devs, end users and robots. Process Owner - Is the key stakeholder and beneficiaries of the RPA solution. Usually Senior Management level, with some 10-15+ years of experience, possibly split across domains. Multiple people can have this role, based on department (Finance, IT, HR, etc). RPA Support - Manage the robots after the processes have been moved to production, with support from the original RPA devs who have performed the automation. May have multiple levels of support: L1- Client, L2- client/ partner, (L0 - Super users; L3 - UiPath)
The Automation First Mindset
In the Automation First Era, you need to constantly look at your work and the processes in your company through the lens of automation potential. This is what we call the Automation First mindset. We envision a work world where "automation first" is the first thought when an employee needs help to accomplish a task or improve a work process. The first question will be, "how can I automate this task to improve my efficiency and effectiveness?", rather than trying to execute all work manually. Adopting an "automation first" mindset is the first step on the path to making digital transformation real in the enterprise. Thinking automation first enables your company to move faster and more effectively. It helps you serve customers better. It enables you to operate more efficiently. It unburdens your employees from mundane, repetitive work, allowing them to focus on solving problems and creating value.
Process Example: Order-to-Cash1
Inputs - The received Email message; Process Flows - the verification of the product code presence, the SAP transaction execution and the SAP fields population; Source Applications - Outlook, Desktop and SAP Outputs - the result generated by the process; Also, there are several sub-process outputs that serve as input for other sub-processes. For example, the result of the missing product code in the master data file check represents an input for the master data analyst to update the file. In the context of an RPA implementation, the process flow we have just described, along with the procedure documenting it, would be considered the "As-Is" process.
UiPath Orchestrator
Lets you control, manage and monitor the robots. It is also the place where libraries, reusable components, assets and processes used by the robots are stored. Orchestrator is a server application accessed via browser, through which the robotic workforce is controlled, managed and monitored: • The connections with the robots are created and maintained, and the robots are grouped (control) • The automated processes are distributed as tasks to the robots (management) • The execution of tasks is logged and kept track of (monitoring)
How do RPA implementation projects work?
Most often, we will find six stages in RPA implementations: 1 Prepare RPA - the processes are defined, assessed, prioritized and the implementation is planned. 2 Solution Design - Each process to be automated is documented ("as is" and "to be"), the architecture is created and reviewed, the test scenarios and environments are prepared and the solution design is created and documented for each process. 3 Build RPA - The processes are automated, the workflow is tested and validated and the UAT prepared. 4 Test RPA - The UAT is performed, the workflow is debugged and the process is signed off. 5 Stabilize RPA - The Go-Live is prepared, the process is moved to production, monitored, measured and the lessons learned are documented. 6 Constant Improvement - The process automation performance is assessed, the benefits tracked and the changes managed.
Assessing automation potential
NO RPA Processes where change is frequent, the system environment is volatile, and multiple manual (even non-digital) actions are required SEMI AUTOMATION Processes that can be broken down into steps that can be clearly automated, and steps that need to stay manual (such as validations or usage of physical security tokens) HIGH-COST RPA Processes that are rather digital and can be automated, but use some technologies that are complex (such as OCR) or require advanced programming skills ZERO-TOUCH AUTOMATION Processes that are digital and involve a highly static system and process environment, so that they can be easily broken into instructions and simple triggers can be defined
RPA Digital Transformation
RPA is probably the fastest path to digital transformation and one of the most efficient and effective. To better understand why, let's see first what it is and what it can do. RPA, or Robotic Process Automation, is the technology that enables computer software to emulate and integrate actions typically performed by humans interacting with digital systems.
What do RPA Bots do?
RPA robots are able to capture data, run applications, trigger responses, take decisions based on predefined rules and communicate with other systems. RPA primarily targets processes which are highly manual, repetitive, rule-based, with low exceptions rate and standard electronic readable input. RPA solutions can be thought of as virtual robotic workforces, whose operational management is made by the business line (only supported by IT), just like for a human workforce.
Meet the UiPath Platform
The UiPath Platform offers you the components you need to design and develop automation projects, execute the instructions automatically and manage your robot workforce. The components of the UiPath Platform are Studio (the workflow designer), Orchestrator (the robot management platform) and the Robot (the agent executing the instructions).
Quick Recap
The learning program we've prepared for you consists of: Foundation Training, Advanced Training and the Continuous Learning. 2 The Academy Ecosystem offers several platforms to help you succeed as an RPA Developer: Connect!, Marketplace, Community Forum and Academy. 3 RPA robots are able to capture data, run applications, trigger responses, take decisions based on predefined rules and communicate with other systems. 4 RPA primarily targets processes which are highly manual, repetitive, rule-based, with low exceptions rate and standard electronic readable input. 5 Automation First is a three-pronged approach: A Robot for Every Person, Open and Free Collaboration, Robots Learn Skills. 6 The components of the UiPath Suite are Studio (the workflow designer), Orchestrator (the robot management platform) and the Robot (the agent executing the instructions). 7 We've learned how to install UiPath Studio Community Edition. 8 We've learned how to create our first workflow. 9 A process is a set of interrelated or interacting activities that transforms inputs into outputs. 10 Most often, RPA implementations are organized on six stages: Prepare RPA, Solution Design, Build RPA Solution, Test RPA Solution, Stabilize RPA, Constant Improvement.
What is a Business Process?
The successful RPA developer combines a good grasp of the technical skill set with the ability to quickly understand business processes in terms of inputs, outputs and decision points. The latter will come into play when collaborating with an RPA Business Analyst on a large implementation project or when undertaking a smaller project on your own. Definition: A process is a set of interrelated or interacting activities that transforms inputs into outputs. Components of a process: Inputs - the data that goes in the process;Process Flows - the sequences of sub-processes or activities undertaken in the process;Source Applications - the applications or systems used to perform the sub-processes or activities of the process; Outputs - the result generated by the process;
The relation between processes and procedures
There are a lot of things that are missing from the definition of a standard process, such as time constraints, dependency on other processes, variations and how resources are assigned. This is where procedures come into play. Essentially, a procedure complements a process and describes the way it is carried out; it explains who is responsible for each part of the process, when each part of the process needs to occur, how to handle exceptions and the specifications applicable to each part of the process. A procedure explains: who is responsible for each part of the process when each part of the process needs to occur how to handle exceptions the specifications applicable to each part of the process. In what concerns the way they are documented, processes and procedures are different. A process is typically documented via a diagram, be it a flowchart or workflow, which aims to highlight the logical sequence of the process steps. A procedure, on the other hand, is often a complex, written document, focused on providing guidelines.
What makes a process a good candidate for automation
There are a number of factors you can take into account when considering if a process is fit for automation. Normally the analysis and prioritization are performed by an RPA Business Analyst, but it's useful for developers to evaluate the prioritization, while on smaller implementations, you may not have a Business Analyst in the team. There are two sets of criteria you can use to determine the automation potential: process fitness and automation complexity.
Process Example: Order-to-Cash
To better understand this, let's take a commonly automated business process and compare the manual ("As Is") flowchart with the automated ("To Be") flowchart. A Purchase Order is received via email. The agent opens the email attachment and checks that the product code is present in the PO. If the product code is present in the PO, the agent opens SAP and runs a specific SAP transaction.If the product code is not present in the PO, the agent looks it up in the master data file.If the product code is present in the master data file, the agent opens SAP and runs a specific SAP transaction.If the product code is not present in the master data file, the agent sends out an email to the Master Data Analyst to update the file. Once the product code is provided, the agent populates the required fields in the SAP screen, as per the organization requirements and the PO . Next, the agent generates the sales order. Finally, the agent replies to the initial email, adds the Sales Order in the attachment and moves the email to the processed folder.
