Not sure if I'm missing something obvious, but there are two triggers I'd be keen to see included that don't seem to be implemented in the current version:
- Run at startup/login (and shutdown/logout would be nice too)
- Run on keyword entered, so you can implement an autoreplace feature like that in Word (e.g. if you type ##phone it could replace that text with your phone number, but in any application - such as notepad). I mention this one because it's a potential use of WinAutomation mentioned in the "what you can do with automation" article.
Run at startup/login
There are several ways to do that:
(a) Compile to executable (no trigger): Compile an exe file of your job and place it on the Startup menu.
(b) Process Monitor Trigger: Monitor a process that starts when windows start. You may choose the process of an application that is placed in the Startup menu.
(c) Event Log Monitor Trigger: Let your system fully boot and then go to Control Panel - Administrative Tools - Event Viewer and check what was the last entry under "System" category. In most cases monitoring this last event that occurred during the boot process will guarantee that your job will start after windows' full boot.
The method that worked perfectly for me is the "Service Monitor" trigger. I have selected the "WinAutomation Service" to monitor. This launches my job when the WinAutomation's service starts (which is when your system boots), and applies at the "Startup" condition. If you want to launch a job when a user has logged in, you can use the "Process Monitor Trigger" and monitor WinAutomationDIAgent process (since it only starts when a user logs in).
Regarding your second request, please check this thread reply. There is a sample job attached in the specific post that may be what you are looking for. It uses a single hotkey to replace an unlimited number of abbreviations based on a text file database.
==Dedicated Automation Solutions==
==Dedicated Automation Solutions==