OnSuccessEnabled, OnSuccessCommand, OnSuccessParameters, OnSuccessStartingFolder, OnFailureEnabled, OnFailureCommand, OnFailureParameters, OnFailureStartingFolder |
OnSuccessEnabled
Default: empty string
When empty, any Run Command options set in the profile for success are used. Set to 0 to disable or 1 to enable.
[Run] OnSuccessEnabled=1 |
See also: Run Commands
OnSuccessCommand
Default: empty string
The path to the command to run when conversion succeeds. This path can be hard coded, or dynamically created using environment variables (%VARIABLE%) and/or a value read from a registry keys ($[REGKEY]. When using any of the commands provided in the RunCommands folder, our internal variable %InstallFolder% can be used to generically specify the path. Your own commands can also be copied into this folder to take advantage of this feature.
This command can also be used to signal an event to another waiting program. See Using Environment Variables and Registry Keys and Signaling Events Using Run Commands.
[Run] OnSuccessCommand="C:\Program Files\PDF Image Printer 12\RunCommands\CustomMoveFiles.bat" ;OnSuccessCommand="%InstallFolder%\RunCommands\CustomMoveFiles.bat" |
See also: Run Commands
OnSuccessParameters
Default: empty string
Any parameters to pass to the command. Parameters can include built-in run command macros. If you need to pass quoted parameters, you need to have one level of outer quotes. When the script file is read the outer quotes are striped off. Environment variables can also be used in the parameters list.
The last parameter passed is always the path to a text file (pnf-<GUID>.txt) created by PDF Image Printer. This text file lists each file generated, one per line, and can contain zero or more lines.
[Run] OnSuccessParameters="$(OutputDir) "$(PrintJobID)" "$(FileGUID)"" |
See also: Run Commands
OnSuccessStartingFolder
Default: empty string
The default working directory for your application, if needed. Environment variables and registry keys can also be used.
[Run] OnSuccessStartingFolder= |
See also: Run Commands
OnFailureEnabled
Default: empty string
When empty, any Run Command options set in the profile for failure are used instead. Set to 0 to disable or 1 to enable.
[Run] OnFailureEnabled=1 |
See also: Run Commands
OnFailureCommand
Default: empty string
The path to the command to run when conversion fails. This path can be hard coded, or dynamically created using environment variables (%VARIABLE%) and/or a value read from a registry keys ($[REGKEY]. When using any of the commands provided in the RunCommands folder, our internal variable %InstallFolder% can be used to generically specify the path. Your own commands can also be copied into this folder to take advantage of this feature.
This command can also be used to signal an event to another waiting program. See Using Environment Variables and Registry Keys and Signaling Events Using Run Commands.
[Run] OnFailureCommand="C:\Program Files\PDF Image Printer 12\RunCommands\SendEmail.bat" ;OnFailureCommand="%InstallFolder%\RunCommands\SendEmail.bat" |
See also: Run Commands
OnFailureParameters
Default: empty string
Any parameters to pass to the command. Parameters can include built-in run command macros. If you need to pass quoted parameters, you need to have one level of outer quotes. When the script file is read the outer quotes are striped off. Environment variables can also be used in the parameters list.
The last parameter passed is always the path to a text file (pnf-<GUID>.txt) created by PDF Image Printer. This text file lists each file generated, one per line, and can contain zero or more lines.
[Run] OnFailureParameters="$(OutputDir) "$(PrintJobID)" "$(FileGUID)"" |
See also: Run Commands
OnFailureStartingFolder
Default: empty string
The default working directory for your application, if needed. Environment variables and registry keys can also be used.
[Run] OnFailureStartingFolder= |
See also: Run Commands
