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-025 - Saved Value Misuse
Studio User Guide
Last updated Nov 4, 2024
ST-USG-025 - Saved Value Misuse
Rule ID:
ST-USG-025
Scope: Workflow
Note:
- This rule was introduced in UiPath.System.Activities v20.4 and only applies to projects created in the StudioX profile.
- This rule does not apply to projects that use UiPath.System.Activities v22.4 and newer.
The rule checks for variables that are used as input in activities placed before the activity where the variables are saved.