Sunday, October 9, 2022

Keyboard Operation on RPA

I'm playing with RPA using Sikulix on my Cloud Computer, and the basic concept of Sikulix is Image Matching. RPA is to save a button, field, or message in an image and write the logic to match it.
However, this is a little bit SLOW. The search is done on the screen to find a match with the corresponding image, so it is a reasonable process, and it can be said to be unavoidable. In this case, it is necessary to think about what can be done with scripts and keyboard operations. I have previously introduced the use of RPA notifications via e-mail or LINE.
It is useful to know that Windows can be operated with the keyboard alone more than expecting, which improves the efficiency of RPA.

  1. Alt key family: Window size change, etc.
  2. WinKeys family: Windows standard shortcut keys
  3. Function family: Shift + F10, etc. Substitute for right button menu of mouse.
  4. Tab key: Move between fields, links in the browser, etc.

When I actually tried this with Sikulix, I also found that it requires a lot of fine tuning at the execution stage. It takes quite a while for the app to accept the next key after starting up or transitioning menus. Of course, it takes a few seconds at most, but if the RPA executes type() without a pause, it usually results in an error. Naturally, the time varies depending on the performance of the machine and the load, so we have a function that waits for a certain amount of time after a key is entered in the type() function, and we fine-tune the waiting time according to the condition of the execution, but if the function is executed for a long time, the time still does not match up and an error occurs. This is a point of another difficulty that has not existed in previous command-line programs.

Labels: , ,

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home