Input methods selection (simulate, send window messages) for Click & Type activities

[Cosin (Cosmin Voicu)]

@andrzej.kniola

It’s not like it is required to know exactly how WindowMessages or the API method works, just the basic differences between them are needed.

@andrzej.kniola

if the names of the functionalities correspond too close to 1:1 normal language, the underlying functionality never gets checked.

The purpose of renaming these 3 methods is to better describe what they do, and all their underlying implications to the normal UiPath user (which is, with coding skills, but not necessarily UI automation experience).
I’m afraid that giving no information about what the options do or what’s the difference between them does not encourage research into underlying functionality, it encourages frustration.

But your point is definitely noted, and about that, maybe you can tell me a bit more.
When you first encountered these options, did you feel their current names (Window msgs, Simulate) were clear to you? as to what they do, and when you should use them?

If a user, no matter Technical or Functional, can’t comprehend the above table or can’t be bothered to look it up he will fail with making a working workflow in other ways

Yes, but the fact that you need to fire up a browser and lookup a table using appropriate keywords is a huge drawback, no matter the application, experience, or type of user.
Ideally, all these 3 options should not exist, and you should not have to deal with them. But since that’s not possible, we do want to make it as easy for you as possible.

Thanks!