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 actually executing the project, as opposed to dynamic analyzers which step in during execution.
Workflow Analyzer uses a set of rules to check for various inconsistencies unrelated to project execution. The rules are based on Automation Best Practices and take into consideration variable and argument naming, empty sequences or workflows, package restrictions, and so on. The analyzer does not identify errors in execution or compilation.
It is available in the Design ribbon tab, the Analyze File and Analyze Project buttons. The first performs an analysis on the file currently focused in the Designer panel, while the second analyzes all files in the automation project.
Studio built-in rules cannot be ported to older Studio versions. However, rules from compatible activities packages can be used in older Studio versions that come with the Workflow Analyzer.
Each rule has an ID, name, description, and recommendation. The ID contains the origin, category, and number. For example, Variables Naming Convention has the
ST- reveals that the rule is built into Studio.
NMG- shows that the rule is part of the Naming Rules category. Rules part of Project Anatomy Rules category have the
ANAabbreviation, those part of Design Best Practices the
DBP, and so on.
001- is the rule number.
The project or file is analyzed based on a set of rules available in the Project Settings window:
- In the Project panel, click the icon, then select Workflow Analyzer.
- In the ribbon, click the Analyze File button, then select Workflow Analyzer Settings from the dropdown.
Rules can be filtered by scope and action. Uncheck the box next to each rule to define a configuration specific to your project. By default, rules are arranged by code in the window, and enabled rules are displayed first.
Each rule has a scope to which it applies:
- Activity: The rules are enforced at activity level, checking variables, arguments, properties. Variables Naming Convention is one such rule.
- Workflow: Rules perform checks in a single project file, for example Unused Variables.
- Project: Checks are performed at project level.
Rules have a number of actions that can be set:
- Error: Generates an error in the Error List panel.
- Warning: Generates a warning in the Error List panel.
- Info: Generates a message in the Error List panel.
- Verbose: Creates large log files.
Check the Logging Levels page to learn more about logging with Studio.
After any changes were made to the default values of rules, be it Regex or thresholds, the values may be reverted to default by right-clicking the rule and then selecting Reset to Default.
Validation of the file or project is performed whenever the Workflow Analyzer is triggered. Validation options are available in the Analyze File ribbon button, Validate File and Validate Project.
This action checks whether variables, arguments, expressions, and imports are properly configured. The Validate File action can be triggered using the F8 shortcut, while Validate Project using Shift + F8. Validation can be cancelled at any time.
The file(s) that contain errors are marked in the Project panel with a red dot, and the errors are shown in the Error List and Output panels.
Double-clicking an item in the Error List panel opens the
.xaml and highlights the element which threw the error, whether it's an activity, argument, or variable.
.xaml files are validated, the project cannot be debugged, executed or published. Breakpoint conditions are not evaluated.
When triggered, the Workflow Analyzer uses the configured ruleset to check the project or file, and logs the found errors in the Error List panel, in accordance with the rule action.
The Error List panel filters items by Errors, Warnings and Messages. The scope drop-down menu is useful for filtering errors by project, current file or a specific file in the automation. In addition, items can be filtered by rule ID.
Click a found warning or error to display the rule’s recommendation and a link to the documentation page for each rule.
In addition to rule violations, the Error List panel also displays errors that may occur in the execution of workflow analysis, When the Workflow Analyzer or one of the configured rules fails to run, an error is logged with details about the cause of the error in the description.
UiPath.Studio.CommandLine.exe command-line user interface contains a set of parameters for checking files or projects against certain rules, even in CI/CD pipeline configurations.
UiPath.Studio.CommandLine.exe is available in the installation folder:
- For the Windows Installer (.msi) version of Studio, the default path is
C:\Program Files (x86)\UiPath\Studio\
- For Studio installed in User Mode (.exe), the default path is
By default, Workflow Analyzer rules are enabled when installing Studio, except for Argument Default Values. Configure rules directly from Studio:
- From the Workflow Analyzer Settings window, enable or disable rules by clicking the checkbox next to each one of them,
- From the
%LocalAppData%\UiPath\Rules. Find a specific rule, modify its parameter, change the
falseto disable the rule.
Rules are organized according to their unique ID, visible in the Workflow Analyzer Settings also.
For example, in the image below only the Variables Naming Convention rule was enabled and received the
([A-Z]) Regex expression. This means that variable names must be uppercase. All the other rules were disabled in this example.
After configuring the rules, access the
UiPath.Studio.CommandLine.exe command-line user interface.
Workflow Analyzer commands are the following:
analyze- Analyzes the whole project. Requires the path to the
analyze-file- Analyzes a single file. Requires the path to the
For example, the command
UiPath.Studio.CommandLine.exe analyze-file -p "C:\BlankProcess\Main.xaml" analyzes only one file in a project,
Main.xaml. The output of the command returns a json-encoded dictionary with the following information for each rule violation:
FilePath: The path to the analyzed file.
ErrorCode: The rule ID.
ActivityDisplayName: The display name of the activity (
nullif not applicable).
Item- The name and type of the item (for example, activity or variable) where the error message was generated.
ErrorSeverity: The value of the
DefaultActionparameter, which is the configured log message for each rule, either Warning, Error, Info or Verbose.
Description: The rule's description.
URL: The recommended changes for solving the issue, together with the documentation link with more information.
To return the exit code of the command, execute
echo %errorlevel% after you run it. If there are no messages with the
ErrorSeverity Error, the code
0 is returned. Otherwise,
1 is returned.
Please note that some of the entries may not be associated with a rule, but can be errors generated by the Workflow Analyzer. For example, in the case of an empty
.xaml` file, an error is displayed.
The Globally Unique Identifiers (GUID) used as prefixes for an entry are generated on each run and apply to the current result only.
The execution and publishing of projects with Workflow Analyzer errors can be prohibited using the options Enforce Analyzer before Publish and Enforce Analyzer before Run from Studio Backstage View > Settings > Design. The Workflow Analyzer is triggered every time you perform the action for which the option is enabled (publish or run/debug) and the action is allowed only if there are no rule violations with the action
When the option is enabled for publishing, the results of the workflow analysis are included in the published
.nupkg package in the file
project_analysis_results.json located in
\lib\net45\.analysis\. The file contains the following information about each enabled rule that was checked during the analysis:
RuleId- The rule ID.
RuleName- The name of the rule.
Parameters- The customizable parameters in the rule, if applicable.
ErrorsDescription- A list of error messages generated by the rule, if applicable.
Updated 8 days ago
|Building Custom Rules|
|Project Anatomy Rules|
|Design Best Practices|
|Maintainability and Readability Rules|
|Performance and Reusability Rules|
|UI Automation Rules|