![4
Process Automation Lifecycle(RPA Lifecycle)
❑ Prepare RPA – Calculate and understand the automation complexity of the in-scope processes, Map
the automation benefits
❑ Solution Design- Document and validate As-Is process flow and all relevant data for RPA, Design the
To-Be process flow [Handover Documents ]
❑ Build RPA- Design Workflow and Update the PDD to include the requested changes.
❑ Test RPA- Test scenarios to cover all the business use-cases, rules and exceptions
❑ Stabilize RPA- User Manual must be updated throughout all the implementation phases
❑ Constant Improvement - Monitor the performance of the process and measure it against the baseline](https://image.slidesharecdn.com/rpadeveloperkickstarterday11bestpracticesandrpalifecycle-220613152503-dbee23aa/85/RPA-Developer-Kickstarter-Day-11-Best-Practices-and-RPA-Lifecycle-pdf-4-320.jpg)
RPA Developer Kickstarter Day 11 Best Practices and RPA Lifecycle.pdf
- 1. RPA Developer Kickstarter Day 11 Best Practices and RPA Lifecycle
- 2. 2 1. Introduction 2. Process Automation Lifecycle(RPA Lifecycle) 3. Process Documentation Method 4. PDD Template Using Task Capture Tool 5. RPA Lifecycle Documents Sample 6. Best Practices 7. Assignment based on Task capture Agenda
- 3. 3 Satish Prasad, Holds Master Degree from NIT Kurukshetra. He has 10+ years of experience in IT Development & Maintenance ranging in Data analytics, Datawarehouse, ETL, Production support & Robotics Process Automation. • Trained many professionals on RPA Automation tools Such as UiPath, Robot Framework. • Currently working as an RPA Solution Architect in Leading IT MNC in Delhi NCR. • Actively contribute to #UiPath Community through various programs. • Owns RPABOTSWORLD.COM Blog that has established itself as an indispensable resource for robotics process automation education and community building. • https://www.linkedin.com/in/prasad-satish/ Introduction
- 4. 4 Process Automation Lifecycle(RPA Lifecycle) ❑ Prepare RPA – Calculate and understand the automation complexity of the in-scope processes, Map the automation benefits ❑ Solution Design- Document and validate As-Is process flow and all relevant data for RPA, Design the To-Be process flow [Handover Documents ] ❑ Build RPA- Design Workflow and Update the PDD to include the requested changes. ❑ Test RPA- Test scenarios to cover all the business use-cases, rules and exceptions ❑ Stabilize RPA- User Manual must be updated throughout all the implementation phases ❑ Constant Improvement - Monitor the performance of the process and measure it against the baseline
- 6. 6 TRAINER WILL DEMO TASK CAPTURE.
- 7. 7 1. Introduction 1.1 Purpose of the Document 1.2 Objectives 1.3 Key Contacts 1.4 Minimum Prerequisites for Automation 2. As-Is Process Description 2.1 Process Overview 2.2 Applications Used in the Process 2.3 As-Is Process Map 2.4 Detailed As-Is Process Steps 2.5 Input Data Description 3. To-Be Process Description 3.1 To-Be Detailed Process Map 3.2 Parallel Initiatives / Overlap (if applicable) 3.3 In Scope for RPA 3.4 Out of Scope for RPA 3.5 Business Exceptions Handling 3.6 Application Error and Exception Handling 3.7 Reporting 4. Other Observations 5. Additional Sources of Process Documentation A process documentation that describes only “the happy path” is considered incomplete, so it is important to keep track of both business exceptions and technical exceptions. Make sure you cover all possible scenarios when something might not go as planned PDD – Table of Contents
- 8. 8 RPA Lifecycle Documents Sample • PDD – What is being automated • SDD or DSD- How to be automated • Test Scenarios- How to be tested • Release Notes – How to be deployed • Operation Handover Guide- How to be supported Development Specification Document Solution Design Document
- 9. 9 Best Practices • Efficient execution and effective error handling • How to avoid common errors
- 10. 10 1. Naming convention and strategy – Follow organization practice for all variables, arguments, workflow names. 2. No hardcoded delays. 3. Configurations – Keep out side code 4. Credentials – Robot and Application Credentials no hardcoded or plain text should be managed via assets in UiPath or other PM 5. Reliable selectors - Validate multiple times & carefully select variables. 6. UI Synchronization – Validate before perform & Verify Application State 7. Input Types – Try different Input types for navigation and data entry via the Click and Type Into activities 8. Exception handling - log the exception and then rethrow the exception if required to follow “Bubble-up” concepts 9. Use Workflow analyzer before publishing the package UiPath Automation Best Practice Guide
- 12. 12 Assignment – Work with Task Capture Don’t forget to share your learning on Social media #uipathcommunity, #rpakickstarter, #taskcapture