Solved

Do you have any standard for naming variables, and logging in RPA tasks?


Userlevel 3
Badge +10

What could be the best way for naming and logging?

Is logging the errors in txt file and sending email enough, or should take a screenshot or anything else?

Some people say it’s best way to have a report for the task details like powerBi, instead of looking at error mails.

What do you think?

also how do you name variables, string-integer-list-datetime-boolean etc

icon

Best answer by Raul Jaimes 31 May 2023, 11:23

View original

5 replies

Userlevel 5
Badge +9

@Semih 3318 

Kindly check the following links:

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/aae-client/bot-creator/developer-recommendations/cloud-build-reusable-bots.html

 

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/aae-client/bot-creator/using-variables/cloud-user-local-variables.html

 

Regards

Userlevel 3
Badge +10

@Raul Jaimes thank you for your reply,

I will check them

Userlevel 2
Badge +8

We standardized our logging after a long discussion with all our developers. We created a logging taskbot that requires certain params that are fed into the logging taskbot. Things like bot name, task name, bot runner, user, message etc.

Everyone uses the same logging taskbot now and all our logs have the same format. We even added a couple of other taskbots that control how often a log file is created for each bot (daily, weekly, monthly etc.) and a naming convention for the log files.  Those tasks are run at the beginning of each bot and new log files are created if necessary or the BOT may continue to log to an existing file.

Userlevel 3
Badge +10

@JMarino thank you, that sounds great.So you created a general taskbot and use it in the beginning of every bot.

Userlevel 2
Badge +8

@JMarino thank you, that sounds great.So you created a general taskbot and use it in the beginning of every bot.

Yes, we have a taskbot that takes variables (Bot name, log folder, log freq...) and creates a new log file at the start of all our BOTs. Then we have a standardized logging taskbot that we use throughout every BOT for logging. We even added logging levels controlled by a credential (level 1, 2, 3) so we can increase or decrease the amount of logging. Every time we call the logging taskbot, we pass in the credential vault variable and the level of logging for that item and if the level in credential vault is higher than the logging level for that log line, it logs. This way we can get more verbose logging when needed for debugging but we can dial it back to minimal logging when all is well.

Reply