studio
2023.4
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
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
ST-USG-026 - Activity Restrictions
Studio User Guide
Last updated Nov 4, 2024
ST-USG-026 - Activity Restrictions
Rule ID:
ST-USG-026
Scope: Workflow
The rule checks whether any restricted activities are used in the project. Restricted activities are defined by one of the following lists:
- Prohibited Activities - Activities that are not allowed in the project. All activities that are not on this list can be used in the project.
- Allowed Activities - Activities that are allowed in the project. Only the activities that are on this list can be used in the project.
In the Project Settings window, select the Workflow Analyzer tab. Find and select the rule, and then define the restricted activities using either the prohibited activities list or the allowed activities list. When modifying the rule:
- Add the namespaces of the activities (for example
UiPath.Core.Activities.Delete
) separated by comma (,). - You can use the asterisk (\*\) wildcard character at the beginning or at the end of each entry. For example, adding
UiPath.Core.Activities*
to the list of prohibited activities means that no activity with a namespace that starts with UiPath.Core.Activities is allowed. - Do not use the lists concurrently. If both lists are populated, the list of prohibited activities takes precedence.