Common specs for pdfs

From UG

(Difference between revisions)
Jump to: navigation, search
(Rules)
(Common bugs)
Line 29: Line 29:
A: Only on last page.
A: Only on last page.
-
== Common bugs ==
 
-
* combug1// CBM, not CB  //
 
-
* combug2// PCS, not HU (table header)  //
 
-
* combug3// "TOTAL:", NOT "TOTALS:"  //
 
-
 
-
{| class="wikitable" border="1"
 
-
|-
 
-
! spec#
 
-
! descr
 
-
|-
 
-
| [combug1]
 
-
| CBM, not CB
 
-
|-
 
-
| [combug2]
 
-
| PCS, not HU (table header)
 
-
|-
 
-
| [combug3]
 
-
|  "TOTAL:", NOT "TOTALS:"
 
-
|}
 
[[Category:OpsPdfs]]
[[Category:OpsPdfs]]

Revision as of 20:20, 21 June 2009

Contents

Textbox / Textarea input validation

Q: How to handle situation when string entered/populated into textbox / textarea (Example: Special Instructions) above does not fit into the correspondent space on pdf?

A: In this case (as on any pdf) for each single or multiline textbox/textarea there must be a max number of characters/lines determined and:

  • displayed (next to the label) (example: "max 70 chars on one line, max 4 lines")
  • validator must be added that "prevents user from entering more" OR "displays pop-up indicating that max reached". Any other alternative ideas?

Pdf template(zul form) layout and size

  • Must mimic layout on pdf
  • Size of textboxes must reflect space on pdf


[com] Commodity table section

Look and Feel

[com1] (on pdf) unit of measurement that appears to the right of the number (example: 20CBM) must be printed only on the "Total:" line

[com2] (on pdf) comtable needs vertical lines but not horizontal lines

[com3] (on pdf) comtable needs lines around it - it must be "in the box"

Functionality

1] Totals for multipage:

Q: In case table is split between multiple pages, do we need to print totals line on each page or only on last page? A: Only on last page.

Personal tools