Processing is specified by means of a $post_process or $fax_post-process command. The infobox sequence is called after the FS file has been successfully sent or finally failed. It is not called after a failure which will result in a retry, unless the keyword infoboxall is used.

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.

Typical applications include:

status: you can pass an identifying variable to a DLL which updates your database with the information about the final disposition of the transmission.
logging: you can carry out custom logging of outbound transmissions and suppress the normal CopiaFacts DBF log file.
confirmation: you can originate an e-mail reporting the result of the transmission, by writing an FS file from a $type FS infobox. See the examples for $type FS for more details.

Variables defined in the FS file (with $var_def) are available at pre-process time, as are the standard cover-sheet variables such as ROUTETO. In addition you can set the FS_INDEX variable to select one of the $fax_filename lines (base 1) and then retrieve its filename and other attributes using the other FS_I... variables described in Appendix D.

Additionally, the set of OC_... variables provide full information about the outcome of the fax attempt. Note that some of these variables may be empty if the FS file is rejected before an attempt has been made to send it.

In your post-process, you can specify that the FS file should be retried, by setting the system variable POST_DELAY to the number of minutes to delay. This value is ignored if the FS file is already scheduled for retry, and in this case the delay already determined from the retry parameters will not be changed. Setting POSTPROC_FAIL to any non-empty value will force the failure of the FS file, with an outcome code of 82. This overrides POST_DELAY if both are used. Both of these variables are also ineffective if the infoboxend postprocess type is specified, since your infobox sequence will not be called until after the FS file has been written. Currently, these variables cannot be used (and are ignored) in conjunction with Job Administration.

If the user profile specified by $fax_user cannot be loaded, then the system attempts to load the default user profile for the line instead. If this also fails, infobox post-processing is skipped and the FS file is moved to FAIL.