|
Rendering
|
Previous Top Next |
|
Print to Fax
|
FACSys Printer Driver
|
Client-side (workstation) rendering unless the advanced client option to render locally is turned off.
|
|
e-mail to fax
|
FACSys Print Driver
|
Client-side (workstation) rendering unless the advanced client option to render locally is turned off.
|
|
File attachment from an email application or from AFM-SDK
|
from an e-mail gateway such as Outlook, SMTP, Lotus Notes, GroupWise
or from the Active Fax Messaging Software Development Kit. |
Server-Side rendering. Native application is launched to render the attachment. (eg MS OFFICE or ADOBE ACROBAT). Rendering will also occur if no native application is associated with the file type but the option 'Use the server's Outside In™ Rendering Services' is turned ON. If neither of these options are available, rendering will fail with the error "image sub-system failed to render the document"
|
|
Embedded codes in HPCL or PS files
|
from an application using print-stream embedded tokens. EG SAP, AMS, FileNet.
|
Server-side Rendering. This print process requires the optional FACSys (HPCL-PS) Renderer to convert the printer stream's embedded codes through the FXQ: port. You need to also install the FACSys Queue Monitor
|
|
|
|
|
|
TIFF G3/G4/MH
|
Intel DCX
|
|
PCX
|
HPGL2
|
|
ASCII Text
|
Basic-RTF Documents
|
|
BMP (1,4,16,256, 24-bit color)
|
Postscript Level 1 and 2 AND PCL5e w/ TrueType**
|
|
Microsoft Excel XLS
|
Lotus WordPro
|
|
Microsoft Write WRI
|
Adobe Acrobat PDF**
|
|
WordPad TXT
|
JetForm Central JFM
|
|
Outlook V-card
|
PowerPoint PPT
|
|
Lotus 123 WKS
|
Visio
|
|
Microsoft Word DOC, HTML, RTF
|
|
| - stop all the FACSys services and close the Desktop client from the System Tray
|
| - replace C:\FACSys\faxmngr.exe with the one included in the ZIP file
|
| - replace the C:\Windows\System32\imglib32.dll and C:\Windows\System32\FxPrinter.dll with the ones included in the ZIP file
|
| - edit the following registry key HKLM\Software\FACSys\ImageLibrary\ShellFlags and add 40 hexadecimal to the current value. For example if the ShellFlags are 0, make it 40 hexadecimal, if the ShellFlags are 8, then make it 48 hexadecimal and so on.
|
| - start all the FACSys services and test
|
| · | Purchase the Optional Outside In™ Rendering Service
|
| · | Download the FACSys-OutsideIn.zip file and install the Outside In™ engine
|
| · | Acquire and install a FACSys Outside In™ Rendering Service License from emFAST.
|
| · | When you install the FACSys fax server software, the Outside In™ Viewer technology can be optionally installed if you purchased this add-on feature. At Outside In™ core is a filtering technology that understands the file formats of more than 250 current and legacy applications, including the most popular word-processor, spreadsheet, database, bitmap, drawing and presentation formats.
|
| · | When you configure FACSys to use the Outside In™ software for rendering/printing fax file attachments at the fax server, you eliminate the requirement of installing the Native applications on the fax server. For example, if users will be attaching Excel documents to their outbound faxes and you configure fax server rendering using the FACSys print services (rather than the Outside In™ print services), then you must install Excel on the fax server.
|
| · | However, Outside In™ is a viewer program designed to provide a reasonable facsimile of the file content. Using Outside In™ for conversion is not as accurate as using the native application to obtain "What you see is what you fax" ("WYSIWYF").
|
| · | If your outbound faxing results are not being rendered accurately enough by Outside In™ then install the native application for the document type and set the rendering option in the FACSys Server Properties, rendering tab, to use the native application.
|
| · | An example of this would be the requirement to fax LEGAL, LANDSCAPE Excel file attachments. Outside In™ will tile them onto separate pages, but Microsoft Excel will render them properly.
|
| · | Similarly if you are rendering HTML documents you must consider that the variety of HTML viewers and display techniques provides differing results. FACSys uses Word to render HTML documents. Therefore you must ensure that the formatting of the file displays properly in WORD, before attempting to have FACSys render it.
|
| · | If you are planning to use the FACSys API to programmatically attach a created file it is preferable to submit a WORD or a PDF attachment rather than an HTML or an RTF attachment AND have WORD or Adobe FULL PRODUCT installed on the faxserver.
|
| · | FACSys fully automates the installation and configuration of the software's rendering services by doing the following:
|
| · | When you install the FACSys fax server software, a server-based FACSys Document Printer is created automatically. This printer outputs to a special port monitored by FACSys and is used for rendering file attachments on the server.
|
| · | If you purchase the optional FACSys Outside In™ Rendering Service, and install it along with the FACSys Outside In™ Rendering Service License, the installation program installs the Outside In™ Viewer files and adds the INSO path to the system PATH environment variable. As an alternative to installing document applications on the fax server, Outside In™ understands the file formats of more than 250 applications.
|
| · | When you install the FACSys Desktop client software, a local FACSys Fax Printer is created automatically. This printer is used by the client for "printing documents to fax format" and for rendering file attachments on the workstation.
|
| · | The Outside In™ installer files which can be purchased through your FACSys Authorized Reseller
|
| · | The FACSys Outside In™ Rendering Service License, which will be provided at no cost when you purchase the optional Outside In™ Renderer.
|
| · | The user must have a FACSys Fax Printer installed on their workstation. (The FACSys Desktop client setup program installs and configures the FACSys Fax Printer automatically).
|
| · | The user must enable the 'local rendering' option in their FACSys Desktop (this is the default setting).
|
| · | The applications in which the document attachments were created must also be installed on the workstation.
|
| · | Document attachments can be rendered into fax format at the fax server either by the native applications (e.g., Word, Excel) or by the optional Outside In™ Viewer technology.
|
| · | On the fax server, you must install the applications in which the document attachments were created. For example, to render Word attachments, you must install Microsoft Word on the fax server. Also, the application versions on the server must be the same as or greater than the application versions used at the FACSys clients.
|
| · | On the fax server, you must associate the FACSys Fax Device Manager service with a Windows account that has local administrative privileges. See Services Associations.
|
| · | In Pre 4.8 versions of FACSys the fax server's FACSys Document Printer was set to print to the FACSYS: port. Since FACSys 4.8 and on operating systems Windows 2000 and newer, this is now set to the FXS: port (The FACSys fax server setup program installs and configures the FACSys Document Printer automatically).
|
| · | To satisfy any initial program prompts that may display the first time an application is opened, you must do the following: Using the Windows account that is associated with the FACSys Fax Device Manager service, log onto the fax server. Then open and close every application that will be used to output/print attachments. Clear any 'automatic update' dialogs and change them to 'manual'
|
| 1. | On the fax server, launch Microsoft Word.
|
| 2. | Open an HTML file that WAS NOT created with Word. When you are prompted to use Word as your default HTML editor, answer NO.
|
| 3. | Close the Word application.
|
| 1. | On the fax server, you must associate the FACSys Fax Device Manager service with a Windows account that has local administrative privileges. See Services Associations.
|
| 2. | In Pre 4.8 versions of FACSys the fax server's FACSys Document Printer was set to print to the FACSYS: port. With FACSys 4.8 on operating systems Windows 2000 and newer, this is now set to the FXS: port (The FACSys fax server setup program installs and configures the FACSys Document Printer automatically.)
|
| 3. | From the FACSys Administrator program, display the server's properties and define the options on the Rendering tab.
|
| · | In addition to the supported file listed above note the following:
|
| · | If users will be attaching file types not supported directly by FACSys, you should implement the Outside In™ rendering technology.
|
| · | Server-based rendering of Adobe Acrobat PDF file attachments requires that your fax server operate under Windows 2000 or better. Also, note that you must install the FULL Acrobat product on the server (i.e., not the Acrobat Reader). As of the printing of this manual, Acrobat 7 or better is the minimum supported version required for server-based rendering.
|
| · | JetForm Central rendering by FACSys requires that you define the path to the JetForm Central program directory in the fax server's Registry. Detailed instructions are listed in a Technical Support Bulletin available from the FACSys Web site.
|
| · | When preparing a fax message, FACSys will render cover page text and document attachments using the exact or closest True-Type font available. If users require specific fonts, then you must verify that the fonts are installed on the sending fax server.
|
| · | By default, basic-RTF formatted attachments are rendered directly by FACSys without invoking the print services of another application. However, Word-RTF files generally include many extended RTF features. As a result, when Word-RTF attachments are rendered by the FACSys print services, the quality of the resulting faxed files may not be acceptable.
|
| · | Select the 'Microsoft Word (Rich Text Format)' option on the server Properties Rendering tab.
|
| · | Define a WordRTF registry key according to the Technical Support Bulletin on the FACSys Web site.
|
| · | Research has shown that the majority of FACSys customers no longer use HPCL files to submit attachments to the rendering engine. Therefore, with the release of version 4.7 SP4a the HPCL rendering tool was removed from FACSys in favor of a new Enterprise Fax Rendering System designed to accommodate more file types and produce better results using native application rendering.
|
| · | Any user who purchased FACSys 4.1 through FACSys 4.7 SP3 will receive the HPCL renderer at no cost.
|
| · | The HPCL rendering functionality will continue to be available as an add-on option at additional cost.
|
|
|
| · | a mail gateway.
|
| · | or through the AFM/SDK (Active Fax Messaging Software Development Kit, sometimes also referred to as an API – Application Programming Interface).
|
| · | or as an attachment to the FACSys Desktop Client (if 'render locally' is not enabled on the client).
|
| 1. | If, in the "FACSys Admin program, properties, rendering tab", no native applications are checked as being installed
|
| 2. | then FACSys will attempt to use the optional Outside In™ to convert the document.
|
| · | If 'application rendering' options are checked, FACSys will use the native application.
|
| · | (Note, these applications must be installed while logged in as the Account associated to the FACSys Fax Device Manager and opened at least once to clear any dialog screens that may launch on initial use).
|
| · | The option 'if the Application fails, use the server's Outside In™ rendering services' is CHECKED, FACSys will also attempt to render using Outside In™.
|
| 2. | Check the file content.
|
| · | If the file is HPCL:
|
| · | If the HPCL-PS renderer service is present, the HPCL attachment will be converted to TIF.
|
| 1. | If the file is a Postscript File:
|
| · | FACSys will first try the add-on HPCL-PS renderer. If the add-on renderer is present, and the file content is compatible with the add-on renderer (PS Level I and II), it will be converted to a TIF image and be submitted to the queue.
|
| · | If that process fails, and if Acrobat 7 or better full product (not just Reader) is installed, FACSys will launch Adobe Acobat, convert the PS file to a PDF file, submit to Acrobat and convert to TIF. This is the default process. This process will take longer than converting the document with the optional HPCL Renderer.
|
| · | If you have the renderer installed but don't want FACSys to ignore the renderer and want to FORCE the use of application rendering, then set the TryApplication Key to 2 as shown below:
|
|
|
| NEW TryApplication Key
|
| HKLM System\CurrentControlSet\Services\FaxManager\System\TryApplication
|
| TryApplication = 0 If renderer is installed use only the renderer for PS even though the application is installed
|
| TryApplication = 1 If renderer is installed then use it first. If that fails then use the application. This is the default
|
| 2-- Always use the app even though renderer is present
|
| 2. | If the file is an MS Office-type file, then FACSys will launch the native application, convert to a TIF image, and submit to the queue.
|
| · | Note that the behavior of MS Office attachments is different depending on what version of Office you have installed. There are known issues, for example, with PowerPoint attachments. MS Office 97 and XP behave one way, and Office 2000 behaves another way. To accommodate this, has introduced a new registry key as follows:
|
| Use the 'ShellFlags' DWORD key only if you have problems with Excel, PPT or Word.
|
| If you have difficulty with rendering RTF (Rich Text Format) documents (particularly those created by programs other than Microsoft Word), you may need to add a DWORD key as follows:
|
| · | HKEY_LOCAL_MACHINE\SOFTWARE\FACSys\ImageLibrary\WordRTF and set the value to 1.
|
|
|