My first RPA process definition meeting went something like this:
- Is this a good process to automate? Yes
- Is there any documentation? No
- Does the SME know the process? Yes, but there are 3 different ways of completing the same set of tasks
- How do we create the documentation? Let's make a WebEx recording!
Surely there is a better way of doing this work! While other RPA platforms insist on creating 'Record' buttons, Blue Prism has made it clear that the tool will not go down the route of desktop automation. Hence there was a need to fill the gap for being able to capture a process efficiently and accurately.
Capture
Capture was launched to help with the above, but it goes beyond just capturing low-level details of individual tasks. With the release of Capture 2.1 we are well on our way in our journey to reduce the gap between business analysis and automation development.
To start with, Capture does exactly that, i.e. it captures the individual clicks and data entry as the SME goes about completing the business process end to end. However, there are certain pre-requisites required to make sure the activity goes smoothly.
Make sure you have a defined process that you want to capture end to end and the person stepping through it knows the low-level details of each step. While Capture is very flexible in letting you make changes one process has been captured, it's still much easier to get it right in the first place.
Test data. Never underestimate the importance of valid scenarios and the availability of test data throughout the RPA journey. The same applies to the use of Capture. The tool lets you start and stop, but your life will be so much easier if you have the right scenario and the right data already in place.
This applies to the happy path as well as the exception flows. The more prepared you are the smoother the experience.
The Next Iteration
The pinnacle of RPA development is to have the automation be created as the business requirements are being defined. And Capture is well on its way in that direction. With a click of a button, you are now able to create a Blue Prism release file based on the captured business process. It creates a wireframe of the automations, which may sound basic for now, but it brings several advantages with it:
- Taking care of the mundane tasks while creating an automation (even here!)
- Ensuring consistency in naming conventions
- Consistency of the logical break up of pages and subpages within an automation
- Etc.
The tool is free to use and easy to install. There are minimal overheads. Hence there is absolutely no reason not to start getting used to it since tools like Capture will be the building blocks of where Blue Prism is headed towards in the future.
------------------------------
Usman Azim
Professional Services
Blue Prism
------------------------------
Usman Azim
Professional Services
Blue Prism
