The ExecuteExternalProcessor Job-Step starts an external process, eg batch file, scripting, exe file, etc. In contrast to the ExecuteExternal Job-Step, this process is executed for all attachments of all incoming messages.
| Name | Meaning |
|---|---|
| Name | Name of the job step that will appear in the job designer |
| Type | Type of the job step. |
| Description | Optional description for the job step. |
| ExternalCommand | File, scripting, external process to be started, for example sample.bat |
| CommandArguments | The script arguments. You can use all variables from Register a containerizer and the variable ${Filename} for the saved attachment. Note that you have to set the quotes except for ${Filename}. |
| MatchFile | A regular expression1) which, if set, must match the filename. |
| TraceStandardOutput | True: Logging the external process. |
| ImportIfChanged | True: Import attachments if changed by the command. |
| ThrowTaskOnNonZeroExit | True: Throw a Task if external process is not terminated with return value 0 (eg: error). |
With ExternalCommand set “<path>\test.bat” and the following values in CommandArguments:
${Filename} "Subject=${Subject}" "${CurrentFileName}"
eBiss will execute the 'cmd.exe' with following args:
/C "<path>\test.bat" "<eBiss path>\bin\temp\19cc929426a74edabd1f6bbf417ea868.dat" "Subject=<message subject>" "<attachment filename>"
Therefore, the second parameter (%1) in the batch contains the path with the attachment content.
Sorting the contents of the attachments
ExternalCommand: Sort
CommandArguments: /+1 /r ${Filename} /o ${Filename}
ImportIfChanged: yes