Book Image

RPA Solution Architect's Handbook

By : Sachin Sahgal
Book Image

RPA Solution Architect's Handbook

By: Sachin Sahgal

Overview of this book

RPA solution architects play an important role in the automation journey and initiatives within the organization. However, the implementation process is quite complex and daunting at times. RPA Solution Architect’s Handbook is a playbook for solution architects looking to build well-designed and scalable RPA solutions. You’ll begin by understanding the different roles, responsibilities, and interactions between cross-functional teams. Then, you’ll learn about the pillars of a good design: stability, maintainability, scalability, and resilience, helping you develop a process design document, solution design document, SIT/UAT scripts, and wireframes. You’ll also learn how to design reusable components for faster, cheaper, and better RPA implementation, and design and develop best practices for module decoupling, handling garbage collection, and exception handling. At the end of the book, you’ll explore the concepts of privacy, security, reporting automated processes, analytics, and taking preventive action to keep the bots healthy. By the end of this book, you’ll be well equipped to undertake a complete RPA process from design to implementation efficiently.
Table of Contents (25 chapters)
Part 1:Role of a Solution Architect
Part 2:Being Techno/Functional
Part 3: Tool Agnostic Approach
Part 4:Best Practices

Use cases

Let’s now go through some use cases that are well suited for reusable components and some examples to get you started.

Use case 1

A common use case that we see very often in the RPA world is the use of PDF files. PDF is a common format in which data and text are shared across the organization. With the wide use of PDF documents, their association with automation is inevitable. PDFs come in many types. There can be text, pictures, scanned images, forms, and many more. All these different types can be a part of the process that you are trying to automate. If there are many processes using a PDF, it makes sense to have a common package, library, or reusable component that can be developed once and reused as and when necessary. Some common operations that involve PDFs are as follows:

  • You might have a process that uses PDF documents as a form from the customer. This type of process is categorized as an intake process. A PDF form is given to the customer, which...