Asset tab in Orchestrator

When working with several processes in one tenant there is a huge risk that the Assets tab gets cluttered with a lot of assets.

My suggestion is that it would be great if we could have the choice of using folders to structure the assets by process, besides having all assets in one list.

Yes, there are a possibility to create folders on another level but if I don’t want to separate the processes from each other it would be a better choice to be able to create folders under the Asset tab.

@Nicolas_Lewentorp

This is where you would use tags/labels

cheers

Thanks,
But this “going over the bridge to fetch water”-procedure is way to time consuming for me instead of just using the file explorer-procedure of having a folder structure. I don’t want to enter a bunch of keywords that I later need to use to filter a view which I could just get with 1-2 clicks.

I can appreciate tags/labels in certain setups but unfortunately not for this. It’s just a personal preference I guess.

1 Like

Folders already exist though

You are deciding that you need said bridge because you want to not use folders, but use different, asset only folders… or something.

I can’t see why something like this would be such a big stretch.

Because its redundant?

Organizing per folder seems perfectly adequate.
There is a trade off between functionality and complexity. What you would ask for would add another layer of complexity and management that would offer very little to I think 99% of users.

I feel you are able to simple put these assets into dedicated folders, with their respective processes, but you have a red line that you dont want to split the processes, which creates this tension in you wanting something that I dont think should be made cause of the reasons above.

I see what you are saying, and it’s probably the right way to go. In my mind it’s just getting cluttered if I have say 50 clients and each client has 2-3 or more processes with 5+ assets per.

Whats the problem in each of those being in a folder?

You can also give each client a tenant to further segregate. This of course depends on the licences you have purchased etc, but assuming they each have their own unattended runtimes I don’t think a setup with multiple clients should even have a shared tenant.

If you are sharing an unattended licence across clients then indeed they must be separated by folders, but I don’t see why a folder per business process is a problem, especially when thats how you want to manage the assets.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.