My bot requirement is need to account the invoice in the desktop application and it has 10 fields.Bot picks the one invoice and processed neccessary steps and need to save the particular invoice document.
It’s correctly entered the input in the desired field through simulate,Send windows message,Hardware events input mode except one field…The desktop application behaviour is when we click the save button it generates the document number and the it clears the current input details.
I am having issue in one field,it’s entered the input correctly through simulate mode but when i try save the invoice it saved and generated the document number also but it does not clear the current input detail for particular field so particular field details not captured in manual report verification.
Thanks for your suggestion anil…I don’t have issue in typing the input field…After typing all field need to save the particular document.
The application behaviour is After successful save document it generated the document number and cleared the all inputs for particular document but in my case it clears all input field except one field…
I have seen times where the automation appears to type the data into a field but the application doesn’t recognize it. This is due to the input method. You can change the input method for each individual Type Into, until you get it to work. Tedious, but that’s what we do.
Yes…You are right…I have changed my input mode for this it’s working fine in the hardware event but need to run bot via unattende mode so i have changed the input method to simulate and it got failed…
Thanks…I have used hardware events previously an unattended mode bot got foreground error so i changed the input mode to simulate,windows message for unattended automation…
If you’re getting errors with hardware events in unattended mode, I can guess that you (or someone else) has logged into the server using the robot account (ie with RDP) and then just closed the RDP window without logging out. This leaves the session active but in a state similar to locking your screen, and interferes with automations. You must click Start and Sign Out from the RDP session.
Then that is your problem. It should not get disconnected when you sign out. When you installed UiPath Robot on the server, you probably selected User mode instead of Service mode. You have to install it on unattended servers in Service mode.
Once they’ve installed it in Service mode, log into the server as the robot account, then click Start and Sign Out. Now check that it stays connected and you can run the automation unattended.