Re: [Phpgwtimetrack-developers] invoicing

[Jeroen L. <je...@zw...>]

> I agree with your reasoning that the financial program should keep track
of
> what's been billed etc., but it just occured to me that it would if there
> were a bit set we could use it to prevent time track users from editing
> hours that already been processed.
>
> Maybe the new bit could be called 'approved' instead of 'processed' to
> clarify what it does.

Agree. I build a timetracking programs some years ago in Borland Delphi with
the same functionality in it. At a certain time the hours are processed and
users should not be able to change them after that. Kind of read-only flag.
So using the flag for that sounds good.
But ... I am not sure if am export should set this flag automatically. Our
normal procedure was:
1. users input their hours
2. manager makes output and checks the hours.
3. users correct their errors, e.g. if some had a meeting together, it's
nice if they write the same number of hours (on the same day) :)
4. manager makes final output for invoice and from that moment users are not
allowed to change their hours in that period.

So optional setting this flag sound best for me.

To prevent to many input errors I added a list of hours as inputed by
you/others (this week) below the hour input form.

I still think about something to make checking the hours easier.

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 devlist"
<php...@li...>
Sent: Saturday, November 11, 2000 9:48 PM
Subject: Re: [Phpgwtimetrack-developers] invoicing


> Thanks for the input Jeroen,
>
> I agree with your reasoning that the financial program should keep track
of
> what's been billed etc., but it just occured to me that it would if there
> were a bit set we could use it to prevent time track users from editing
> hours that already been processed.
>
> Maybe the new bit could be called 'approved' instead of 'processed' to
> clarify what it does.
>
> Let me know what you guys think,
>
> Camden
>
> ----- Original Message -----
> From: Jeroen Laarhoven <je...@zw...>
> To: phpgwtimetrack <php...@li...>
> Sent: Friday, November 10, 2000 3:01 AM
> Subject: Re: [Phpgwtimetrack-developers] invoicing
>
>
> > 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 :(
> >
>
>
>
> _______________________________________________
> Phpgwtimetrack-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpgwtimetrack-developers
>