CT.Ocean.PickupOrder

(Difference between revisions)

Current revision as of 19:34, 5 June 2010

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

@@ 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 ==
-See :[http://mantis.jaguarfreight.com/svn/ct2/SS/ops/pdfs/ocean_indiv_ct/Pickup_Order/v3/pdf1.jpg Pdf example with sections]
-== 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) ==
-=== Q&A ===
-a) How many PO/ItemCode textboxes should be on template? (Right now  system produces as many as there are in CT. )
-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?