Robot groups for assets / asset sharing

[richarddenton]

Hi guys,

I also potentially like the idea of process specific assets. So for example, rather than having to search through each individual asset you are presented with a grid (ala table) with each of the settings that only apply to that specific process.

@Mihai_Dunareanu For me this could potentially replace the config file direction that we’re moving in which I personally am not a fan of as everything else in RPA / technology seeks to move away from multiple inputs and spread sheets and move more towards databases. This could be segmented into process variables e.g. timeouts etc, assets, etc. Maybe you already had this idea

Also see my suggestion on static queues for a similar line of thought.

Static Tables in Orchestrator

Hello Team, Another idea is to have the option to create static tables in the database. These would act as reference tables and could be used for two different purposes… A Config file for the process - instead of having a separate Excel file - in fact I think that all processes should by default have a config table within Orchestrator A reference table for specific processes, e.g. this table should be something that can be referenced from the process. For example, a list of valid airports tha…

Thoughts?