The way RPA works is by emulating a human user. I can't say that this is from experience though since My main experience was with Process Robot and a little bit with UIPath. We are hoping that since Microsoft bought Softomotive, some of the issues will be tackled, but from my discussions with other people from the rpa sub-reddit, the major issues we're facing are common to the whole industry. RPA a really good tool for some things, and lacking in others. I knew about RPA beforehand, and was training with another program before this full time job directly using RPA, so basically my current company just gave me a hammer, roughly showed me how to use it and pointed me towards some nails. Ideally you'd have separate people for these tasks obviously, but the whole idea behind RPA, and buzzword the marketing people like to use, is to have citizen developers develop their own BOTs/Flows/Processes. I've only been working with RPA for 1.5 years and I'm the only full timer in my department, so I have to go through the whole process of analyzing, designing, developing and testing, and post-release maintenance. If you'd like some more information on the subject of RPA, you can join r/rpa as well. I currently work with Process Robot RPA, which is the licensed RPA program by Softomotive, the development company the article mentions was bought by Microsoft.
0 Comments
Leave a Reply. |