We do not currently use bot labels (Assign label to a bot).

As a bot developer in a controlled corporate environment, I do not have the ability to experiment with this feature.

However, after reading the documentation, I believe that bot labels may be able to solve an issue we experience and I am looking for advice and expertise from those who use bot labels.

The problem: we have a standard bot development cycle which goes from Dev to UAT to Prod environments. In the UAT environment we perform the majority of testing over test data. However, we often run bots over production data in UAT as a final step before promoting to Prod. Due to the fact that UAT uniquely runs over both production and test data, our config file (which stores the “test = TRUE/FALSE” variable) has to be updated via tedious promotion several times.

The Possible Solution: after reading about bot labels, I now suspect that instead of having to promote a brand new config file from Test to UAT every time we need to switch the data sources, that we could just create a TEST and a PROD label for the two different versions of the config file living in the UAT repository. So (with my limited understanding), in theory, when we need to run a bot in UAT over test data, we could simply select the TEST label at run time and the bot will use the config with test flag = TRUE. Vice versa for production data.

For those with experience, can you please let me know if this would work and where I might be off base?