Related Posts
Anyone else super bored in quarantine?
Mentor
Is retail quant trading on a massive rise?
Additional Posts in Robotic Process Automation (RPA)
Anyone hiring for RPA roles in your company ?
Who wants to be a millionaire?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
EY1 is accurate, RPA is a non-code based automation solution that interacts with a system at the graphic user interface (GUI) level. This attribute makes RPA not only less costly and quicker develop, but also offering the benefit of being less risky from a technology and data perspective.
I also find it laughable next to none of you guys staff architects on rpa projects. You got a whole bunch of junior process people acting as devs leading these things and blaming the client when the "requirements" weren't correct lol.
EY3 I have had similar experiences. I think our organization tends to trust process design people to lead RPA projects which is wrong. It's enough to create POCs but their programming background is not strong enough to scale it. They don't know how a development projet is led. They lack understanding on defining standards, reusable tools, testing...etc. RPA it s a lightweight software development project. You need technical expertise to do it.
Robots
How come there's no code? AA, Uipath and BP all have coding features
I don't agree with what you are saying. You do code to program the interaction between the bot and the applications. It easier to support a standard program than a bot. There is too many moving pieces and most of the applications are not developed to fit automation.
Seriously the idea that youre not that reliant on coders/devs needs to stop. This is still lightweight software dev at this point.
It is a development projet. When you involve process design people instead of developers you end up with unstable bots.
EY2 and 3, good points, fully functional and reliable RPA should involve technical developers, but they are not necessary for simplistic bots, as is not coding.
A viable, Enterprise wide bot should include a cross-functional team, not for building, but for intergrating bots in the Change Management process.
And what do you define as simplistic exactly? Ive seen rpa certified staff write 8 if elseif statments when a do while loop wouldve done the same thing in 1/8 of code lines. Thats a simple fundamental concept for anyone with any programming knowledge.
I dont mean to come off as condescending here, but EY 2 is right there is a serious danger of selling this based on claims of how easy it and all the sudden once xyz consulting firm (more importantly xyz's devs) are out the door the whole intiaive will go real south real quick.
True that. When I first started on my current project I was blown away by the BS my managers and senior managers gave during meetings with the client. They don't even know jack shit about the tools we're using. Everything they knew or understood is from meetings with Junior devs. We need architects to lead.
You're not reliant on coders too much
Because it clicks around on a windows session just like a human would. That said, you would likely need code/config if you want to interact directly with APIs rather than script the process of clicking around.
M1, agreed, coding can be used to enhance RPA, but simplistically bots can be created solely using scripting within the dev platform (AA, BP, etc).
True. But it's dangerous to over simplify RPA. If you don't take it as a real development project you won't be able to scale it and support a large number of bots.