Static parameters in the Post Process Command

When entering the Post Process Command, remember that the script called may reside on the Generate server, which may be different to the EngageOne Deliver server. The Post Process Command value will be run as a command line process on the Generate server.

You can use any scripting language (e.g. Java, Perl, PHP, Ruby) for a post process command, as long as an interpreter for the chosen language is present in the Generate server. When specifying the script interpreter, provide the full path leading to the executable, relative to the Generate server's folder structure. Alternatively, the PATH environment variable can be updated to include the full path.

Since the Post Process Command deals with Generate output, EngageOne Deliver provides static parameter values for your script as a “fill-in” for the EngageOne Deliver folders holding the Generate output. Before execution, these static parameters will be replaced with actual UNC paths to the EngageOne Deliver folders.

For the Post Process Command the following static parameters can be specified:

• _DIJ_ – to be replaced with the DIJ filename, including its full directory path
• Folder_HTML – to be replaced with the folder where Generate outputs HTML files
• Folder_Text – to be replaced with the folder where Generate outputs the text files (linedata or text journal files)
• Folder_Attachx – to be replaced with the folder where Generate outputs the PDF files for Attachment x specified in the Outbound Profile.
• Folder_Image – to be replaced with the folder where image files are stored for the Outbound Profile that is called after the Generate job successfully completes.

When writing the script file, be careful when accepting input parameters containing back slashes; use escapes when needed (e.g. use “\\” to escape “\”).