Ok, so the list is a should be a dropbox in your app where you can pick the service or the pieces in you invoice? I guess it is now an kind of check list you receive to create the invoice?
There is a lot of wording in your business you could start by simplifying all the concept the use and figure out what it refer to in a simple invoice app, like invoice and item, etc. To me you need a invoice table structure for your service order, you need item table for all the service your business provide that will serve as a lookup table to make sure employee don't spell service or product differently from time to time. Then you need to a complex form to make all this working together with consumer table, etc. Some time you don't want to make a system so custom that only well trained person can understand. Paper system tend to be not well organize and thought because relation between stuff wrote there is just the sheet of paper, no multiplicity and well define relation with the rest of the thing. Things get added overtime and they just add a check box for instance and when you try to deconstruct all this you discover that there is many missleading practices that you should not allow in a computing system. I would not try to make my system do the exact workflow process then the paper because it will surely lead to a poor db and app design. It is difficult to help you with the design because there a lot of work that I can really do for you (missing info and lack of knowledge of you organisation). But you should start by create a db schema that is normalized and follow invoice system best practices before the thinking to your app. Don't think how you will implement you app at first because it will bring you to make mistake in you db schema. Once you have a good db schema (that you can pick on the web directly, they are mostly good because invoice systeme is a big classic) you can start to implement the app and start feelling nervous because you don't know how to do it :) When there is only to find a way to create a complex form, if you ask the right question here you will get the exact pieces of code you need. There is also the web2py slices that are really good. Richard On Tue, Aug 5, 2014 at 3:27 PM, Jesse Ferguson <ifl...@gmail.com> wrote: > The service order on the right is what is completed in the field by the > techs. (The part they bring me). The form on the left is what our company > calls a Work-Up. The work up Is created by me by taking the service orders > information and the information from a rolodex card. The rolodex card (not > pictured) contains just basic information about the company and location > (mileage to charge and hours). then i scan them both just as pictured and > send them to main office. > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
