This is the sixth and final post in a series about the four styles of RPA (Robotic Process Automation) in OSS.
Over the last few days, we’ve looked into the following styles of RPA used in OSS, their implementation approaches, pros / cons and the types of automation they’re best suited to:
- Automating repeatable tasks – using an algorithmic approach to completing regular, mundane tasks
- Streamlining processes / tasks – using an algorithmic approach to assist an operator during a process or as an alternate integration technique
- Predefined decision support – guiding operators through a complex decision process
- As part of a closed-loop system – that provides a learning, improving solution
RPA tools can significantly improve the usability of an OSS suite, especially for end-to-end processes that jump between different applications (in the many ways mentioned in the above links).
However, there can be a tendency to use the power of RPAs to “solve all problems” (see this article about automating bad processes). That can introduce a life-cycle of pain for operators and RPA admins alike. Like any OSS integration, we should look to keep the design as simple and streamlined as possible before embarking on implementation (subtraction projects).Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email