UiPath 26.0.187 February Community Release

UiPath 26.0.187 February Community Release

Studio

For the Workflow Analyzer rule ST-USG-014 (Package Restrictions), you can now:

  • use more than 250-characters
  • use the less-than (<) operator

This should provide more flexibility when it comes to this rule, both for allowed and prohibited packages.

UI Automation

The features below are available as part of the UiPath.UIAutomation.Activities 26.1.0-preview package.

Object Repository - Synchronize Window Selector

During Object Repository creation, when elements are captured under a Screen, a Window Selector is automatically captured and saved together with those elements.

Previously, if the Window Selector for the Screen was updated, the change was not propagated to its child elements, and in some cases the Window Selector had to be manually updated for each child.

We have now added an option in the Edit Screen window: Update the window selector in children objects. This allows any changes made to the Screen’s Window Selector to be automatically applied to all child elements.

Chromium Native Support

We continue to ensure support for the latest embedded browsers technologies. This version adds compatibility for:

  • JxBrowser version 8.15.0 - 8.16.1
  • Chromium version 146 / Electron 41, 42
  • Edge WebView2 version 144

Accessibility Testing

Accessibility Testing enables teams to continuously test and validate accessibility conformance of webpages throughout development and release cycles — ensuring digital inclusion, reducing risk, and enabling faster remediation of issues.

The Accessibility Check activity (available as part of the UiPath.UIAutomation.Activities 26.1.0-preview package) enables users to perform Accessibility Testing in all Test Manager instances delivered with Test Cloud.

This activity loads a web browser page, and performs accessibility checks as per the WCAG 2.1 (or higher) standard.Examples of accessibility checks include DOM and visual accessibility, contrast ratio, alt tags, tab order, improper ARIA roles.

The Accessibility Check activity can be used multiple times within a workflow. Each time the Accessibility Check activity runs, an output file is generated. The activity must be added inside a Use Application/Browser activity configured on the web page to use.

You can store Accessibility Results in an output file, as per the workflow example above. This is a sample Accessibility Results file snippet.

Previous release notes

Please tell us what you think

Which features excite you the most and are you 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:

5 Likes

こんにちは!

2026.0.187 February Community Release に今日アップデートしたら、Clickアクティビティのスコープ/ターゲットが空っぽになってエラーになりました。

  • Indicate on screen を押しても反応なし(選択できない)
  • Clickのターゲットが何も設定されていない状態(空)
  • 他のUI Automationアクティビティ(Type Intoなど)は今のところ空になってないのを確認済み
  • フローの修正は一切してなくて、アップデートしただけです。
    似た報告で186でもUI Automation壊れるケースがあったのを読みました。
    このバグ(特にClick関連)の修正予定・ワークアラウンドがあればお願いします!

よろしくお願いします!