-
Source: UiPath Presentation; Scenarios are described good for Unattended/Attended. Citizen Developer just means, that typically Business Users can develop their own processes, also utilizing Unattended/Attended. -
One terminal server for all citizen developers. Deployment looks the same, as for usual developers. Users might use assets or so in Orchestrator, so giving them access to Orchestrator might be imperative… If you want to automate things, you could use Azure DevOps to create a build pipeline and push from stage to stage. The thing is, that you will still have to deal with assets. Especially if you use sensitive ones (passwords etc.) it’s not that easy to do that 100% automatically. Still hoping for UiPath to publish a native CI/CD / Pipeline integration between OR stages. Also, I would recommend to treat the users environment (in this example the terminal server) as Dev and then have a Nonproduction robot as Test. The Nonproduction robot can also run on the same terminal server as the developers do. Connect both stages to one Orchestrator Tenant and Prod Robot to another Tenant.
To describe further, I attached another slide. This setup is based on a Citrix server and different Workers for Dev/Test and Prod.
