Need option to Export Workflow Analyzer Results

Feedback Studio
, , , ,
#1

Regarding Workflow Analyzer in Studio: It would be good if we have option to export “Analyze Project/File” results to xls/csv file.

This will be use full when multiple team members are working on project and tech lead have to do code review and assign observations/violations to team members.

Count of all activities use in a project
#2

Hi,
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.

5 Likes
#4

I also have the same thought as Kuldip.gohil.
My company wants to show customers analyzer result in excel.

#5

Any updates on this capability? What about exporting the configurations for the workflow analyzer across developers?

#6

Hi. This case is still under review.

2 Likes
#7

For anyone who needs a temporary workaround, please use the command line version of Workflow Analyzer.

Analyze a single file:
“C:\Program Files (x86)\UiPath\Studio\UiPath.Studio.CommandLine.exe” analyze-file -p “c:\UiPath\Test Process\Main.xaml” > c:\temp\results-Main.json

Analyze an entire project:
“C:\Program Files (x86)\UiPath\Studio\UiPath.Studio.CommandLine.exe” analyze -p “c:\UiPath\Test Process\project.json” > c:\temp\results-Test_Processs.json.

Thanks

3 Likes
#8

Hi Krishtopher,

I am using commandline window for Workflow analyzer execution. But it is not giving any results.

image
image1366×768 61 KB
.any idea?

#9

Hi @shalini23,

Can you validate the paths are correct for the files please?

Unfortunately the executable does not produce an error when it cannot find the file to analyze.

Can you go to c:\users\svcFLNACICDADM\Documents\UiPath\RoboticEnterpriseFramework and issue a command dir to see if the path is correct / the files are found please?

Thanks

image001.png

image002.png

image003.jpg

#10

Hi Kristopher,

Thanks for the immediate response. PFB screenshot of command DIR. It is listing down all the files and folders in that path.

image
image1366×768 74 KB

#11

Hi @shalini23,

This is odd behavior. Can you create a brand new project and put the new project’s folder with the project.json and Main.xaml onto the base of the C drive and then try to run the command again?
e.g. c:\project1

Thanks

#12

Isn’t it because you are forcing a file output “C:\Program Files (x86)\UiPath\Studio\UiPath.Studio.CommandLine.exe” analyze -p “c:\UiPath\Test Process\project.json” > c:\temp\results-Test_Processs.json.

However i guess it of course should provide the results in the command-line but could be that it would work if using that. I can’t see that @shalini23 is generating any output file.

#13

Hi Kristopher & Sonnymeyer

Thank you so much . Now it is working I just changed folder path and i have tried.

Do you have any idea regarding custom code rule implementation in uipath using Visual studio?

#14

Hi @shalini23,
Why don’t you check our documentation? Everything is there :slight_smile:

Watch the video attached where one of UiPath member is showing live how to build a rule :wink:

1 Like
#15

I am sure that the video is very good, but the upload quality is terrible.
Nobody can read or watch that video and see the code itself.
Is it possible to get access to a high quality version?

YouTubeScreen
YouTubeScreen1920×1079 113 KB

YouTubeScreen2
YouTubeScreen21090×478 32.2 KB

#16

No Matter, I found it here :

This version is very watchable and good res.

Could you possibly embed this version into Building Custom Rules as a replacement for the existing video?

#17

Hi @kuldip.gohil,

I agree with you on this. It would be helpful for reviewers to have a look at the analyzer results standalone without having to depend on user to showcase the errors produced.

Thank you for bringing this up.

Regards
Sonali

1 Like
#18

I have created an executable to export the results. I am awaiting my Marketplace posting to be approved. Once approved I will link it here.

1 Like
#19

@Robert_Schneider,

Great to hear that :slight_smile:

Regards
Sonali

#20

Hi, Did you find a way to export workflow analyzer settings across developers?

#21

Yes, this can be done via cmd line. I am awaiting the marketplace to publish my exe for this purpose.

Below is the back end powershell used to export it. You could run this while the exe is being reviewed.

#############################################################################################################

NAME: UiPath_Analyzer_2020_10.ps1

AUTHOR: Schneider, Robert

DATE: 09/16/2021

This script allows user to select correct project.json file for uipath analyzer output

VERSION HISTORY:

1.0 Initial Version

2.0 Updates for resiliency and exe

#############################################################################################################
try{
###########################
#Setting Variables #
###########################
$PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent #set the current path of the script
$continue = “Yes”
$useroutput = $null
$outputpath = $null
$projectjson2 = $null
$param = $null
$par = $null
$output = $null
$error.Clear()

##########################
#CHecking User Session #
##########################

$wshell = New-Object -ComObject Wscript.Shell
$wshell.Popup(“PLEASE SELECT THE UIPATH PROJECT.JSON FILE”,0,"")|Out-Null

Add-Type -AssemblyName System.Windows.Forms
$FileBrowser = New-Object System.Windows.Forms.OpenFileDialog -Property @{
Multiselect = $false # Multiple files can be chosen
Filter = ‘UiPath Project.json (.json)|.json’ # Specified file types
}

[void]$FileBrowser.ShowDialog()

$projectjson = $FileBrowser.FileName

if ([string]::IsNullOrEmpty($projectjson) -eq $true) {

$wshell = New-Object -ComObject Wscript.Shell

$wshell.Popup(“YOU DID NOT SELECT A UIPATH PROJECT.JSON FILE. PLEASE TRY AGAIN.”,0,“Error”)|Out-Null
exit
}

Add-Type -AssemblyName Microsoft.VisualBasic
$usecase = [Microsoft.VisualBasic.Interaction]::InputBox(“Enter Use Case Name”, “Use Case Name”, “”)
if([string]::IsNullOrEmpty($usecase) -eq $true)
{$wshell.Popup(“YOU DID NOT ENTER A NAME. PLEASE TRY AGAIN.”,0,“Error”)|Out-Null #writing error message to user popup window
exit
}

If ((Test-Path ‘C:\Program Files\UiPath\Studio\UiPath.Studio.CommandLine.exe’) -eq $true){
$path = ‘C:\Program Files\UiPath\Studio\UiPath.Studio.CommandLine.exe’

$outputpath = “C:\users$env:USERNAME\Desktop”+$usecase+“Analyzer”+(Get-Date -Format MM_dd_yy_hh_mm_ss)+".txt"
$projectjson2 = ‘"’+"-p $projectjson"+’"’
$param = “,analyze,$projectjson2”
$par = $param.Split(",")
$output = & $path $par

$outputclean = ($output.Replace(’#json’,"").Replace(’"’,"").replace(’{’,’’).replace(’}’,’’) -Replace ‘.*FilePath’,’, , , ,FilePath’).split(’,’)
$outputclean |Out-File $outputpath
}

If ((Test-Path ‘C:\Program Files (x86)\UiPath\Studio\UiPath.Studio.CommandLine.exe’) -eq $true){

$path = ‘C:\Program Files (x86)\UiPath\Studio\UiPath.Studio.CommandLine.exe’

$outputpath = “C:\users$env:USERNAME\Desktop”+$usecase+“Analyzer”+(Get-Date -Format MM_dd_yy_hh_mm_ss)+".txt"
$projectjson2 = ‘"’+"-p $projectjson"+’"’
$param = “,analyze,$projectjson2”
$par = $param.Split(",")
$output = & $path $par

$outputclean = ($output.Replace(’#json’,"").Replace(’"’,"").replace(’{’,’’).replace(’}’,’’) -Replace ‘.*FilePath’,’, , , ,FilePath’).split(’,’)
$outputclean |Out-File $outputpath

}

Add-Type -AssemblyName PresentationCore,PresentationFramework
$PopUp = [System.Windows.MessageBox]::Show("$error",“Results”,0,0)

}

catch{
Add-Type -AssemblyName PresentationCore,PresentationFramework
$Error_Check = [System.Windows.MessageBox]::Show(“Do you want to view errors?”,“Error Report”,4,0)

if($error_check -eq “Yes”)
{
$date = Get-Date -Format “mmddyyhhss”
$error | export-csv C:\Users$env:USERNAME\Desktop\Error_$Date.csv
Add-Type -AssemblyName PresentationCore,PresentationFramework
$Error_Output = [System.Windows.MessageBox]::Show(“Errors have been exported to: C:\Users$env:USERNAME\Desktop\Error_$Date.csv”,“Error Report”,0,0)
}
}

2 Likes