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

The Workflow Analyzer tool, which is part of versions 2019.10.x and later of UiPath Studio, is used to catch errors and warnings within an automation. As of version 2020.10.x of Studio, the IDE does not have the ability to export the results of the Workflow Analyzer, but the product instead provides an executable to run the analysis via the command line, in which the results can be piped to file

The Workflow Analyzer CLI Script is a PowerShell script used to run Studio's Command Line Executable to analyze an automation and pipe the results to a JSON file. This script can be easily integrated into an automated error/warning check within a DevOps pipeline, without the hassle of opening the Studio application in its entirety

-ProjectFilePath: The path to the project.json or individual workflow (XAML) file to analyze. By default, this value is set to ".\project.json"

-ExecutableFilePath: The path to Studio's Command Line Executable. By default, this value is set to "C:\'Program Files (x86)'\UiPath\Studio\UiPath.Studio.CommandLine.exe", which is the executable's location if Studio was installed in Service Mode. The value should instead be pointed to "%LocalAppData%\UiPath\[Studio_version]\UiPath.Studio.CommandLine.exe" if Studio was installed in User Mode, replacing [Studio_version] with the actual name of the version folder in that path

-OutputFilePath: The path where the results of Workflow Analyzer should be piped. By default, this value is set to ".\$(Get-Date -Format 'yyyy-MM-dd-HH-mm-ss')-Workflow-Analysis.json"

1) Open a PowerShell session as Administrator

2) Optionally run the following to allow the current session to run scripts not digitally signed:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

3) For example, running the following from the same directory where Workflow-Analyzer-CLI-Script.ps1 is will analyze C:\Date-Reminder\src\project.json, point to the default location for a Service Mode Studio's Command Line Executable, and pipe the results to .\Workflow-Analysis.json:

.\Workflow-Analyzer-CLI-Script.ps1 `
  -ProjectFilePath "C:\Date-Reminder\src\project.json" `
  -ExecutableFilePath "C:\'Program Files (x86)'\UiPath\Studio\UiPath.Studio.CommandLine.exe" `
  -OutputFilePath .\Workflow-Analysis.json

Run UiPath Studio's Workflow Analyzer via command line and pipe results to file

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Workflow Analyzer CLI Script

Workflow Analyzer CLI Script

Help

How To