|
From: Jeroen L. <je...@zw...> - 2000-11-10 19:09:38
|
> Regarding the export, I am working on a page that currently prints > it's comma separated values to the browser as preformatted text and > includes those fields, but I currently don't have a form setup to > control date ranges and such. It should be easy enough to have it > save this info to a file somewhere instead. An easy temporary way to get things like a range is to let the user add them as GET params. We often do this with admin pages and then make one admin UI page with form input calling these admin pages with GET params. > I also have some other cosmetic changes and such that I will try to > get into CVS sometime today if I have the time. I have spent most > if the week working on them. I have also been fixing bugs in my running > version of phpgroupware, which is right now a mix of versions at > or around 0.9.3pre4. Some of the later changes they have been making > has made me want to hold back from trying to keep up with them, as > the changes are too many to keep up with. Perhaps if I make a new > sourceforge release soon, I should include my customized version of > phpgroupware as it's base? Any opinions welcome. Sounds very good. I got GW from CVS tried parts of it, but it was so buggy that I kept the 0.92 version and just modified (or better hacked :]) the addressbook in there so it does what I want for the moment: have a list with names, emails and tel-numbers. I am looking forward to your export page. Greetings Jeroen. = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Jeroen Laarhoven, Zwolle, Netherlands business: je...@we..., www.webbridge.nl private: je...@zw..., www.zwolnet.com = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = ----- Original Message ----- From: "Bob Schader" <bo...@pr...> Cc: "phpgwtimetrack" <php...@li...> Sent: Friday, November 10, 2000 3:29 PM Subject: Re: [Phpgwtimetrack-developers] invoicing > Regarding the export, I am working on a page that currently prints > it's comma separated values to the browser as preformatted text and > includes those fields, but I currently don't have a form setup to > control date ranges and such. It should be easy enough to have it > save this info to a file somewhere instead. > > I also have some other cosmetic changes and such that I will try to > get into CVS sometime today if I have the time. I have spent most > if the week working on them. I have also been fixing bugs in my running > version of phpgroupware, which is right now a mix of versions at > or around 0.9.3pre4. Some of the later changes they have been making > has made me want to hold back from trying to keep up with them, as > the changes are too many to keep up with. Perhaps if I make a new > sourceforge release soon, I should include my customized version of > phpgroupware as it's base? Any opinions welcome. > > Regarding a new field for "processed" or "exported", am I correct in > assuming that this should go into the job_details table instead > of the jobs table, so hours can be processed in an ongoing manner? > I had originallly thought the status_id field in the jobs table > could be used for something similar, but to track details separately > like this would require the field to be in the job_details records > instead. Adding the field to the table should be no problem, coding > might be a little trickier as to exactly when to set the field, etc. > > Also, is anyone familiar with quickbooks? Is the company data the same > for all setups? They have their "iif" format for exporting and importing > data, but I understand that data for jobs would need to be imported > separately into quickbooks before data for timesheets related to those > jobs could be imported. > > Regarding items previously mentioned, it seems I was wrong about our > company and users not wanting start and end times too! They have > recently > asked about the possibility of that. We should be able to do it with > the current tables, but the pages would need to be redone to support > the possible entry of more than one detail per job per day. This would > mainly affect the timesheets.php page and the editdetail.php page, as > far as I can tell. > > Jeroen Laarhoven wrote: > > > > > Next week I'm going to need to generate invoices based on the hours that > > > have put into time track. > > > > Next week we'll start using timetrack for our time tracking operational and > > the end of this month we also need something to generate so money ... > > > > > I would like to hear everyones thoughts on the best way to implement this. > > > For now, all I need to do is mark hours processed. Should I just add > > another > > > field named "processed" and set it's value to "1" when I do my export? > > > > In my opinion the export (flat table) should include: > > date + customer_name + job_name + employee(_name) + work_category + hours > > (with the combination of the first 5 field being unique) > > > > We will base the rate on the combination customer + job + employee + > > work_category. I think that most companies should be able to choose a rate > > based on the combination customer + job and the employee or work_category or > > both, maybe in combination with the total hours in a period. > > > > I would separate the financial functionality totally from time tracking. > > Using a standard format like XML or CVS for the export. A financial program > > (any or some PHP pages) imports the numbers and makes the bills. (This means > > that timetrack probably needs more then one export filter.) > > > > The financial program (or people) should know what has been billed, when, if > > paid, etc. That's why I (but who am I) see no reason why to set a > > 'processed' bit in timetrack. Even if the record has been processed in > > timetrack you're not sure it has been processed in your financial program. > > So let the financial program decide if something has been processed. > > Before you know timetrack will be extended to a financial program :( > > > > This is how we will probably process the hours: > > - make a timetrack 'hours export'. > > - import this on our local gw system (different server) and generate the > > invoice (appendix). > > > > So we keep the two completely separated. > > I'll make some PHP pages generating a invoice (appendix) out of the > > timetrack hours. > > > > So far my thoughts ... now back to work. > > > > Greetings > > Jeroen. > > > > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = > > Jeroen Laarhoven, Zwolle, Netherlands > > business: je...@we..., www.webbridge.nl > > private: je...@zw..., www.zwolnet.com > > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = > > > > ----- Original Message ----- > > From: "Camden Spiller" <ca...@ar...> > > To: "phpgwtimetrack" <php...@li...> > > Sent: Friday, November 10, 2000 8:03 AM > > Subject: [Phpgwtimetrack-developers] invoicing > > > > > Next week I'm going to need to generate invoices based on the hours that > > > have put into time track. > > > > > > Bob, I think I read one of your comments in the code that said you would > > > like use time track to export hours to Quickbooks and then mark the > > exported > > > hours as "processed" or something. I'm going to be doing a similar type > > > export. > > > > > > I would like to hear everyones thoughts on the best way to implement this. > > > For now, all I need to do is mark hours processed. Should I just add > > another > > > field named "processed" and set it's value to "1" when I do my export? > > > > > > Camden > > > > > > _______________________________________________ > > > Phpgwtimetrack-developers mailing list > > > Php...@li... > > > http://lists.sourceforge.net/mailman/listinfo/phpgwtimetrack-developers > > > > > > > _______________________________________________ > > Phpgwtimetrack-developers mailing list > > Php...@li... > > http://lists.sourceforge.net/mailman/listinfo/phpgwtimetrack-developers > > -- > ______________________________________________________________________ > Bob Schader > Computer Systems Manager > Product Design International, Inc. > 4880 36th St. SE, Suite 100 > Grand Rapids, MI 49512 > > Voice: (616) 667-2600 x104 > Fax: (616) 667-2692 > _______________________________________________ > Phpgwtimetrack-developers mailing list > Php...@li... > http://lists.sourceforge.net/mailman/listinfo/phpgwtimetrack-developers > |