- リリース ノート
- 2024.10.1
- 2024.10.5
- 基本情報
- セットアップと構成
- オートメーション プロジェクト
- 依存関係
- ワークフローの種類
- ファイルの比較
- オートメーションのベスト プラクティス
- ソース管理との連携
- デバッグ
- 診断ツール
- ワークフロー アナライザー
- ワークフロー アナライザーについて
- ST-NMG-001 - 変数の命名規則
- ST-NMG-002 - 引数の命名規則
- ST-NMG-004 - 表示名の重複
- ST-NMG-005 - 変数が変数をオーバーライド
- ST-NMG-006 - 変数が引数をオーバーライド
- ST-NMG-008 - 変数名が最大文字数を超過
- ST-NMG-009 - DataTable 型の変数のプレフィックス
- ST-NMG-011 - DataTable 型の引数のプレフィックス
- ST-NMG-012 - 引数の既定値
- ST-NMG-016 - 引数の長さが最大文字数を超過
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - 多数の引数
- ST-DBP-003 - 空の catch ブロック
- ST-DBP-007 - 複数のフローチャートレイヤー
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - 未定義の出力プロパティ
- ST-DBP-021 - ハードコードされたタイムアウト
- ST-DBP-023 - 空のワークフロー
- ST-DBP-024 - 永続性アクティビティの確認
- ST-DBP-025 - 変数のシリアル化の前提条件
- ST-DBP-026 - [待機] アクティビティの使用
- ST-DBP-027 - Persistence のベスト プラクティス
- ST-DBP-028 - 引数のシリアル化の前提条件
- 変数
- 引数
- インポートされた名前空間
- コード化されたオートメーション
- トリガーベースの有人オートメーション
- レコーディング
- UI 要素
- 制御フロー
- セレクター
- オブジェクト リポジトリ
- データ スクレイピング
- 画像とテキストの自動化
- Citrix テクノロジの自動化
- RDP の自動化
- VMware Horizon の自動化
- Salesforce の操作の自動化
- SAP のオートメーション
- ログ
- ScreenScrapeJavaSupport ツール
- Webdriver プロトコル
- Test Suite - Studio
- 拡張機能
- トラブルシューティング
2024.10.5
Release date: 21 October 2024
Autopilot can also generate activity output variables which are then automatically used in subsequent activities (for example, Autopilot will use the output variable generated for a Create Event activity in the Event field of a Forward Event activity).
The new Autopilot panel makes the development process more accessible and efficient.
Two new Workflow Analyzer rules are now available to help with migrating projects from the Windows - Legacy to the Windows compatibility.
Workflow Analyer rule for code
- ST-DPB-010: Make sure that within any coded workflow or test case, only one method is marked with either the
[Workflow]
or[Test Case]
attribute. - ST-NMG-017: Ensures that a class name is distinct from the default namespace.
XML documentation file for your custom code and libraries
XML
documentation files after you publish a project and enjoy the benefit of code documentation for your custom code and libraries. After the project is published, the XML
files are generated alongside the DLL
and PDB
files in your project folder. You can also find them in the lib folder of the generated NUPKG
file. Visit Working with Coded automations to learn more about publishing projects that contain coded automations.
XBrowser テスト テンプレート
Streamline your testing processes of websites and web applications by using the XBrowser Test Template. This template allows you to test the same test data of a web application with multiple browsers, all into one single automation. Visit XBrowser Test Template for more information.
Generating low-code test cases using AI
You can now generate a fully automated low-code test case using natural language, with the help of AutopilotTM. Visit Generating test cases using AI to check how to generate low-code test cases.
We have made several improvements to the way in which you can manage cloud projects.
When a cloud project is edited in Studio Web, you can only open it in Studio in read-only mode (the project cannot be opened in edit mode both in Studio Web and Studio).
Studio now informs you every time you lose editing access (for example, when the project is edited by someone else or the cloud connection is lost), to avoid possible future conflicts when trying to save the project.
When a project is saved in a different location on your machine, you now have the option to either unlink the project from the cloud or use the new local path to the project.
When you open a project, Studio automatically detects if you manually moved the project to a different location on your machine, and your input is not needed.
Lastly, local and cloud projects are now clearly labeled as such in the Studio Backstage.
- New designs for the Start, State, and Final nodes.
- An infinite canvas Designer panel, with a new grid system to better position your activities.
- Improvements to the design and functionality of activities and connectors, complete with support for adding annotations.
- 行間とテキストの配置を修正しました。
- Improving the layout of the Fix and Use Variables buttons.
- 専用の [元に戻す] ボタンと [やり直し] ボタンを追加しました。
- The following keyboard shortcuts now allow you to expand or reduce your current code selection as follows:
Ctrl + Shift + <Num+
: Expand your current code selection to include the next larger syntax node. From the current line, you can expand to include the current block, then the current method, the current class, the namespace, and finally the entire file.Ctrl + <Shift + Num-
: Contract the current syntax node selection incrementally.
- You can now record your interactions with UI elements and translate them into coded automations.
AI-generated test data improvements
- When using Autopilot for generating test data, you can instruct it to introduce additional arguments, which will be included in the test case once you import the generated data set.
- Now, you initially offer a prompt instruction to Autopilot to get a primary test data set. This is a change from the previous behavior where Autopilot initially created a test data set that you were able to refine using prompt instructions.
- You can instruct Autopilot to generate a certain number of data variations.
Improved error messages for Postman integration
We've made improvements to the API Test Automation. Error messages from the Postman integration are now more clearly displayed in the user interface.
Converting text into code improvements
You can now turn text into code by selecting the Autopilot icon or by choosing the existent Generate Code action.
- The
UiPathStudio.msi
installer no longer supports thePackages
command line feature flag . This does not impact the installation process, as the feature flag was kept for backwards compatibility and had no real function. UiPathStudio.msi
does not support direct upgrade from Studio 2018.4 or lower. Upgrading from such a version must be done through an intermediary upgrade to the latest 24.10 patch.
- Optimized compile times for complex projects including low-code and coded test cases, execution templates, and entities.
- You can now improve the alignment of flowchart nodes and connectors in the Designer panel by using the Auto arrange context menu option. You can choose to make your flowcharts more readable by arranging them either horizontally or vertically.
- Project validation is now faster.
- Studio の Git 連携機能で Schannel がサポートされるようになりました。
- The Dictionary Builder now supports complex expressions both in the Key and Value fields. You can also switch between the Expression Editor and the Dictionary Builder in activity properties that only used the Dictionary builder.
- You can now add a top level annotation to the main sequence of a project by right-clicking the Designer panel and selecting Annotations > Add Annotation. The main sequence is now hidden by default.
- We have improved the message you see in the Manage Packages window when you select an activities package that is not compatible with your project.
- The Project Dependencies Mass Update Tool now has an Install Missing Package option for updating dependencies which are already part of projects or installing dependencies in projects that do not contain them.
- To reduce the size of published packages, .git and .svn folders are now excluded from the resulting NUPKG file.
-
Several performance improvements have been made to RAM usage.
Coded Automations
To avoid conflicts when you use connections from the same Orchestrator folders, you now need to use a different naming convention when establishing connections in coded automations. After you create the connection in Integration Service, call it in your coded automation using both the Orchestrator folder and subfolder name where the connection resides.
var myGmailConnection = connections.Gmail.My_Workspace_john_doe_gmail_com
, where My_Workspace
is the Orchestrator folder name, you now need to include the subfolder name where the connection was first made. So if the Gmail connection is in the My Gmail Workspace
subfolder, you would change the connection name to: var myGmailConnection = connections.Gmail.My_Workspace_My_Gmail_Workspace_john_doe_gmail_com
.
For more details on the new way to set up service connections in coded automations, visit Creating Connections for services in coded automations.
Studio ログ
Fatal
severity logs appear as Trace
logs in the Output panel and are filtered as Trace
logs when clicking the Trace button in the panel’s header.
- While debugging a XAML workflow within a project that contained CS files, an 'Unexpected error during library compilation: Value cannot be null. (Parameter 'type')' error occurred, which caused the compilation to fail.
- A Root element is missing error occurred when publishing some background processes.
- プロジェクト依存関係一括更新ツールを使用する際に、依存関係が不足している一部のプロジェクトが誤ってパブリッシュ済みとして報告されていました。
- Studio logged Bad IL format compilation errors when running some projects migrated from Windows - Legacy. These errors did not affect project execution.
- Unused dependencies were not correctly identified when analyzing some projects migrated from Windows - Legacy.
- Compilation failed for some projects where the combined length of user strings exceeded the allowed limit.
- Renaming a project caused invalid references in projects with XAML files referencing code assemblies.
- When creating custom activities using code, the UiPath.Workflow 6.0.0-20231211-03 package led to a version conflict with Microsoft.CodeAnalysis.Common. The solution involved adding a previously missing dependency.
- Publishing some projects with missing dependencies in a GitHub CI/CD pipeline did not return validation errors.
- The ST-NMG-004 - Display Name Duplication rule incorrectly detected repetitive activities names.
- The Locals panel did not display any information when debugging some projects saved on a network drive.
- Elastic Robot Pools were not displayed in the Machine drop-down menu when configuring an Unattended Robot remote debugging connection.
- Studio incorrectly detected workflow changes when debugging some projects using Step Into.
- The Text Builder showed a non-functional Plus button in cross-platform projects.
- Multiple BC31424 and BC30652 validation errors occurred when trying to publish some projects created in earlier versions of Studio.
- Publishing some projects that contained a large number of test cases (200+) took longer than expected.
- Compiling some projects containing a large number of workflows (1000+) took longer than expected.
- Application tracking does not work for applications used in libraries.
- When working with coded workflows or test cases, an error can occur. If you attempt to create arguments of any type (including In, Out, and In/Out) with certain names such as
result
,newResult
,codedWorkflow
andisolated
, you may encounter a compilation error.
UiPathStudio.msi
インストーラーに含まれており、ローカル フィードから確認できます。
アクティビティ パッケージ |
バージョン |
---|---|
UiPath.UIAutomation.Activities | |
UiPath.System.Activities | |
UiPath.Excel.Activities | |
UiPath.Mail.Activities | |
UiPath.Word.Activities | |
UiPath.ComplexScenarios.Activities | |
UiPath.Presentations.Activities | |
UiPath.Testing.Activities | |
UiPath.WebAPI.Activities | |
UiPath.Form.Activities | v24.10.5 |
UiPath.Callout.Activities | v24.10.5 |