Release date: 3 September 2021
Deploying test project packages to Orchestrator resulted in error as they can have multiple entry points. This issue has been addressed by ignoring entry points for packages published from a Testing project.
Release date: 1 September 2021
This update brings changes to the Orchestrator authentication, new test set configurations, and bugfixes.
- Authentication with Orchestrator is now possible through external apps. You can configure Orchestrator as a new service connection.
- You can configure the UiPath Pack task used for publishing packages in Orchestrator, to report workflow validation errors. This additional configuration allows you to check your project for Workflow Analyzer violations.
- Now you can parameterize your test cases at runtime by defining arguments at the test set level. You can use this feature to reconfigure existing test cases by overriding the default argument value, instead of creating new ones.
- Test results now show assertion details.
- Libraries within Object Repository that were published through the plugin did not show Object Repository details in Studio.
- Using the UiPath Deploy task to create a process that was already existent in Orchestrator resulted in error.
Release date: 3 August 2021
This update adds additional information to the testing items and fixes a couple of bugs.
- Folders with a dedicated package feed are now supported for package deployment.
- Test results now contain assertion details and outcomes, and arguments such as device information to help you identify executed test cases.
- Links to the Orchestrator test set results are now available as part of the UiPath Test job output.
- Now you can define entry points (XAML files) when configuring a process. This is helpful for packages with multiple entry points activated.
- When you run a job, you can select whether it is going to be executed through production or non-production robots.
- Now, you can provide a description for Assets ca within the CSV file.
- The asset descriptions were not properly displayed due to a character encoding issue.
- Packaging libraries that included namespaces with periods through the UiPath Pack task failed.
Release date: 23 March 2021
This update fixes a couple of bugs.
- Packaging Orchestrator projects version 2018.x did not work with the UiPath Integration for Azure DevOps version 2.3. The issue has been fixed using UiPath Pack with Studio version 2018.x.
- Executing tests within Orchestrator processes did not work whenever they were uploaded via the UiPath Deploy task and then ran through the UiPath Run Tests task. This issue was caused by a duplicate package version in Orchestrator.
- Executing UiPath Manage Assets task on non-Windows build agents did not result in a proper error message. Now, when the UiPath Manage Assets task runs on a non-Windows build agent, the information is logged within the command-line.
Release date: 11 March 2021
This update provides compatibility with our latest UiPath Cloud Orchestrator version. If you are using a cloud-hosted UiPath Orchestrator, make sure that you update your UiPath Azure DevOps extension.
- Our tasks are now all localizable, supporting the following languages: German, English, Spanish, French, Portuguese, Russian, Turkish, Korean, Chinese, Japanese.
- For changing your display language in Azure DevOps, see Set user preferences.
- If your local language is not supported, our plugin will fall back to English.
When packing libraries, we now output more logging information about the compiling process. Also, packing a library will fail if the library compilation fails.
- We fixed an issue were packing a process with an entry point XAML file that contains In/Out argument would not create the In/Out arguments in the generated package, resulting in the arguments not being available in Orchestrator.
- We fixed an issue that resulted in packing incorrectly a library when the task is run on a Windows machine with FIPS enabled.
- We fixed an issue where the Test task would fail if used in a Release pipeline.
Release date: 8 December 2020
Run job executions as part of a new task called Run Job.
Manage assets as part of a new task called UiPathAssets. You can either deploy using an upsert operation, or delete assets.
Logging is now improved with clear-cut error messages that provide context and call-to-action.
- Custom non-activity packages are deployed in the libraries feed when using the Deploy task
- The UiPath Pack task compiles expressions and VBA activities.
- Extension configuration includes non-Latin characters.
Updated 21 days ago