NApplication Cardで囲まなくて良いブラウザ操作アクティビティ

日本 フォーラム
1

こんにちは
UiPath Studio 2025.0.161 community editionのユーザです。

スクリーンショットを作成アクティビティはNApplication Cardで囲まなくて良いことは知っていますが、NApplication Cardで囲まなくて良いブラウザ操作アクティビティは他にありますか？

2

Hey @gorby San
In UiPath, NApplication Cards are typically used in automating desktop applications, but for browser automation, most activities usually don’t require an Application Card, as they are inherently designed to work with web elements. Specifically, for browser manipulation activities, you usually don’t need to enclose them in an Application Card, and they function directly within browser contexts such as Chrome, Firefox, or Edge.

Here’s a list of common browser manipulation activities in UiPath that do not need to be enclosed in an Application Card:

1. Open Browser

  • Opens a browser window and navigates to a URL. Does not need an Application Card.

2. Click

  • Clicks on web elements like buttons, links, etc. in the browser. This is directly related to the browser context, so no Application Card is needed.

3. Type Into

  • Types text into web elements like input fields. This activity operates directly within the browser environment.

4. Get Text

  • Extracts text from a web element. Again, this activity interacts directly with the browser.

5. Extract Structured Data (Data Scraping)

  • Extracts data from web pages, usually in tabular format. It works directly with the browser, and you don’t need an Application Card.

6. Navigate To

  • Navigates the browser to a different URL. Works within the browser environment, no need for an Application Card.

7. Find Element

  • Finds a specific web element on the page. No need for an Application Card here either.

8. Wait For Element

  • Waits for a specific element to appear in the browser. It’s a browser-specific activity.

9. Close Tab

  • Closes the browser tab. Works directly with the browser and doesn’t need an Application Card.

10. Maximize/Minimize Window

  • Maximize or minimize the browser window, which is handled directly by the browser activities.

11. Send Hotkey (for browser)

  • Sends hotkeys to browser elements (e.g., Ctrl+T for a new tab). No Application Card required.
5

Hi, Please provide an answer about modern activities.

1 Like
6

Hi, Since it is hard for me to ignore(Because I cannot bare to be silent in this case),I replied him politely.
If you feel further discomfort, please let me know.

1 Like
7

@gorby

Check app state also does not need scope in the modern

If you use classic activities then none of the ui activities need it

Cheers

8

Dear my congenial Indian Friend,
Thank you for your reply!

I remember I received the same comment from you the other day.
However, I am now suspicious for your comment observing the following thread.
What do you think? Please let me know your idea.

9

@gorby

if you just try it you would know it works..

here is an example

The image shows a software automation workflow with a "Check App State" activity highlighted, displaying options for actions based on whether a target appears or does not appear. (Captioned by AI)
The image shows a software automation workflow with a "Check App State" activity highlighted, displaying options for actions based on whether a target appears or does not appear. (Captioned by AI)1482×745 50.8 KB

No use app/broswer here

cheers

10

Hi, @Anil_G My Indian Friend,

Your case is just one case that you do not need to encircle check state activity by Napplication Card.

I found another case that you are recommended to encircle check state activity by Napplication Card.

It seems check state activity is not universally recommended to be isolated from Napplication Card.

How complicated! That’s so UiPath!

11

@gorby

the ask was if it can be used separately..answer is yes it can be used separately..but would you use it or no? this is upto you..but still it has ability to work outside scope there is no question about it..

someone using inside or outside is upto the usecase and usage

cheers