Has anyone come up with naming standards for Assets in Orchestrator? A search on the forums shows posts for variable naming standards, but I am curious if someone has come up with good standards for assets. This is what I thought of using (as examples), but am welcome to suggestions.
Global assets can be used by any process, and once changed would apply to all processes that use them:
Global.HomeOffice.Address (e.g. 123 Main St, Anywhere, USA)
Credentials are, well, credentials, but are named for the application and robot that uses them:
Credential.Robot1.Amazon (Robot1’s credentials to log into the Amazon site)
Process specific assets are only to be used by that particular process, not others:
Proc.AmazonOrder.ItemNumber (AmazonOrder is the process name, ItemNumber is the identifier)
I kind of like this naming because it groups the assets together in the list and you can clearly see the scope, or what is using, the assets.
Anyone else have good naming standards for Assets?