Click and fill an element using Vision No Longer working

Leeann

Hi @Product ,

We have a wrkflow that has switched from using element-description to element-text but despite the text being present, it's returning no-result.

We've also noticed this in a few other wrkflows today.

Example of Wrkflow with element-description working
Launch ID: 1158921
Account name: 5812
Wrkflow: AWS 05: BMO_RTND_CHK (ID: 53751)
Launch name: Launch-851132fc
Execution ID: 584f081a-f97f-4771-9372-90a336dcb9eb

Example with the recently updated element-text
Launch ID: 1162361
Account name: 5812
Wrkflow: AWS 05: BMO_RTND_CHK (ID: 53818)
Launch name: Launch-4347445c
Execution ID: dee9aaf2-b75a-42cd-baee-434f80b4b941

I've updated the wrkflow to use an image selector for the time being.

Leeann

Similarly, switched to image and it was working.
While monitoring I watched it populate the input field, but then it returned unsuccessful

Launch ID: 1162484
Account name: 5812
Wrkflow: AWS 05: BMO_RTND_CHK (ID: 53868)
Launch name: Launch-45e988d8
Execution ID: 7b607bef-124e-4e90-b421-4eefa651ff47

But in the same run, with the same WA, it was successful beforehand
Execution ID: ea7496be-9622-4a60-be6c-9fb4f008f02e

And success on the third reset:
Execution ID: 12a466e0-9c6a-4334-ab48-517b07a59d4c

Launch-68593383
Shows multiple retries where I witnessed the WA populating the field, the screen changing, and it still returned unsuccessful

Nick

We identified that this was an issue with "Disable value type validation" input being unclear. This Wrk Action will validate the text is typed where you clicked. However, since you're not typing where you clicked (you're typign beside it) it was producing irregular results. I've made a ticket to modify the WA to make this feature more clear.

I believe everything is now working as expected.

https://wrk-technologies.atlassian.net/browse/SUP-1744

Nick

An update on why Search BMO_ReturnCheck retrieved nothing. It looks like the technology we use to extract text read all BMO_ReturnedCheck as "BMO Returned Check" I've validated that "Search BMO Returned Check" works as expected but I can't influence how the technology reads the characters.

From a product perspective I believe it should be easier to figure out what the Wrk Action thinks the text is for testing purposes. I'm going to do some research and see if there's a nice way that we can expose to the user the text that was found so these things are easier to debug.