3 ms·
Obligatory RPA: GUI-based automation to mimic user interactions, leveraging existing application and web GUIs as an API to automate against. Not something I'd
by ethbro 7y ago
Obligatory RPA: GUI-based automation to mimic user interactions, leveraging existing application and web GUIs as an API to automate against.
Not something I'd recommend to backend developers / data crews. But it's pretty awesome stuff for non-developer, front-line business users.
What is RPA? - https://www.uipath.com/rpa/robotic-process-automation https://www.uipath.com/rpa/robotic-process-automation
UiPath free, "unlimited time for non commercial use" trial - https://www.uipath.com/product/studio https://www.uipath.com/product/studio (you're looking for "Community Edition")
Disclaimer: I have no financial interest in UiPath as a product, past running a business user-focused automation enablement team that is currently using it. I've been in the space about a decade, and just happen to think they do it "better" than anyone else currently (YMMV. Pegasystems' RPA offering is also great, but they don't talk to non-Fortune 500s or advertise it)
- carapace 7y agoSo, this looks to me like a marketing layer ("Robots!") over a macro-recorder on steroids. I'm not complaining, I bet you can make a lot of money doing this, and it's arguably helpful to the clients, but am I missing something? Like, there are no actual robots involved, yeah?
- ethbro 7y ago"Macro-recorder on steroids" is a surprisingly tricky thing to do well. Think supporting 30+ years of different UI frameworks, over process variants that may be dissimilar (e.g. when code = 5, the "OK" button is actually a different class). All while hiding enough of the underlying complexity that a business user ignorant of all the above can write 95%+ of the automation. So yes, I'd say it's one of those things that seems easy, but is difficult to actually get working for compatibility reasons. There are no physical robots involved. ;)