Jasper Document Terms and Conditions

Jasper Reports is a 'Open Source' product used to design and print documents using laser style print format options to provide flexibility customizing reports and documents, with company logos, duplex printing, etc.
The Jasper Reports forms option can be activated and configured from the Customer Forms window on the Company Parameters.
Jasper documents are generated from the Server, outputting the form to the Client screen to enable printing.

Jasper reports uses the same program in the Document/Forms Mappings window for both A4 and letter size paper.

Terms and Conditions:

To print custom Terms on the back of selected documents, duplex printing must be employed.
To use double sided printing, refer to Customer Forms And Duplex Printing for more details on the duplex printer setup.

Terms print on the back of all Jasper forms that are setup to print duplex in the Customer Forms Document Mapping window of Customer Forms, where the duplex format can be triggered by adding a _D to the end of the relevant document names.
For example, Contract printing, default template is CounterDocument.jasper, so to use duplex with term, the mapping should be CounterDocument_D.jasper.

The layout of the Terms can be setup to print in one or two columns as defined in the Jasper Appearance and Formatting window of Customer Forms.
The content or text of the Terms is stored by language under resource property on the server as part of the contents of the Language Label file.

Maintaining the Property File for all Field Labels:

The property file controls the language labels and the text of the terms and conditions used for duplex printing.

Following are some key points:

1. Label files are named as convention of “reportLabel_xx_XX.properties” where:
   • xx represents Language code: lower case, two-letter ISO 639-1 standard
     Reference: http://www.loc.gov/standards/iso639-2/php/English_list.php
   • XX represents Country codes:upper-case, two-letter defined by ISO-3166
     Reference: http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htmhttp://www.loc.gov/standards/iso639-2/php/English_list.php

2. Label files for Windows OS are stored in c:\\scsbin\\jasper\\reports.
   Label files for Linux are stored in /usr/local/tsi/jasperreport/reports.

   Any new language/country code property file must be saved under these directories with the same language code and country code configured in the Standard Language Encoding or Alternate Language Encoding field in Jasper Appearance and Formatting window of Customer Forms.

   For example, if the encoding field value is “fr CA” there must be a mapping “reportLabel_fr_CA.properties” file in the directory for the corresponding server OS.

3. The default language files distributed with the software include “reportLabel.properties”, “reportLabel_en_US.properties”, “report_en_CA.properties”, “reportLabel_fr_CA.properties” and also “reportLabel_xx_XX.properties”

   Determining Label Field Sizes:
   The main purpose for the “reportLabel_xx_XX.properties” property file is to address any concerns regarding the maximum length of each label when designing the report layouts.
   This property file uses the standard release labels appended by many “123456789-“ strings after the standard values, to illustrate the maximum file size.
   This clarifies each specific label’s length, and can be used experimenting in the report design by changing the “Standard Language Encoding” to “xx XX” in the play area, and printing any document. The resulting document output will show the maximum length allowed for each label.

4. The property file must be open using a text editor that does not utilize a "line wrapper" as it is important to display the name=value pair separately for each line, especially when maintaining the script for the terms.

   There are two formats available for Terms as defined by the columns setting configured in the Jasper Appearance and Formatting window of Customer Forms,

   For a "one column term" the lines from LINE1=~~ to LINE70=~~ can be modified.
   For a "two-column term" the lines LLINE1=leftcolumnvalue… to LLINE35=~~… and RLINE1=rightcolumnlineone… to RLINE35=~~ apply.

   Generally when setting up the terms document, there is no definition restriction.
   The text can be copied and pasted from an existing word document.

   When formatting the text, the following apply:

   • An empty value can be allowed a line to force a blank line to print.
   • To start a new line within the text, a line break can be triggered by using “\n” at the end of the previous line.
     (back slash and small letter n without any quotes)
   • Jasper will auto wrap if there are more characters than fit on the line.
     All 35 lines or 70 lines (two column) do not need to be filled. The terms will auto wrap if for example there are only 3 lines of big trunk, it might turn out to be over 25 lines in the final results.
     

For best results, experiment with the text and label choices in designing the forms.