This Zetafax technical note applies to:
- Zetafax version 17.0 and earlier
When using Zetafax with an application using the Zetafax Automation Toolkit for submitting faxes, manually resending a failed fax using the Zetafax Client results in just the first page or the first few pages being resent.
Viewing the resubmitted fax in the Zetafax Client OUT window also shows that the fax has been truncated, with later pages omitted from the fax.
When a Zetafax-enabled application sends a fax using the Zetafax Automation Toolkit, it can supply one or more files containing the fax image to send. The Zetafax Server converts these files into the correct format for sending, combines them together, then sends them as a single fax.
When you resend a fax, the Zetafax Client copies the image files into a new message, then submits this to the Zetafax Server for sending.
On Zetafax version 17.0 and older Zetafax systems, if the submitted file was not in the native file format used by the Zetafax Server, the Zetafax Client converted the file to the native format when resending a fax before submitting it to the Zetafax Server. However this conversion was only performed on the first image file, and any further image files were omitted from the resent fax.
The issue only affects image files requiring conversion, and so only occurs on systems using Zetafax-enabled applications to submit faxes which include multiple image files.
An update for the Zetafax Client is available which corrects this issue. It changes the behaviour of the client when resending a fax from the OUT window so that it copies the original message file(s) without performing any additional conversion process.
This issue is caused by a fault in the Zetafax Client application when forwarding or resending faxes, which has now been corrected.
Last updated: 14th April 2016 (GW)
Keywords: API, Automation, Toolkit