The LogOn property can be defined to use any account. It can be a local windows account or a domain account.
THere's no "FreeFlow Core" account as FFCore runs as the computer (aka NT_AUTHORITY) by default.
I would write a small batch file to do the following:
One other thing I would do... make sure the second workflow has an external node to delete the preflight report.
(note - if needed you can also pass the prefight report to another workflow before emailing it)
How would you go about doing this?
FFCore's notification subsystem will email selected administrators when relevant system events occur. However, it does not provide the same functionality as the email node in FFProM.
However, the External workflow component and the Blat CLI email client can enable building of workflows that send email notifications when jobs each a given point in the workflow.
In order to get this to work I had to change the LogOn property for the FFCore server to an administrator account. Instructions for making that change are in the install guide.
Note: In theory this should work with an account with fewer privileges but I did not attempt that.
I downloaded Blat and dropped it in the Program Files directory. After that, the configuration is pretty simple:
The string used for the parameters:
-to firstname.lastname@example.org -subject "blat test" -body "this is my message" -server xxx.xxx.xxx.xxx -f email@example.com
Most switches are self-explanatory.
The -f switch requires an email address that the SMTP server will recognize.
You can use $FF...$ variables for any of all of the above content which opens up a number of possibilities:
Additional information about supported switches can be found in the Blat Documentation.