I’ve been lurking for a while on this forum, and have my first question. We are about to use UiPath to apply RPA in our organization, and I was wondering about best practices when it comes to adding comments/annotations to the source files. These are robots that will be running for years and will need to be maintained by various people.
Quote: “Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.”
I have a programming background, and one of my main points of frustration with UiPath is readability. A robot consisting of many different .xaml files with dozens of variables and activities quickly becomes a visual mess and if you want to figure out what’s actually going on, you have to dig into the activities. If you’re not the original developer, this can be pretty rough. And even if you are, it can still be rough if you haven’t looked at it for months.
Other than obvious naming conventions, I thought about using annotations to describe the process in layman’s terms, especially with the Flow Decision and Invoke Workflow activities. I don’t like the Comment activity, because it increases visual clutter even more.
How do you guys handle this? Does anyone have any other ideas to improve readability? It doesn’t matter much for the small robots you create during your trainings, but when automating enterprise processes with dozens of variables and activities it can be quite daunting.