Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
RPA Solution Architect's Handbook

You're reading from   RPA Solution Architect's Handbook Design modern and custom RPA solutions for digital innovation

Arrow left icon
Product type Paperback
Published in Jun 2023
Publisher Packt
ISBN-13 9781803249605
Length 302 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Sachin Sahgal Sachin Sahgal
Author Profile Icon Sachin Sahgal
Sachin Sahgal
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Part 1:Role of a Solution Architect
2. Chapter 1: Why Do We Need a Solution Architect? FREE CHAPTER 3. Chapter 2: Case Study of a Banking Client 4. Chapter 3: Extracurricular Activities 5. Part 2:Being Techno/Functional
6. Chapter 4: Studying the Lay of the Land 7. Chapter 5: Designing Framework for Consistency and Resiliency 8. Chapter 6: Need for Documentation and Working with SIT/UAT Scripts 9. Chapter 7: RPA Development Phases 10. Chapter 8: Customer Obsession in the RPA Journey 11. Part 3: Tool Agnostic Approach
12. Chapter 9: Intelligent Automation 13. Chapter 10: Hyperautomation: The Future of RPA 14. Chapter 11: Reusable Components 15. Chapter 12: RPA as a Service (RPAaaS) 16. Chapter 13: Finding the Best Solution 17. Part 4:Best Practices
18. Chapter 14: Design Best Practices 19. Chapter 15: Data, Security, and Logs 20. Chapter 16: Key Performance Indicators (KPIs) 21. Chapter 17: Reporting, Analytics, Efficiency, and Efficacy 22. Epilogue
23. Index 24. Other Books You May Enjoy

POC

You may wonder why we are covering a POC at this stage and whether this should be covered by the SA during the solution stage. Well, you are right – this POC is not for the components, new technology, or any open source library but more for the application and other components that are involved in the process. Doing a quick POC will give you the confidence that there will be no roadblocks or impediments as the development advances. This needs to be taken care of at this stage to avoid any issues later, as then you will have neither the liberty to change your course of action nor the time to go back to the whiteboard to redesign the process.

Let’s understand this using a scenario.

You are working on an RPA project that involves three applications – one is a home-grown application developed on dotnet, the second application is a third-party application that is accessible only through a VPN, and the third application is based on a desktop thick client.

...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime