Information Systems:Making changes to Jetform templates - Revision history

Norwinu: /* How-to: Making changes to templates */

2018-03-15T20:23:16Z

How-to: Making changes to templates

Norwinu: /* How-to: Making changes to templates */

2018-03-15T20:22:05Z

How-to: Making changes to templates

Norwinu: /* How-to: Making changes to templates */

2018-03-15T20:21:40Z

How-to: Making changes to templates

Norwinu: /* Presentments */

2018-03-15T20:20:29Z

Presentments

Norwinu: /* Location of template files */

2018-03-15T20:18:57Z

Location of template files

Norwinu: /* Location of templates files */

2018-03-15T20:18:37Z

Location of templates files

Norwinu: /* Form types */

2018-03-15T20:18:15Z

Form types

Norwinu: /* Form types */

2018-03-15T20:17:19Z

Form types

Norwinu: /* Form types */

2018-03-15T20:16:46Z

Form types

Norwinu at 20:13, 15 March 2018

2018-03-15T20:13:13Z

@@ Line 62: / Line 62: @@
 * 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 be eventually be the same name. It is best to compile them to different names first, copy them to their destination folders, and rename them there.
+* 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.

@@ Line 62: / Line 62: @@
 * 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. If this is a purchase order or invoice, take caution with the filenames, as the 3 (one for each presentment) will have to be eventually be the same name. It is best to compile them to different names first, copy them to their destination folders, and rename them there.
+* 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 be eventually be the same name. It is best to compile them 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.

@@ Line 61: / Line 61: @@
 * 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.
+* 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. If this is a purchase order or invoice, take caution with the filenames, as the 3 (one for each presentment) will have to be eventually be the same name. It is best to compile them 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.

@@ Line 10: / Line 10: @@
 ==Presentments==
-A presentment, in Jetform terminology, is an output type. We use three: printer, PDF, fax. IFD files are always compiled for a specific presentment (actually, you can select multiple at one time, but I haven't tried doing it this way).
+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:

@@ Line 46: / Line 46: @@
 ==Location of template files==
-* IFD files can be stored anywhere (Jetform Output Designer saves locally on desktops, and there are also copies on Lucy).
+* 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 print: {{unc|\\lucy1.unipharm.local\c$\JetForm\Central\ASW\480b\Forms|\\lucy1.unipharm.local\c$\JetForm\Central\ASW\480b\Forms}}

← Older revision		Revision as of 20:18, 15 March 2018
Line 40:		Line 40:

	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).		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.		'''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.

@@ Line 39: / Line 39: @@
 |}
-The form names are 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).
+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).
 '''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.

@@ Line 24: / Line 24: @@
  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 for specific presentments (if applicable) are described below.
+The current form types and their different names (MDF filenames) for specific presentments are described below.
 {| class="wikitable sortable"
@@ Line 30: / Line 30: @@
 ! Form !! Form name for print !! Form name for PDF !! Form name for print
 |-
-| Purchase order || DMR512J || DMR512J || DMR512J
+| Purchase order || Dmr512j.mdf || Dmr512j.mdf || Dmr512j.mdf
 |-
-| Invoice || DMR344J || DMR344J || DMR344J
+| Invoice || Dmr344j.mdf || Dmr344j.mdf || Dmr344j.mdf
 |-
-| A/R Statement || ARR512J || ARR512E || ARR512F
+| A/R Statement || ARRST51J.mdf || ARRST51E.mdf || ARRST51F.mdf
 |-
-| Narcotic control form || NCRP001J || NCRP001E || NCRP001F
+| Narcotic control form || NCRP001J.mdf || NCRP001E.mdf || NCRP001F.mdf
 |}