a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

c2749ac7-173f-4ef9-9842-3f286ebc140b.png

Technical Account Manager II at UiPath

Hi, let me know how to integrate this with Azure Pipeline please.

When using commandline.exe into a devops pipeline how is the ruleconfig.json integrated into this process below. Normally in a on premise machine rulesconfig .json is located within the user profile,... how do we handle this in devops?  Rule.config.json is needed to provide analyzyer with rules to evaluate project.json.  Please give specifics.  Thank You.

The below is the UiPath provided Azure CLI script that has been modified for my devops pipeline.  (Workflow Anaylzer)

    $ProjectFilePath= $(Buildin.SourcesDirectory)\TESTREPO7\project.json

    $ExecutableFilePath= $(Buildin.SourcesDirectory)\TESTREPO7\Studio.zip\Studio\UiPath.Studio.CommandLine.exe

    $OutputFilePath= $(Buildin.SourcesDirectory)\$(Get-Date -Format 'yyyy-MM-dd-HH-mm-ss')-Workflow-Analysis.json

Write-Output "$(Get-Date -Format 'HH:mm:ss') - STARTED - Workflow Analyzer CLI Script"

$Command = "$ExecutableFilePath analyze -p $ProjectFilePath"

Invoke-Expression $Command | Out-File -FilePath $OutputFilePath

Write-Output "$(Get-Date -Format 'HH:mm:ss') - COMPLETED - Workflow Analyzer CLI Script"

Hi Michael - I have the same question as David Kim below. How do we references the rulesconfig.json in the pipeline?

Hi, let me know how to integrate this with Jenkins Pipeline please.

I am new to powershell and tried the commands you mentioned but i am not able to make it work.

PS C:\agent\Configuration> .\Workflow-Analyzer-CLI-Script.ps1 `

>> -ProjectFilePath "C:\agent\Configuration\Azure_Test\project.json" `

>> -ExecutableFilePath "C:\'Program Files (x86)'\UiPath\Studio\UiPath.Studio.CommandLine.exe" `

>> -OutputFilePath .\Workflow-Analysis.json

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:15 char:81

+ ... ãC*¥ÕºJH0ô¨¨•º¶pvrú[vz’=z”J8j€Þßm´¹ÂÐuÝ:„Æè²-\„r8ä­Å’;,„£šhŒ6 ...

+                                                                  ~

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:15 char:93

+ ... ¹ÂÐuÝ:„Æè²-\„r8ä­Å’;,„£šhŒ6Ö'ï„©eý`¡“®’5Å@´NÏ„#$Œì0ÂuvpQ0 ‚#†Þ_¾ ...

+                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Unexpected token '©eý`¡“®’5Å@´NÏ„#$Œì0ÂuvpQ0' in expression or statement.

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:16 char:19

+ ~Üá÷m8[‡¢äç¹,‘SB,Z'îrzCð9‡¥~yÜX9QGÒ×q”í½ÊxîGGßSÞÑ ...

At C:\agent\a¥ZP¯I§ä[½–œ"^ ÇqöPTX|[lyzer-CLI-Script.ps1:17 char:42

+                                          ~

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:23 char:7

+ ‘¿X4‘Fe}jZ+¾6ÝCN±LÍ3˜@ø«”òA:ŸËÊ‡Ëó$Éó¼a(–¡$cê=le¸ÕdDHÇÙÐF” ...

Unexpected token 'Fe' in expression or statement.

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:23 char:9

Unexpected token '}' in expression or statement.

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:23 char:219

+ ... ýšô…°ÚÄ)Á÷¢™Ÿý½äÙäiuä;ŒoŸÜmò`Û”aðbËƒðá®iÂÿãp!ýæžÂà¹Î^ ÿPK

+                                                                          ~

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:24 char:22

+      jWjQ            )      Workflow-Analyzer-CLI-Script-1.4.1/media/ ...

Unexpected token ')' in expression or statement.

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:28 char:114

+ ... "EšZeY–UÙîu:°M¸Ø=w¯:ð:8ëÊqf#*pöº    @ðu‘©Ô®ž¯píùhµÆ]Ž#}b»ÁsÌ¾íù ...

+                                                                 ~

At C:\agent\Configuration\Workflow-Analyzer-CLI-Script.ps1:28 char:147

+ ... öº    @ðu‘©Ô®ž¯píùhµÆ]Ž#}b»ÁsÌ¾íùa‹—BõâÁq»÷AàÑÌ×Ï? 0(8$4,<"2*ÚÀ;& ...

Not all parse errors were reported.  Correct the reported errors and try again.

    + CategoryInfo          : ParserError: (:) [], ParseException

    + FullyQualifiedErrorId : MissingEndParenthesisInExpression

I succeed to execute my powershell script based on your script from Azure DevOps but sometimes I encountered the following error :
Could not load file D:\abc\toto.xaml. Reason: Cannot create unknown type ‘{clr-namespace:LibAbc;assembly=LibAbc}LibAbc_xyz’. It's a custom library shared in the Orchestator.
If I open the project onto my Studio and I only run workflow analyzer, I have the same error. I have to click on repair dependencie onto the one which is in red. And after that, I can run the workflow analyzer. So, I think I need to execute repair dependencie in a command line without Studio but it is possible ? Or do you have any idea ? Thanks for your help.

Thanks for your last answer but I don't need to repair the dependencie each time I open Studio, only the first time but it's not possible to open Studio onto the machines which are performing the analyze from Azure DevOps. Therefore the problem will appear each time a new custom library will be used. So I have to find a NOT manual solution.

467f5a41-3646-4651-8cf1-9ff9b5d8b6f8.zip

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

f3dbddc9-1be9-4dfa-aa99-04e28643c638.gif

db443866-a915-47c6-86d8-ef64d5cbe1d0.png

05c7b06b-8ce4-4cfd-9744-5c4f85d8d9ce.png

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.

Visual Basic

6b4018ce-6b5e-44b7-9748-7c9058cefb21.ps1

2604c9a3-e8c3-440b-be07-9d08e02f7ba0.zip

9402e21e-6cae-4bba-966a-72dc53f01fd0.zip

872e1482-0925-43b8-981a-13cab9041121.zip

c3d3b54e-7400-4a97-9ae0-e3610c7ec0f0.zip

db4629b6-f9da-42e9-8498-75709d7fcda5.zip

Update LICENSE to match UiPath Connect's MIT

Version	Release Date	Download Link
1.4.1	Mon, 16 Nov 2020
v1.4.1 Release Notes: Update LICENSE to match UiPath Connect's MIT Remove Batch tag from component page
1.4.1	Wed, 11 Nov 2020
v1.4.1 Release Notes: Update LICENSE to match UiPath Connect's MIT
1.4.0	Mon, 9 Nov 2020
Latest Release v1.4.0: Update component name Update script Update description Update benefits Update use case Update media Remove old dependency
1.4.0	Fri, 6 Nov 2020
Latest Release v1.4.0: Update component name Update script Update description Update benefits Update use case Update media
1.3.5	Thu, 29 Oct 2020
Latest Release v1.3.5: Update component name Improve description formatting Fix broken links Upload screenshot Update benefits Add use case
1.3.4	Wed, 28 Oct 2020
Latest Release
1.1.0	Tue, 27 Oct 2020
First Release

Workflow Analyzer CLI Script

Workflow Analyzer CLI Script

VMware - Custom Workflow Analyzer Rules…

Reply - Workflow Analyzer Rules Library…