I would like to propose the addition of a cloning feature for assets in UiPath Orchestrator. This feature would enable developers to replicate an existing asset and make small modifications, which would save time and minimize errors. It would be particularly beneficial when managing numerous assets that share similar characteristics but have minor differences.
I believe this is already covered using Solutions Management which handles not only assets but the entire automation solution when needing to clone it to another folder or tenant.
Again, Solutions Management should solve this I feel.
If its a queue trigger youâd also need to âcloneâ the queue first aswell.
Obviously there are also time based, but still.
For Development / Testing youâd surely want to copy the entire solution to another folder or tenant, not just a single trigger.
Can I challenge you on why you need so many assets in the folder that contain âsimilarâ information but maybe have different names? Or different names but the same values? It seems odd to me to have that duplication.
If they have a different name and a different value but its âsimilarâ then I dont see how cloning really helps since its not a clone, its just kinda similar and you still need to do the same manual edits that are prone to error.
Solutions Mgmt isnât the end all be all. As I said, this would be useful for development/testing and Iâm not going through Solutions Mgmt to create one trigger, queue, or asset for testing.
For Development / Testing youâd surely want to copy the entire solution to another folder or tenant, not just a single trigger.
To test different settings. To test a different value without losing the original value. This would especially be true for a trigger that has multiple arguments, copy the trigger with the argument values and then change what you need. Then you still have the original.
Would having the ability to copy triggers, assets, and queues be some sort of detriment to you? You donât have to use the feature, and some people would find it useful.