Information Systems:Making changes to Jetform templates
Jetform Design and Template Files
With regards to Jetform forms, there are two types of files:
- .IFD files, which are design files
- .MDF files, which are the template files themselves
.IFD files are what you open in JetForm Output Designer, which is a desktop application that allows you to edit the look of the form using a GUI. Here, you can make logo changes, layout changes etc. IFD files are then compiled to .MDF files, and MDF files are what Jetform Central (the server on Lucy1) uses in its job definitions to transform spool data into forms.
Presentments
A presentment, in Jetform terminology, is an output type. We use three: printer, PDF, fax. IFD files are always compiled (to MDF) for a specific presentment (actually, you can select multiple at one time, but I haven't tried doing it this way).
When selecting a presentment for compilation, use the following:
- When compiling printer templates, use HP LaserJet 4 (PCL5) [hplj4]
- When compiling PDF templates, use Portable Document Format (PDF) [pdf]
- When compiling fax templates, use Fax - VSI-FAX GoldSeries [faxvsi]
I have verified that using an incorrect presentment type for a job type (e.g. using a printer presentment to compile a template for the PDF job) causes corrupted output files.
Form types
This table is a work-in-progress and hasn't been verified to be an exhaustive/complete list of all forms actively being used at uniPHARM.
The current form types and their different names (MDF filenames) for specific presentments are described below.
| Form | Form name for print | Form name for PDF | Form name for print |
|---|---|---|---|
| Purchase order | Dmr512j.mdf | Dmr512j.mdf | Dmr512j.mdf |
| Invoice | Dmr344j.mdf | Dmr344j.mdf | Dmr344j.mdf |
| A/R Statement | ARRST51J.mdf | ARRST51E.mdf | ARRST51F.mdf |
| Narcotic control form | NCRP001J.mdf | NCRP001E.mdf | NCRP001F.mdf |
The form names were named after the document-generation programs (RPG) that generate the correlating spool files (e.g. DMR344 is the ASW program that generates invoices for document distribution).
IFD design files don't need to follow a specific name, but conventionally they are named for the print template (e.g. DMR512J.IFD).
Important: As is indicated by the table, the purchase order and invoice form templates all have the same name. Thus, when compiling, take caution with the filenames. Stephen Aberle changed this for the other two form types so that this type of confusion could be avoided, but the issue still exists for the purchase order and invoice forms.
Location of template files
- IFD files can be stored anywhere (since Jetform Output Designer saves locally on desktops. And there are also copies on Lucy).
- MDF files are located in specific folders on Lucy:
For reference, the most recent copies of IFD and MDF files (along with test data) will be here: Jetform Templates
How-to: Making changes to templates
- Install JetForm Output Designer on your desktop.
- Open an IFD file to change.
- If a message shows up regarding default presentment, just click through it.
- Select File -> Presentments, and choose the presentment.
- Make desired changes. If they are logo-related, note that there may be multiple pages that need to be changed.
- Test the presentment using File -> Test Presentment. Locate the appropriate test data for the form type and select a test printer. This will use test data to demo the changes prior to compilation.
- Once the desired changes are made, compile the design into a template (File -> Compile). If this is a purchase order or invoice, take caution with the filenames, as the 3 (one for each presentment) will have to eventually be the same name. To avoid confusion, it is best to compile the templates for each presentment to different names first, copy them to their destination folders, and rename them there.
- If this is a logo change, select the option to embed the logo in template so there isn't a need to point to a separate image file.
- Copy the compiled template to the locations in the table above. Create a backup of the old one. Use the timestamps to validate the pending changes (e.g. determine which one is the most recent i.e. the one being replaced). The filename must be exact (e.g. Dmr512j.mdf), as that is what the job/route will look for. Match the case just to be certain.
- Reprint or regenerate forms from ASW to test the changes.