- 入门指南
- 设置和配置
- 自动化项目
- 依赖项
- 工作流类型
- 控制流程
- 文件比较
- 自动化最佳实践
- 源代码控件集成
- 调试
- 日志记录
- 诊断工具
- 工作流分析器
- 变量
- 参数
- 导入的命名空间
- 编码自动化
- 基于触发器的 Attended 自动化
- 录制
- 用户界面元素
- 选取器
- 对象存储库
- 数据抓取
- 图像与文本自动化
- Citrix 技术自动化
- RDP 自动化
- VMware Horizon 自动化
- Salesforce 自动化
- SAP 自动化
- macOS 用户界面自动化
- ScreenScrapeJavaSupport 工具
- Webdriver 协议
- 扩展程序
- 测试套件 - Studio
- 故障排除

Studio 用户指南
关于 Windows - 旧版兼容性
Studio 2021.10 brought support for .NET-based projects and introduced the concept of project compatibility based on robot type. In releases prior to 2021.10, all projects used the Windows - Legacy compatibility. Starting with Studio 2021.10 until Studio 2024.10, you had the option to create projects with the Windows and cross-platform compatibilities in addition to Windows - Legacy.
-
Studio LTS - 以每年的发布周期提供长期稳定性。
- Studio 持续发布- 经常提供更新和新功能,同时保持可靠性。
要了解更多信息,请参阅产品生命周期支持条款页面。
下表突出显示了两个 Studio 版本之间的主要区别:
Studio 版本 | 目标受众 | 云连接要求 | Windows - 旧版支持 | 支持模型 | 发布周期 |
---|---|---|---|---|---|
Studio LTS 工作室年份。 10 .补丁 例如:2024.10.8 | 需要长期支持、稳定性和 Windows - 旧版支持的企业用户。 可用于内部部署连接和 Automation Cloud/Automation Suite 连接。 |
|
|
长期支持 (LTS) 24 个月主流支持 + 12 个月扩展支持。 | 每年一次。 |
Studio 持续发布 工作室年份。 0.补丁 例如:2025.0.157 | 希望经常更新和添加新功能,同时保持可靠性的企业用户。 只能与 Automation Cloud 连接一起使用。 |
|
|
持续发布支持 在下一次更新之前,每个版本都受支持。 | Every two months. |
在可预见的将来,Studio LTS 将继续允许打开和编辑 Windows - 旧版项目。
Studio 持续发布不再允许创建或编辑 Windows - 旧版项目。
允许创建 Windows - 旧版项目的最后一个 Studio LTS 是 Studio 2024.10。 可以通过监管策略启用此选项。
现在,新项目默认兼容 Windows。不再支持创建和编辑具有“Windows - 旧版”兼容性的项目,这意味着新功能仅在具有 Windows 和跨平台兼容性的项目中可用。
Using the Windows or cross-platform compatibilities unlocks future innovations and prepares you for the UiPath Agentic Automation vision, featuring:
- Robots that handle structured, rule-based tasks efficiently.
- AI-Powered Agents that process unstructured data and make intelligent decisions.
- Humans that validate and oversee critical automation workflows.
Access new capabilities
Windows and cross-platform projects give you access to a next-generation capabilities which are not available in Windows - Legacy, including:
- 支持在数据管理器中创建全局变量和常量。
- 新的设计体验可用于跨平台项目和 Windows 项目中的某些活动。
- 能够自定义从库生成的活动的布局。
- Coded automations.
- Autopilot™ capabilities.
- Business Process Model and Notation modeling through long running workflows.
Enhanced performance and scalability
Windows and cross-platform projects:
- Are compiled and provides significant performance improvements, reducing execution time for automations.
- Are ideal for large-scale automation scenarios with high transaction volumes.
- Feature modern memory management and Just-In-Time (JIT) compilation.
Enhanced security
- .NET includes the latest encryption algorithms and security protocols to protect sensitive data.
- Active maintenance ensures quick resolution of vulnerabilities, minimizing risks.
Reduced technical debt
- Converting Windows-Legacy projects removes reliance on deprecated libraries and outdated technologies.
- Future upgrades and enhancements will be easier and more cost-effective.
- Modern workflows are easier to debug, scale, and adapt to evolving business needs.
Studio 附带一个内置的转换工具,可用于将任何 Windows - 旧版项目转换为 Windows 项目。
将项目转换为 Windows 项目时:
- 项目依赖项是根据以下规则管理的:
- 如果配置的包源中存在相同版本的软件包,则不会更改 Windows - 旧版项目中使用的版本。
- 如果不存在相同版本的软件包,则 Windows - 旧版项目中使用的版本将更改为最近版本的最新补丁。
- 转换后的项目中将保留所有活动和属性。
- Windows - 旧版和 Windows 项目中不同的命名空间已更新。
-
系统将添加 Windows 项目中所需的命名空间,并删除仅在 Windows - 旧版项目中使用的命名空间。
注意:在转换库在其中作为依赖项安装的流程之前,请转换并重新发布 Windows - 旧版库。
要将旧项目转换为 Windows 兼容的项目,请执行以下操作:
-
在 Studio 中打开 Windows - 旧版项目,并确保仅在一个 Studio 实例中打开该项目。系统将显示一个新窗口。
-
选择转换方式:
- 要使用 Windows 兼容性创建当前项目的副本并保留原始 Windows 旧版项目,请选择“新建项目”。输入新项目的名称、创建位置以及(可选)说明。
- 要更新现有项目并将其转换为与 Windows 兼容的项目,请清除“新建项目”复选框。如果选择此选项,则对项目所做的更改将无法撤消。
- 单击“转换”。
如果依赖项问题导致转换后活动无法解析,则每个此类活动顶部都会显示一条消息,指出该活动缺失或无法加载。每个活动都会提供以下信息:显示名称、活动命名空间、活动属性和值。单击“替换”以查找替代方法并替换缺失或无效的活动。有关更多信息,请参阅缺少活动或活动无效。
- Inventory and assessment - Prepare a detailed inventory of all your Windows - Legacy projects and their dependencies:
- List all projects, libraries, and dependencies.
- Assess compatibility with the Windows (.NET) environment.
- Identify components that need updates or replacements.
Note: The NuGet Package Explorer application can be used to inspect .NET target frameworks. - Proof of concept - Test the conversion process on a small subset of workflows:
- Select a representative workflow that has a library added as a dependency.
- Perform a pilot conversion to identify challenges and blockers.
- Validate the result with tests.
提示:- Create a backup of the Windows - Legacy project and library.
- Do not change the name of the project or library when migrating.
- Migrate the library first and publish it. Don’t worry – the migrated version of the library cannot be used in Windows - Legacy projects.
- Scaling - Convert all projects and libraries systematically:
- Migrate all libraries and publish them.
- Migrate all projects.
- Validation and testing - Ensure the converted workflows perform as intended:
- Perform testing.
- Address errors or compatibility issues iteratively.
- Test interactions with external systems and data sources.
- Production deployment - Transition the project to the production environment:
- Deploy workflows to production.
- Monitor for stability and performance issues.
- Provide user training or updated documentation if necessary.
- Post-migration monitoring - Report migration issues to UiPath for future improvements:
- Send feedback.
- Share challenges or solutions with UiPath representatives.
问题 | 解决方案 |
---|---|
Some expressions are incompatible with Windows projects and need to be manually changed to successfully convert a Windows - Legacy project to Windows. |
{} to new Object() {} new Object()
{task_output.Id.ToString,task_action,now,I_comment } to new Object() {task_output.Id.ToString,task_action,now,I_comment } |
Validation errors generated by other expressions that worked before the conversion. | Cut the expression using the CTRL + X keyboard shortcut and paste it back in the activity field using CTRL + V. |
在“遍历循环”活动中,将要迭代其值的变量命名为“表达式”会导致编译错误。 | Refrain from naming the variable "expression". |
|
Modern programming languages enforce stricter type inference compared to older versions. Cast the array or the element to the desired type, for example: {} to new Object() {}
|
Encoding-sensitive operations | Add System.Text.Encoding.RegisterProvider(System.Text.CodePagesEncodingProvider.Instance) using InvokeMethod.
|
“ (0x201C) vs. " (0x22)
| Replace all instances with " (0x22), which is the only valid quotation mark for string literals in modern .NET.
|
BC30311: Value of type 'SecureString' cannot be converted to
'CvString'. The selected value is incompatible with the property
type. | Remove and re-add the Computer Vision activity arguments. |
|
To fix these validation errors:
|