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)
1
Part 1:Role of a Solution Architect
5
Part 2:Being Techno/Functional
11
Part 3: Tool Agnostic Approach
17
Part 4:Best Practices
22
Epilogue

Security standards

Security is always paramount for the IT industry. It is inevitable to not define the standards that a bot should follow. To do this, there should be guidelines that developers can follow throughout the development process. This not only applies to development but also to design so there is no room for security breaches. Some of the ways we can achieve this are as follows:

  • Predefining the bot access and evaluating it based on the actions it is going to perform will give you an idea of whether the bot has access it does not need, to avoid it from becoming a security issue. Having a resource-based access control (RBAC) design will make sure that the bot doesn’t get any extra access. Also, baking the information security guideline into the framework will ensure it is implemented without fail.
  • Do not hardcode any sensitive information, such as API keys and tokens, within the code. Rather, storing this sensitive information in a centralized database...