For attended robots developed by citizen developers, what are the hardening steps to be performed on the code to make it resilient prior to deploying in UAT/Production?

Attended robots should be built using coding best practices that consider consumption by large groups of users; there will be requirements, design, development, and testing implications to keep in mind when attended robots are built. If citizens build them, such considerations should be enforced using a combination of workflow analyzer rules, code review checklists, and CoE reviews.

1 Like

Thanks @arep and completely agree with the requirements, best practices… But isn’t this a kind of contradiction to the easiness of use speech so broadly spread by UiPath in what concerns to the RPA Citizen Developer product?