Orchestrator Asset Folders



Hi again,

I’ve been working a bit with Assets on Orchestrator. Even quite quickly, it seems to me that could become quite a extensive and unwieldy list reasonably quickly.

I’m sure the robots are fine with it - but maybe for us humans we could put in a folder-style concept. We could then separate some of our common assets (e.g. I have a html email header & footer), and then have a folder per process (with things like the special system credentials, flags or similar).

No need to use the folder path for the robot to reference the asset (though maybe optionally they could)


Thinking overnight, maybe another option would be allow tagging of assets and filtering by those tags.


The need for better organisation of assets and resources in general will be addressed soon :wink: