Hello UiPath
I would like you all to consider giving the users more control about how to deploy solutions into folders than they have now.
For our specific usecase, having each solution in each their own folder is already a little bit of a hazzle, but forcefully creating a environment subfolder when best practice is to divide environments into different tenants for CI/CD purposes makes the subfolder seem pointless.
Pls check below link, might be helpful,
I have already read this documentation. It does not even mention the behaviour that i’m describing. It merely mentions the selection of parent folders and naming of newly created deployment folder.
If i overlooked something i would love to have it pointed out.
1 Like
Could you please share a sample folder structure that you’d like to have when working with solutions?
Hi @loginerror
We would just like to be able to deploy directly to a shared folder where we host all of our production solutions. Since we dont use insights, having everything running in one folder makes it very easy to get an overview of our production environments operational status.
The default UiPath implementation forces the folder structure to be
[Selected Folder]
[RPA Process Name]
[Environment]
As stated, we would ideally just have everything in [selected folder].
I would also suggest to if nothing else remove the [environment] subfolder, since UiPath’s best practices suggests running different environments in different tenants, the environment subfolder will never have relevance imho.
I suspect the reason UiPath forces the subfolder structure is to make future removal of deployed processes easier, since it can simply delete the folder and all its contents instead of unstaging the related assets/queues/processes/etc.