Generic Pdf Template and Pdf (abstract)
From UG
(→Design) |
(→History) |
||
| Line 75: | Line 75: | ||
* http://mantis.jaguarfreight.com/mantis/view.php?id=1756 | * http://mantis.jaguarfreight.com/mantis/view.php?id=1756 | ||
| - | ==== BA ==== | + | ==== BA 1756 ==== |
see [[#Validation feature]] | see [[#Validation feature]] | ||
| - | ==== SA ==== | + | ==== SA 1756 ==== |
Revision as of 18:23, 20 May 2010
Contents |
Classified As and Parent Mantis
- Classified As: (abstract) component
- Parent Mantis: 1755
Business Requirements
BR: Validation feature
Main need: How to predict in advance if specific value can fit on pdf and warn user
For example, warn user that "AIRMARK OCEAN & AIR LOGISTICS" value can not fit onto space allocated on pdf.
They want to see "as they type" when they exceeded space
This feature has not been implemented yet. See considerations below.
1) this can not be predicted easily in advance (before pdf generation) because characters have different width. Or we can calculate this based on specific font and known width of each symbol?
2) Show warning as they type
3) Show warning after they click on "genrate report"
Systems Design
Summary
Every pdf has a pdf template. See Introduction into Ops Pdfs Module#3 step process.
Classification of widgets on pdf template and How each widget must be defined in spec
Pdf Template serves several purposes (and have related classification of widgets). Respectively we have 3 cases of what should be specified in the design and how.
EXISTING system fields
(CT record mostly)
(Examples: Shipper, CBM)
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
NEW fields
(that we do not have in the system) that would appear on pdf (Examples: pick up time; comments )
In this case there must be a full definition
Data manipulation
(Examples: convert CBM into CFT; insert new lines into "pdf commodity table"; move line up)
Full definition required
Look And Feel
Layout of fields on template should mimic same on pdf as much as possible.
