I'm using a blink(1) led status light and I'd like to update my existing rules to notify me of specific types of email that comes in.
Almost all of my rules are client side in which a message comes in and is assigned a specific Outlook category, so I'm basically just looking to add an additional step to each rule to start the application.
The LED status light has a command line executable that I can add to a batch file and this does work, but every time the rule executes, I get a cmd window until the executable is done, which of course is expected.
In this past to get around this in other programs like task scheduler, I've used ntwind's HStart, which allows you to launch scripts silently without any windows. The app takes everything that you want to run as arguments after the exe.
I can create Windows shortcuts like the following and they work perfectly, without any issues.
C:\local\hstart.exe /SILENT /NOCONSOLE "H:\Docs\Blink1Control-win\blink1-tool.exe --rgb 255,65,59 --blink 5"
Unfortunately when I point outlook to the shortcut, it just follows the shortcut rather than launching the shortcut, so it strips out all of the arguments and just launches C:\local\hstart.exe, which does nothing.
So my question is, does anyone know how to have Outlook take in an executable with arguments from the "start application" action (or any other workaround) in the rules?
Thanks,
Sean
Almost all of my rules are client side in which a message comes in and is assigned a specific Outlook category, so I'm basically just looking to add an additional step to each rule to start the application.
The LED status light has a command line executable that I can add to a batch file and this does work, but every time the rule executes, I get a cmd window until the executable is done, which of course is expected.
In this past to get around this in other programs like task scheduler, I've used ntwind's HStart, which allows you to launch scripts silently without any windows. The app takes everything that you want to run as arguments after the exe.
I can create Windows shortcuts like the following and they work perfectly, without any issues.
C:\local\hstart.exe /SILENT /NOCONSOLE "H:\Docs\Blink1Control-win\blink1-tool.exe --rgb 255,65,59 --blink 5"
Unfortunately when I point outlook to the shortcut, it just follows the shortcut rather than launching the shortcut, so it strips out all of the arguments and just launches C:\local\hstart.exe, which does nothing.
So my question is, does anyone know how to have Outlook take in an executable with arguments from the "start application" action (or any other workaround) in the rules?
Thanks,
Sean