User:GRPA Automation

BEST PRACTICES AND STANDARDS Standards are a set of guidelines and best practices that developers follow while writing code. These standards cover various aspects such as naming conventions, code organization, indentation, commenting, error handling, and more. Consider coding standards as rules, techniques, and best practices to develop cleaner, more readable, and more efficient code with minimal or no error.

• Set work queue retry to 3 times • Set Encryption Enabled to True while defining workqueue • Set Transaction count through environment variable. This will enable the team to handle the case

   execution number at runtime

• Inflight transaction should be part of both dispatcher and worker • Use send keys and region mode only where other methods are not possible • Downloaded files or manipulate the file to your local folder first and then move to shared drive • Validate Edge and Chrome version. Recommended Edge version is 111.0.1661.54 and Chrome version

   is 117.0.5938.150

• No hard code values - all values should come through GRPA config file only • Use retry logic wherever applicable • Exceptions are categorized only as System or Business Exception • Follow the naming conventions for Process and Object Design , Data item, Spy Item • No business logic should be implemented at object level • Share the list of reusable objects for SAP with Anjali and Venkata • File naming convention should be followed while working on templates, standard naming is

   BOTID-Division_Department_ProjectName_FileType 

• Deployment Checklist file naming convention is

   BOTID-Division_Department_ProjectName_MMDDYYYY_DeploymentChecklist.docx