Hi, I have a question on how UiPath deals with software updates. In the age of frequent and often forced software updates such as Windows 10, Office updates, and SaaS applications causing UI to change almost as frequently, how does UiPath deal with this? I would assume that recording of each activity can be broken down such that just one step can be edited later to reflect the changes? Main concern is if an unavoidable change causes any of the recorded steps to fail, how easy it is for the user to take action and fix it?
How does UiPath deal with software updates such as Windows 10, Office updates and SaaS applications?
Its pretty easy.
Have you had a look at what UiPath looks like? think of it as a process flow, so with proper naming conventions and organisation of your ‘process flow’ you will be able to identify any issues quickly with UI changes etc.
Generally I’ve found most ‘big’ (office) applications use hotkeys which don’t change from iteration to iteration, so you have the ability to automate using hotkeys instead of by clicking through.
Think of it as if your staff upgraded from office 2010 to office 365, a few changes, not major but they have to relearn small portions. Its the same with UiPath.
You have the ability to ‘invoke’ workflows within your main workflow, what this means is, if you have reusable actions that are the same between different projects you can almost copy and paste these into other projects. So instead of updating 100 different files with the UI changes, you only need to update 1.
I hope I’ve made sense, I tend to ramble.
2 Likes
Thank you so much for your response and information. Your answer has made perfect sense and had really helped me understand 
Yoichi
Raja.G
mkt.scott4