The rule allows restricting the use of activity packages in a given project. After the list of prohibited packages is defined, the rule checks the project to determine if any were added as dependencies. By default, if any prohibited package has been installed in the project, the rule logs an error in the Error List panel.
Default activities built-in Studio cannot be excluded using this rule, as they do not belong to a specific package.
Make sure no packages that are prohibited by your organization are installed in your project. Such packages may be excluded based on their name or version.
In the Project Settings window, select the Workflow Analyzer tab. Find the rule and select the rule, as in the image below:
By default, this rule does not prohibit any activity packages. Add a package by writing its full name together with its version separated by the equals sign (=), for example,
Add the greater than (>) symbol to restrict higher versions, for example,
UiPath.Excel.Activities>=2.5.3 would restrict all 'UiPath.Excel.Activities' packages having a version of 2.5.3 or higher. The greater than (>) symbol can only be used together with the equals sign (=), inputs such as
UiPath.Excel.Activities>2.5.3 are invalid.
The less than (<) and the less than or equals (<=) symbols are not supported, therefore inputs such as
UiPath.Excel.Activities<=2.5.3 are considered invalid.
Use a wildcard character
* to restrict multiple versions of the same package. For example, the
UiPath.Excel.Activities=2.7.2-beta* value prohibits all beta versions
2.7.2-beta of the
UiPath.Excel.Activities=2.7.2 package, while allowing the usage of other versions of the same package, including
UiPath.Excel.Activities=2.7.2, any other prerelease versions of the
UiPath.Excel.Activities=2.7.2 package (like alpha versions), or any other stable of prerelease versions of the
The wildcard character
* can only be used at the end of the version. Furthermore, when using the greater than or equals (>=) symbol together with a wildcard character
*, the greater than symbol (>=) is interpreted as the equals sign (=), for example,
UiPath.Excel.Activities>=2.7.2-beta* is a valid input, but is interpreted as
The rule does not identify restricted packages if a wildcard is used in a prelease version number, for example,
UiPath.Excel.Activities=2.8.2-beta.10*. The rule also doesn't restrict packages when using a wildcard in a major version number, for example,
UiPath.System.Activities=1* does not identify
To restrict multiple packages, simply separate them by a comma, for example,
UiPath.Excel.Activities, UiPath.UIAutomation.Activities excludes all versions of these two packages.
To check which package an activity belongs to, use the Group by Packages option in the Activities panel, as explained here. Another easy way to check is to hover over an activity in the panel and read the tooltip.
After adding packages to the rule, use the Analyze Project button to try out the rule.
By default, the rule does not prohibit any packages. However, if you wish to quickly remove the packages that you've added, right-click the rule in the Project Settings window, and then click Reset to default.
The Default action is also reset to its default value Error.
Updated 28 days ago