UiPath 2024 September Community Release

UiPath 2024 September Community Release

Autopilot for Developers

Introducing the new Autopilot Panel in Studio, designed to streamline your automation development process with the following key features:

  • Automatically summarize workflows by generating top-level annotations.
  • Easily generate a sequence of activities within the current workflow with a shortcut.
  • Get real-time suggestions to fix validation errors.
  • Receive suggestions to resolve workflow analyzer errors.
  • Search official documentation directly within Studio.

Assistant

:rocket: With this release, you can now add user-friendly display names and tooltips to your input arguments in Assistant, ensuring a smooth and pleasant experience for your users.

To configure argument properties, open the Project panel in Studio, right-click an XAML file set as main or marked as an entry point to the project, and select the Argument Properties option.

Select an argument from the left-side menu and enter the following:

  • :abc: Display name – The user-friendly label that appears in Assistant, instead of the argument name;
  • :speech_balloon: Tooltip - A description for the argument that appears when you hover over the info icon (:information_source:) in Assistant.

The image shows a configuration screen with fields for inputting base salary, bonus, and tax rate, under a menu with tabs for Details, Configure, Jobs, and History. (Captioned by AI)

Test Suite

XBrowser Testing template

Cross-browser testing is the process of verifying that a website or web application functions consistently across different browsers, devices, and operating systems. Its importance lies in ensuring a seamless user experience, regardless of the browser used, as different browsers may render web content differently due to variations in their engines and standards support. By conducting cross-browser testing, developers can identify and fix compatibility issues, improving accessibility and user satisfaction across a wider audience.
So far it was very hard to perform cross browser test with UiPath Test Suite as you had to create separate test cases for each browser and maintain different object repositories.
Within 2024, the UiAutomation team has added the capability to parametrize the browser scope – now, with this community release, we have also added a neat Test Case template for XBrowser Testing for convenience.

Here is how it works

  1. Create a new Test Case and select the ‘XBrowser Test Template

  2. After you hit ‘Create’ a new Test Case is generated, using this template. As you can see, it already has a ‘Set Browser Type’ activity at the top and a ‘Browser’ argument, to set the right runtime browser.

    This is now a data-driven Test Case, which has all common browser names as data variations set.
    By hitting ‘Update Test Data’ and ‘Modify File Data’, you can see all browsers used, and you can also edit them in case you do not want to use all of them.


  3. When you now run your Test Case from Test Explorer, you will notice that it executes multiple times, once for every browser configured in your attached test data sheet.

So why is this relevant?
This greatly reduces the effort required for testing your browser app, as you now only have to create and maintain it once, but can execute it for each browser.

Please tell us what you think

Which features excite you the most and you are going to try right away? We want to hear what you think! Please use the A red button labeled "Reply" with a blue left-facing arrow icon. (Captioned by AI) button below :slight_smile:

14 Likes

That’s excellent! :tada:

This was much needed. Users will get context about the arguments.

Thanks,
Ashok :slight_smile:

4 Likes

Generating auto workflow annotations is an awesome upgrade for developers to reduce time investing in writing descriptions.

5 Likes

That’s amazing, that will help developers a lot

1 Like

Well done. I will try it asap

1 Like

About the Autopilot feature:

Did a tryout asking him to complete a Microsoft Teams sequence: get team names from a query, check for some teams existence, get the list of members, erase all members except one.

He used the same “connect” activity for the 3 steps, although changing the name of every card so you got fooled into thinking it was the right activity , then he used the wrong kind of loop for the type the query returned, and then that’s is. Not worth it in my opinion, as you need to figure out what’s going out because you may believe it’s doing the right thing. Oh, and after that, it said I ran out of credits.

1 Like

New testing template, Awesome :heart_eyes:!