CT.Ocean.PickupOrder

From UG

(Difference between revisions)
Jump to: navigation, search
(Questions:)
((Replaced content with 'Category:Ops Pdfs Old This is original old spec. Content has been hidden. To view - see history.'))
 
(18 intermediate revisions not shown)
Line 1: Line 1:
-
== Exec Summary ==
+
[[Category:Ops Pdfs Old]]
-
''TBD''
+
This is original old spec. Content has been hidden. To view - see history.
-
 
+
-
 
+
-
 
+
-
== Intro ==
+
-
 
+
-
 
+
-
[[Image:CT.Ocean.PickupOrder.pdf.jpg|thumb|CT.Ocean.PickupOrder pdf]]
+
-
 
+
-
* See [http://mantis.jaguarfreight.com/svn/ct2/SS/ops/pdfs/ocean_indiv_ct/Pickup_Order/v3/pdf1.jpg Pdf example with sections]
+
-
 
+
-
* Link to parent Mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=587
+
-
* Link to [http://docs.google.com/Doc?id=dgwxtwcq_25c37qrkhf&hl=en  QA reports] for this component
+
-
 
+
-
== Section A (logo+addr) ==
+
-
 
+
-
 
+
-
a1] This is a standard Logo + Jag address pdf banner.
+
-
 
+
-
== Sec B (CT fields, etc) ==
+
-
 
+
-
b1] This section have a number of fields pulled from CT/group. See [http://mantis.jaguarfreight.com/svn/ct2/SS/ops/pdfs/ocean_indiv_ct/Pickup_Order/v3/secB1.jpg this image]
+
-
 
+
-
b2] Note:
+
-
*green dot means - this field is read only on template
+
-
*orange dot means - in case of [[group generate]] this field comes from CT from which this template is generated
+
-
*blue dot means - in case of group generate this fieldmust show accumulative info from all selected CT
+
-
 
+
-
b3] kg/lb dropdown must convert on the fly
+
-
 
+
-
== Section C (PO/SKU table) ==
+
-
 
+
-
=== <span style="color:red">Questions:</span> ===
+
-
<div style=" border:thin solid red;">
+
-
 
+
-
a)  How many PO/ItemCode textboxes should be on template? (Right now  system produces as many as there are in CT. )
+
-
  Note: template with today's fonts & fields can contain 10 rows х 3 cols = '''30''' ''(andrei, 18/06/09)''
+
-
 
+
-
b) Do we need ability to add additional PO/ItemCode textboxes on template?
+
-
 
+
-
c) If there are more PO/ItemCode in CT than we can display on template, what to do with the rest?
+
-
 
+
-
d) If there are more PO/ItemCode pairs than we can fit on the first page on pdf do we need second page? If yes then What is the 2nd page design?
+
-
 
+
-
e) For Group generate case how to form list of PO/ItemCode from multiple CTs? What if it is very large?
+
-
 
+
-
</div>
+
-
 
+
-
== General requirements ==
+
-
 
+
-
=== Pdf template(zul form) layout and size ===
+
-
 
+
-
* Must mimic layout on pdf
+
-
* Size of textboxes must reflect space on pdf
+
-
 
+
-
=== Textarea input validation ===
+
-
 
+
-
Q: How to handle situation when string entered/populated into 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)
+
-
* validator must be added that "prevents user from entering more" OR "displays pop-up indicating that max reached". Any other alternative ideas?
+
-
 
+
-
== Dev History ==
+
-
 
+
-
Specs folder with all versions/history: http://mantis.jaguarfreight.com/svn/ct2/SS/ops/pdfs/ocean_indiv_ct/Pickup_Order/
+
-
 
+
-
--[[User:Alex|Alex]] 23:38, 17 June 2009 (UTC)
+
-
 
+
-
[[category:OpsPdfs]]
+

Current revision as of 19:34, 5 June 2010


This is original old spec. Content has been hidden. To view - see history.

Personal tools