+1I have created a workflow with opening a browser and capturing login/password and click event on the login page.
When we run the BOT, we are getting error message from the system saying the fields are empty. Although the browser window the BOT opens is showing those fields as filled in.
When we do the same steps manually on the same login page, everything works as expected.
Any help/direction is greatly appreciated.
Best answer by jon.stueveapeople
Sometimes the set text updates the screen and you can see the text but the characters don’t register in the control. The input text box doesn’t actually record the text, and so on a submit the input is seen as empty by the interface. A good workaround to try it adding a delay time between keystrokes. This simulates actual keystrokes so the interface registers the characters individually. I’ve found 40 milliseconds is a good delay, but you can test shorter times between keystrokes.
This is an example, of the bot executing faster than the UI at the field level.
+17
Could you please share exact error screenshot and task bot line where you are getting the error please
+1Hi
In the Recorder Capture Action, please use the keystrokes and enter 100.
Please find the below snap
+1We have tried all that. Here is the setup and what the team has worked on so far trying to figure out the issue.
We are only reaching out after we have spend over 10 hours trying everything after reading all the documentation.
As you can see, data is getting filled in but click event on login fails when running via BOT.
The same process works when I run it manually, of course.
+1We are very interested in upgrading to full enterprise edition but want to make sure we are able to automate what we need to!
We are wanting to setup unattended BOT’s that run every night.
+7Sometimes the set text updates the screen and you can see the text but the characters don’t register in the control. The input text box doesn’t actually record the text, and so on a submit the input is seen as empty by the interface. A good workaround to try it adding a delay time between keystrokes. This simulates actual keystrokes so the interface registers the characters individually. I’ve found 40 milliseconds is a good delay, but you can test shorter times between keystrokes.
This is an example, of the bot executing faster than the UI at the field level.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
