studio
2022.10
false
Studio User Guide
- 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
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Control Flow
- Object Repository
- Logging
- The ScreenScrapeJavaSupport Tool
- Studio testing
- 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
Importante :
A localização de um conteúdo recém-publicado pode levar de 1 a 2 semanas para ficar disponível.
Release date: 6 April 2023
Known issues
Using breakpoints and Step Into when debugging a Windows - Legacy workflow that contains a Type Into activity inside a Use Application/Browser activity does not work as expected.
Bug fixes
- Further improvements were made to a fix for higher than expected memory consumption when multiple interdependent libraries were installed in a project.
- Working with Profile Execution and Activity Coverage wasn’t possible in Windows - Legacy projects.
Activity package versions
The following activity packages and versions are included in the UiPathStudio.msi installer and can be found in the local feed.
| Activity package | Version |
|---|---|
| UiPath.UIAutomation.Activities | v22.10.5 |
| UiPath.System.Activities | v22.10.5 |
| UiPath.Excel.Activities | v2.16.2 |
| UiPath.Mail.Activities | v1.18.2 |
| UiPath.Word.Activities | v1.13.1 |
| UiPath.ComplexScenarios.Activities | v1.3.1 |
| UiPath.Presentations.Activities | v1.7.1 |
| UiPath.Testing.Activities | v22.10.2 |
| UiPath.WebAPI.Activities | v1.13.3 |
| UiPath.MobileAutomation.Activities | v22.10.2 |
| UiPath.Persistence.Activities | v1.4.1 |
| UiPath.PDF.Activities | v3.10.1 |
| UiPath.Terminal.Activities | v2.5.0 |
| UiPath.Form.Activities | v2.0.2 |