Run a specific external application after processing the data.
In the processing method, select the Tools > Post Processing Plugins node.
Choose Run external program from the drop-down list, and click + to add the plugin to the processing method.
Under Custom name, enter a name.
In the method report, the plugin will be shown with this name.
Select the Run plugin check box to run the plugin at the end of processing your data.
Under External program, provide the path and name of the executable file that you want to run.
The executable file can be located on the local computer or on a network share.
Ensure that you have the privilege to run the executable. If an instrument service user is defined in your system, this user must have the privilege to run the executable. For details, see Create Account to Access Network Share in the installation instructions. |
In case of unattended processing in Client/Server systems, the executable file runs on the Analytical Instrument Controller (AIC). Ensure that the executable file runs without a user interface. |
Ensure that only a limited number of instances of your executable is running at the same time. There is no automatic cleanup for orphaned processes. |
Under Parameters, provide
the parameter or parameters that you want to pass to the external program.
Click
to select tokens as required.
The syntax for passing parameters depends on the application. The content of this field is simply appended to the program call, same as if you append parameters in the Command window.
Example
To create a file hello.txt with the content Hello from Agilent on the Desktop, you would use the command echo "Hello from Agilent" | Out-File -FilePath "$env:USERPROFILE\Desktop\hello.txt" in a PowerShell window.
To perform the same action using the Run external program plugin, you would choose the following settings:
External program | C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe |
Parameters |
echo "Hello from Agilent" | Out-File -FilePath "$env:USERPROFILE\Desktop\hello.txt" Note: this example only works when there is no Onedrive running that modifies the $env:USERPROFILE look up. |