hello everyone,
I am automating a process that runs on a terminal. I am using the latest version of the terminal package.
I can perform all operations except “set text at field”, “hover mouse”, “move cursor at position” and “get text at position”.
The terminal itself has coordinates that I can see at the bottom right of the screen, but every time I use these features it returns an error.
In your experience, do you know if it depends on the terminal itself? What kind of changes, if any, can be made? More importantly, what can it depend on?
Thanks in advance
Hi,
When are you receiving error ? Is it while developing or during the run time?
Hello @andreus91
If possible share the error that you are getting with a screenshot? It will help to identify the issue.
Thanks
Hi,
if I start the recorder, the options “set field value”, “set field at position”, “get field value”, “get field at position” and “get screen area” are disabled (in light gray).
If I bring the activity, for example set field at position inside the sequence, the error message is as follows:
“Terminal error: FieldNotFound”.
Message: Terminal error: FieldNotFound
System Exception
Hi @andreus91 ,
I would recommend you to use send hotkeys activity.
yes, that is the strategy I am currently using, but imagining having to act on pages containing dozens of text fields with variable position is not the ideal solution.
That is why I was asking if anyone has had experience regarding a similar problem and knew the cause. Does it depend on the terminal? What kind of settings can I check? Is it about the activity uipath?
Thank you
I see…
Basically I had to work with PuTTY and terminal activities were not working fine, so I followed this approach, made the terminal full screen, used send hotkeys for commands, screen scraping/ get text for getting the text…and later applied regex to filter relevant data.
Regarding the specific cause, I’m also following your post. Thanks!
1 Like
Yep, i’ve followed the same approach with regex on screen text, let’s stand by then if someone has already addressed this issue : )
1 Like