studio
2020.10
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Extensions
- Troubleshooting
OUT OF SUPPORT
Studio User Guide
Last updated Dec 20, 2023
ST-USG-014 - Package Restrictions
Rule ID:
ST-USG-014Scope: Project
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.
Note: 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,
UiPath.Excel.Activities=2.5.3.
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 or 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 or prerelease versions of the UiPath.Excel.Activities package.
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 UiPath.Excel.Activities=2.7.2-beta*.
Examples:
- UiPath.Excel.Activities=2.8.4-*
- UiPath.Excel.Activities>=2.7.2
- UiPath.Excel.Activities=2.7.2
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.
Note: 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.
