Generic Pdf Template and Pdf (abstract)

From UG

Revision as of 17:44, 18 January 2010 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

Classified As and Parent Mantis

  • Classified As: (abstract) component
  • Parent Mantis: tbd

Business Needs

Business Requirements

Technical Specification

Summary

Every pdf has a pdf template. See Introduction into Ops Pdfs Module#3 step process.

See Figure ...


Classification of fields and How each fields must be defined

Template serves several purposes:

  • 1) to show EXISTING fields from the system (CT record mostly) that would appear on pdf (Examples: Shipper, CBM)
  • 2) to let user create some NEW fields (that we do not have in the system) that would appear on pdf (Example: pick up time)
  • 3) to manipulate data (Examples: convert CBM into CFT; insert new lines into "pdf commodity table")

Respectively to 3 cases above we have 3 cases of what should be specified in the design:

  • 1) since these fields has been defined already in the system as a rule (with just minor number of exceptions) these fields are to be considered (by default) on template to be identical (UI control type, UI control attributes, etc.). Example: Import Ref is a alphanumeric textbox, max length 30 chars defined on Gen Tab. On Pdf template where it appears it will be have same characteristics therefore on wiki spec we shall not repeat that it is alphanumeric textbox, max ....

Known exceptions:

    • 1a) value from more complex UI control (combobox or date) is displayed inside more simple UI control (textbox)
    • 2a) values from 2 controls are combined in one
      • in this case there must be a full definition
  • 2) in this case there must be a full definition
  • 3) full definition required

How to predict in advance if specific value can fit on pdf and warn user

....

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure: XXX

Questions and RFC

Known Non Critical Bugs

History

DB

Personal tools