Contact Us

We’re here to help!

Please contact us in case of any query. We are happy to help.


Our Email  jugszygomatic@gmail.com

Comments

Post a Comment

Popular posts from this blog

UiPath Code Review Checklist – To Perform Effective RPA Code Reviews

Image
  Perform Effective RPA Code Reviews Code Review is improving general code quality and reducing the number of bugs by sharing the knowledge of the author and reviewers . Code review can be treated as a checklist in which developers submit their code for feedback before merging branches or deploying code to production. The feedback is usually given by a manager, or a tech lead. ____________________________________________ Workflow Analyzer   Workflow Analyzer  is a static code analyzer that ensures your project meets high quality and reliability standards. A static code analyzer checks for inconsistencies without executing the project, as opposed to dynamic analyzers which step in during execution.   ____________________________________________ Code Review Checklist for UiPath Code Reviewer The Code Review process, like any other process, can use some rules, for complex projects. So, it is the best p...
Read more

What is Debugging in UiPath?

Image
  Debugging Debugging is the process of identifying and removing the errors which prevent the project from functioning correctly. In Studio, debugging is   _________________ Troubleshoot, Debug, and Modify processes The Debug tool in UiPath Studio is a real-time engine that checks for errors while working with the workflow. Whenever an activity has errors, UiPath Studio Process Designer notifies and gives details about the issues encountered. _________________ Debugging Actions _________________   Setting Breakpoints
Read more

What is Logging in UiPath?

Image
    Logging Logging is the process of keeping logs of various events that occur during project execution. There are three types of logs: _________________ How to do logging? Logs are applied using the Log Message activity.   _________________ Logging Log message activities should ideally be used: •        At the beginning and the end of every workflow (Log level = Information) •        Each time an exception is caught in a Catch block (Log level = Error) •        Each time a Business Rule Exception is thrown (Log Level = Error) •        When data is read from external sources (for example, log a message at Information level when an Excel file is read) •        In Parallel or Pick activities, log messages on every branch, to trace the branch taken (Log Level = Information...
Read more