Common specs for pdfs

From UG

Revision as of 23:48, 21 June 2009 (edit) Alex (Talk | contribs) (→Multipage logic) ← Older edit		Revision as of 23:48, 21 June 2009 (edit) (undo) Alex (Talk | contribs) (→Multipage logic) Newer edit →
Line 102:		Line 102:
	*1] In some cases document would consist of more than one page. Examples:		*1] In some cases document would consist of more than one page. Examples:
-	** [[#Instructions_page]] is enabled	+	** [[#Instructions page]] is enabled
	** [[Commodity table]] section is too large to fit on 1 page		** [[Commodity table]] section is too large to fit on 1 page
	** [[TOC]] is too large to fit on 1 page		** [[TOC]] is too large to fit on 1 page

---

Revision as of 23:48, 21 June 2009

Contents 1 Standard Header 1.1 Domestic vs International Address 2 Standard Labels boxes etc 3 Date and Year 4 Prepared by 5 Textbox or Textarea input validation 6 Pdf zul template layout and size 7 Commodity table section 7.1 Pdf Look and Feel 7.2 Functionality 8 Common bugs / changes 9 PO logic 10 Instructions page 11 Multipage logic

Standard Header

It consists of:

• Jag Office Logo (left)
• Jag Office Address (right)

Domestic vs International Address

• 1] We need radio box on template that gives choices: Domestic and International. If Domestic then Address in top right corner must come from login operator office and Logo must be for that office If International then Address in top right corner must be Jaguar NY and Logo must be for Jag NY

• 2] Below listed the only documents that require that:
  • sales pdfs
  • arrival notice

Standard Labels boxes etc

• [lvb0] Most documents share same “Standard Labels, Values, Boxes” style
• [lvb1] All labels must be bold and have ":" after them
• [lvb2] all values in boxes must be left aligned. They should start not immediately after the vertical line but after some margin.
• [lvb3] all labels must be - all capital letters
• [lvb4] all labels must be on a gray background
• [lvb5] example link: TBD
• [lvb6] exact CSS definitions link: TBD

Date and Year

[dy1] Must be always in the following format (Example): 15 May 2009

Prepared by

• [pb1] Must be always at the bottom of the page (on every page?) and in the following format (Example): "Prepared by: Robert Link "

Textbox or 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 zul template layout and size

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

Commodity table section

Pdf Look and Feel

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

• 2] comtable needs vertical lines but not horizontal lines

• 3] comtable needs lines around it - it must be "in the box"

• 4] TOC must always extend to the bottom of the page regardless of how many lines are there

• 5] all totals in TOC (Table Of Charges) must be bold

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.

Common bugs / changes

• 1] correct: CBM, wrong: CB
• 2] correct: PCS, not HU (table header)
• 3] correct: "TOTAL:", not "TOTALS:"
• 4] correct: PICK-UP / XXXX wrong: PICK UP/XXX
• 5] HU on pdf not aligned vertically
• 6] print: Marks & Numbers, not: "CONTAINER NR"
• 7] no need for "AS AGENTS FOR:" on pdf footer (footer that has name/signature/date)
• 8] replace "FOR DELIVERY TO:" with "DELIVERY TO:"

PO logic

Added: --Alex 23:13, 21 June 2009 (UTC)

• PO list comes into template from Commod Table (from one or multiple CTs if Group Generate)
• pre-fill PO field on template based on this logic:
  • if one PO then display it
  • if 2 PO then display both separated by ",". Example: a112233, a1234
  • if more than 2 PO then display first two separated by "," and "++" after . Example: a112233, a1234, ++
• display only first 30 chars on pdf and ignore the rest, do not display any errors
• on template next to "P.O. Numbers:" add label in red "(max 30 chars will be displayed on pdf)"

Instructions page

created:--Alex 23:28, 21 June 2009 (UTC)

• 1] Some documents have so called "Instructions page" (formerly "Page 2").
• 2] On template it is represented by checkbox and 1 page large teaxtarea
• 3] on pdf this would always print as last page
• 4] on pdf text must be surrounded by a single line (be printed inside rectangle)
• 5] at the top of this page doc header must be printed

Multipage logic

created --Alex 23:28, 21 June 2009 (UTC)

• 1] In some cases document would consist of more than one page. Examples:
  • #Instructions page is enabled
  • Commodity table section is too large to fit on 1 page
  • TOC is too large to fit on 1 page

• 2] Print "Page x of y" - at the top right below header on each page
• 3] Print "see next page" - at the bottom right
• 4] print special header for each additional page (see specific doc spec)
• 5] print special footer for each additional page (see specific doc spec)