when can config asset use and in which case we can choose orchestrator asset except credential case
In Config we only give the asset name in assets page. And the value from that asset is retrieved.
If you are asking when to use settings tab on config and Assets then settings are used for generally constant values which don’t change. Assets are used where you might see some changes to values based on Environment in which you run or to give the locations of files for dev uat and prod differently
Configuration values that require regular modifications, would be placed in the assets and if you have values that remain constant always go for the config file.
In general, Assets should be used for global variables & constants used by multiple processes, as well as credentials.
It is always good to use orchastrator asset because when you think of scaling your process say from one robot to 10 then it will really so useful and less hectic job for you as all variables are stored in orchastrator.
But problem comes when your process has lots of variable and configurations that case single config file is really helping and making all things sorted
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.