What is the difference between CromicAPI and Sumulate click

Help Studio
, ,
1

Hi Team,

I want to know the exact difference between ChromicAPI and Simulate.

I know Its accuracy and Sumulate is not supported by the hotkeys.
I need a proper example of why we need to use Cromic API instead of Simulate click.

Thanks.

1 Like
2

@copy_writes

Overall, you should use the Chromium API when standard automation techniques like Simulate Click fail, when dealing with dynamic UI elements, or when automating in virtual or remote environments. For most other scenarios, standard UiPath activities like Simulate Click should work fine and are generally faster and easier to implement.

Chromium API, powered by Computer Vision, allows for precise automation by comprehending screen elements without relying on standard selectors. Use it when dealing with custom UI elements, dynamic interfaces, or virtual environments where Simulate Click might fail due to UI changes or unsupported hotkeys, ensuring more reliable and resilient automation.

3

Hi @copy_writes

  • Chromium API is a newer input method that sends trusted events directly to the browser. This means that the browser is more likely to interpret the events correctly, and it can also be used to automate actions that are not possible with Simulate. However, the Chromium API is not as well-supported as Simulate, and it can be more difficult to use.
  • Simulate is an older input method that sends hardware events to the operating system. This means that the browser is less likely to interpret the events correctly, but it is more widely supported and easier to use.

https://docs.uipath.com/studio/standalone/2023.4/user-guide/input-methods

Hope it helps!!

4

Hi @copy_writes

We generally recommend the Simulate Type/Click method as it is the fastest of the three and works in the background, but only if you do not need to send special keyboard shortcuts.

=> The Chromium api will be compatible only for web applications but the Simulate is compatible for both desktop and web applications.
=> These both are supported for the background execution.
=> The Simulate is faster then the chromium api because the Simulate input method is designed to simulate human-like interactions with web elements by injecting JavaScript directly into the Chromium engine.
=> We can use the simulate in both classic and modern activities but the chromium api will work on modern design activities only.

Check the below image.

image
image1432×379 34 KB

Hope it helps!!

1 Like
5

Hi @copy_writes

  1. Simulate Click: “Simulate” is an input method that allows UiPath to simulate user interactions, such as clicks and keystrokes, on elements in the user interface. When you use “Simulate Click” on a web element, UiPath generates a low-level input event, emulating the action as if a human user performed the click. It is a reliable method for interacting with various types of applications and elements.

  2. Chromium API: “Chromium” is a more advanced and specialized method for interacting with web pages in Google Chrome and Microsoft Edge browsers. It utilizes a special web driver to communicate directly with the browser’s rendering engine.

1 Like
6

@copy_writes

If you got the answer for your question. Please mark it as solution to close the thread.

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.