Hi All ,
i am aware “Add log fields” activity is the one which is responsible to add new fields to logs . it takes collection as inputs. but the value for this is given static way , How about passing some collection as arguments so that today 12 fields of logs can be added and tomorrow 20 fields can be added. in this way we can avoid touching the code for just adding a new log field . rather have a place in config file where these field names are added.
Hi All ,
Yah that’s possible
We can use List kind of variable to take in different set of values in the collection variable
But I would suggest to keep always the same because when we run once and look for a log in the details tab in orchestrator m, we might expect for the same in later testing and if we change the log field it won’t be a robust way to handle to the logs and it’s information
well its as much same as config file. unless no one changes its difficult. there are valid reasons to do in this way.
one : the way the KPIs are defined are unpredictable especially time saved by the bot . some times this time saved is split in to various categories . (after the bot development) .
two : obvious reason , “please include one more field” .(after the bot development)!
thanks @Palaniyappan for the input .
Hi, do anyone have a solution for how this could be achieved? I have a json object that I want to loop through and use AddLogFields for each pair found, but I have not found a way on how I can use the key value as the name of the log field.
What I want is to use the item.Name as the log fields name, so I need to find a way to reference to this variable rather then it ending up like this
hi, did you find any solution to this, your case sounds exactly same as the one we face, and for same reason we are looking for a solution aswell…