Specify Fax Post-processing
This command is used to indicate that post-processing is required for this outbound fax or email. For a callback request, CopiaFacts creates this command from a $post_process command in the user profile.
Post-processing occurs after a previously requested image or list of images have been delivered or all attempts to deliver the image(s) have failed. Post-processing allows you to "hook" into the outbound fax delivery process. You might use this option to initiate notification procedures after a fax has been sent. Or you might create a procedure to send images to an alternate fax number if the maximum number of attempts have failed.
The parameters on this command are used as follows:
|command||the name of an operating system command, program, or batch file that will be executed to initiate post-processing; or an infobox name for infobox method processing. A program or batch file name must have a file extension if its extension is not .EXE. Operating system commands should be preceded by CMD /c.|
|method||one of the following keywords:|
|internal||COPIAFACTS will invoke (spawn) the specified post-processing command with the following program arguments:|
The full name of the FS file to be processed
The FS file number only with no extension
The call number of the call generating the FS request
The directory that contains the TOSEND, SENT, and FAIL directories
The retry outcome class letter for the most recent attempt
The fax error code ($fax_status2) for the most recent attempt
|Internal post-processing should be used for legacy applications only: to run a program with your own choice of parameters, use infobox post-processing to run a $type query infobox and execute a $run command.|
|internalNT||internal post-processing will be done as for the internal keyword, but the FS file will not be selected for processing on a system which is not running under Windows.|
|internalDOS||internal post-processing will be done as for the internal keyword, but the FS file will not be selected for processing on a system which is running under Windows.|
|external||post-processing will be performed by some external process (not supplied), running on a networked system.|
|FFEXTERN||post-processing will be performed by FFEXTERN and the FS file will be placed in the POSTPROC directory so that FFEXTERN will detect it.|
|FFCLIENT||post-processing will be performed by FFCLIENT and the FS file will be placed in the PSPLOCAL subdirectory of the owner directory under USERJOBS so that FFCLIENT will detect it. The $fax_user command must reference a UJP file.|
|infobox||control will pass to an infobox sequence, which MUST be terminated by a transfer to state IIF_PROC_COMPLETE (s191), after the final SENT or FAIL disposition is known. Either $next_box or $chain can be used to transfer to this state.|
|infoboxall||control will pass to an infobox sequence, which MUST be terminated by a transfer to state IIF_PROC_COMPLETE (s191), after every transmission attempt. Either $next_box or $chain can be used to transfer to this state.|
|infoboxend||control will pass to an infobox sequence, which MUST be terminated by a transfer to state IIF_PROC_COMPLETE (s191), after the FS file has been written to SENT or FAIL. This allows the final FS file to be archived. Either $next_box or $chain can be used to transfer to this state. Variables set with $set_var in the postprocess infoboxes will not be saved in the FS file.|
When you select the internal processing method the COPIAFACTS thread controlling the line is suspended. If you have a lengthy process, this could delay the processing of calls by the line and it would be better to do the processing externally.
An external process must monitor the outbound request files to determine which requests it must process. It should examine this $fax_post-process command for a match on the name of the post-processing command and method (external). The $fax_status1 command line must have a status of 4 (awaiting post-processing) before the post-processing program can process it. After accepting the request for processing, the post-processing program should change the status to 5 (post-processing in progress). Upon completion, the status should be changed to 6 (completed).
Infobox postprocessing can be used for operations such as calling an external DLL or program from an infobox. The user profile or user job properties file referenced from the FS file must have one or more $script_locn commands to locate the infobox file(s). Your infobox logic must finish by transferring to state 191 (IIF_PROC_COMPLETE). You may assign a value (minutes) to POST_DELAY to cause the FS file to be retried, or to POSTPROC_FAIL to make it fail (with limitations in a job admin context). Voice operations within your infobox sequence will be ignored, and transfer to any other state may cause unpredictable results. The FS_... system variables contain specific data pertaining to the active FS file, but any valid system and control variables may also be used. Any program or DLL called from an infobox sequence other than types internal or infoboxend should not attempt to modify the FS file other than via the FS... variables.
Although you may specify multiple post-process operations, some limitations apply: only the first infobox or infoboxall postprocess is performed, and only the first infoboxend postprocess is performed.
Default: none (optional feature)
$fax_post-process "mailusr" internal