Yes, that's an interesting point Hans. Bilgin: is planning before hand
what you had in mind?
My thoughts reading this were that the shift they are part of is
redundant information because they can specify the starting and ending
times as opposed to just a number of hours (using the fromDate and
thruDate). If you wanted to see a report by shift you should be able
to figure out the shift they are in. In a report or wherever the shift
information is used you could have that configurable or built in
("hard coded" if you will).
If being "in a shift" means that they are part of a group then a
PartyGroup that they have a membership relationship to would be a
better way to model it. That relationship can have from/thru dates so
they can change groups over time, etc as well.
-David
On Jun 3, 2008, at 7:27 AM, Hans Bakker wrote:
Hi Bilgin...still sounds a bit questionable because time entries are
after the fact...if you want to use it for planning, then workefforts
are more appropriate.
Regards
Hans
On Tue, 2008-06-03 at 16:07 +0300, Bilgin Ibryam wrote:
Hans,
Thanks for your answer.
I want to add a field which can be used to classify the time entries
based on time but not rate. And this field will be informative for
the
user, but not for the customer.
In industries where Shift work hours are used instead of standard
working day hours, the user can easily check only which shift he/
she is.
Also you can have for example the same rate for Day shift and Evening
shift, these fields are not related in most cases.
WDYT?
--
AntWebsystems.com: Quality OFBiz services for competitive rates.....
