We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a 500,000-strong developer community, and 5MM+ robots at work in over 5,000 global enterprises.

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

Guaranteeing the quality of workflows in an RPA implementation project can directly impact its success. Although experienced developers and practices like peer reviewing can improve the quality of workflows created, having an automated way to inspect many XAML files can be helpful to do a preliminary automatic evaluation.

This creates the need for a tool that can aid RPA Developers and Solution Architects in the process of workflow review, checking whether most commonly used development best practices are being followed.

In addition, since development conventions vary with each implementation project, it is essential that users of the this tool can easily understand it, and that the tool itself can be more easily extended to meet the necessities and standards of each implementation.

The Workflow Inspector addresses the mentioned needs by having the following characteristics:

It is offered as a regular UiPath Studio project, making it easy for users to understand and make modifications without having to learn a different programming language or tool.

It uses an Excel file to specify checks to be done and their configurations. This file also contains explanations about checks and suggestions for improvements, contributing to the education of developers in an RPA implementation.

It traverses the structure of XAML files by using XPath expressions, which is a standard to query XML and XAML documents. This provides the necessary flexibility to adapt the tool to specific needs of an implementation.

Currently, reports can be generate in English, Japanese and Korean.

A tool for evaluating UiPath Studio projects according to the best practices of workflow development.

Product Manager

Visual Basic

How can I download this to test?. I dont see the download option on the screen

How can i edit the core for example I want to change the default variable inspector ni camelcase instead of pascalcase and in arguments, i want to change it from having In/Out_ to PascalCase only?

Hello,With the creation of Workflow Analyzer, do you think you will pursue development on this project?I really like Workflow analyzer for the direct feedback to developer but I think in the other end this tool can help in CI/CD implementation.Maybe convergence of both solution to have the ability to customize, improve and the direct feedback + possibility to be called as part of a CICD.

Hello,Did you consider adding check of descriptive names of activities - using regex pattern? Similar to checking variables/arguments naming convention. Quite often default names of activities (click, type into, get value) that cooperate with SAP GUI or other apps are very non-descriptive - containing special strings like [ { ' etc.

I just came up with one more the idea of checking whether the arguments passed from a higher workflow match the arguments passed down to inner one (avoiding the error 'The values provided for the root activity's arguments did not satisfy the root activity's requirements')

Hi, I wanted the Variable naming convention in camel case. Where i have to make changes ?To be more specific, we are following this naming convention - "datatypeVariableName" example - dtInputData, strCustomerName, intRowCounter ...etcCan we include this in naming convention check ?Thanks in advance.

Hi! Would there be any additions you would make to this since this feature is in Studio?

Recently Workflow Analyzer has found 2 Errors and 707 Warnings inside Workflow Inspector project. Challenge accepted? :)

How can I help you with Workfliw Inspector? I really interested in solution like that and I want to contribute to community.

Why should I use "Workflow Inspector" instead of Workflow Analyzer? Workflow Analyzer is build-in feature, easy to use and configure. What is the usage scenario of this project? 

Can i use this to non reframework projects?

I had a prompt on the changes. What are the newly applied changes/enhancements?

Finally - Really needed. I love it. I'm really eager how will this evolve.
I would loved it even more if it was not uipath code (because license consuming), because there are a lot of robots to check here :v
Congratulations.
Thank you.


Much needed - Great, this will certainly help to reduce the QA overhead. Will try it out to post comments


Like it - Great thanks for Japanese localization at a first release.
I was creating same ideas a bit.
I will review the rules and use them.
I'd like to customize it after checking that it automatically changes the activity name to an independent name.


Fantastic innovation - As a product owner I often have to review code.  This is a tedious process if one wants to maintain best practice standards.  Also it results in code being sent back and forth quite a bit.  This solution allows the developers to make sure they adhere to the best practices before the code is sent to me for review.  This allows me to rather concentrate on the efficiency and operational ability of the automation, than to get stuck on best practice reviews.  The way it is built makes it modular and that is great as well.
It also has the consequence of our developers starting to code with best practices in mind as they know they will have to just fix it later anyway.


素晴らしいアイデアです。 - クリティカルな不具合検出のパターンは少ないものの、ベストプラクティスのコーディング規約のチェックとしては、標準のものでも非常に効果があります。過去UiPathフォーラムでもトピックスになっていた変数名と引数名の同名チェック手段も解決でき、バックグラウンドで動作させるためのデフォルトのクリック有無のチェックも時間の節約になります。企業の独自規約に応じて、チェック内容の拡張を作りこめる点も素晴らしい。


 - This tool really reduced my work and does a wow job.


 - The workflow is well thought out and design. Documentation is easy to understand. So I manage to extend checks for bot name in project.json. Thank you.


 - Works like charm (sorry about my previous question - now deleted - , it slipped to wrong project as I was hoarding several of them while at it...)


 - I started using it recently, I think it's incredibly useful and flexible, and it saves a lot of time when doing QA reviews.




 - Well designed and implemented tool. Works great! Highly recommended!


 - Great design. Very helpful for code review.


 - Easy to use, reliable, well done, thank you!


 - Hello,
can you check the documentation links? It seems that the download are not available at this moment.
Thanks in advance.


Amazing tool, and glad a version of it is now officially implemented within Studio!

Very useful and practical! This component is used in review process of my company now.

Reviewing workflows are the most challenging task. Thanks for making our life easy :)
This is one of the best components I have come across so far.

It made checking the workflow easier. Thank you very much. I like that it can be used as another tool if you customize it.

Workflow Inspector

Workflow Inspector

Help

How To