2024.10.5

Release date: October 21, 2024

Coded automations features

Workflow Analyer rule for code

We have introduced two new Workflow Analyzer rules:

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

You can now access 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.

Properties panel for coded automations in libraries

You can now seamlessly adjust the properties of a coded automation reused as an invoked workflow through the Properties panel. This applies when you export a coded automation to a library, install that library into another project, and invoke the coded automation within your current XAML workflow. Simply select the invoked workflow, navigate to the Properties panel, and modify the available properties of the invoked coded automation as needed. For more information, visit Invoking coded automations using libraries.

Test automation features

XBrowser Test Template

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 Autopilot^TM. Visit Generating test cases using AI to check how to generate low-code test cases.

Autopilot^TM improvements

The panel allows you to use Autopilot™ to summarize your workflow and generate workflows from a centralized interface. The panel also improves error handling and troubleshooting by providing AI-based suggestions for resolving both low-code and coded workflow errors, including errors identified by Workflow Analyzer rules. Additionally, you can use Autopilot to search the entire UiPath documentation directly from the panel. To learn more, see The Autopilot Panel.

Coded automations improvements

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.

Test automation improvements

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.

Other improvements

Optimized compile times for complex projects including low-code and coded test cases, execution templates, and entities.

Breaking changes

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.

This doesn't change anything for your Integration Service connections. But, you must manually change the name of the connection that you have set in your coded automations. For instance, if you have an automation where you have a connection similar to this one:

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.

Known issues

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 and isolated, you may encounter a compilation error.

Visit Studio release notes to check all the updates for 2024.10.5.

On this page