Yeah, kind of like the existing Timesheet and TimeEntry entities
(which related to WorkEffort, InvoiceItem, etc).
-David
On May 4, 2009, at 9:22 AM, BJ Freeman wrote:
sounds like a timekeeping function
Erwan de FERRIERES sent the following on 5/4/2009 7:54 AM:
Don't worry Hans, we've been looking before. One of the goals is
also to
keep entities together, and be sure that we will try to reuse a lot.
But for this new feature, we need to create specific entities, like
* ClockingGroup (an employee belongs to a group. A group is a set
of rules)
* ClockingAnomaly which is an error in the clocking. For example, an
employee is missing, so we have to keep this information, the
person who
validates the absence, the time of noticing, the reason, etc...
* PartyClockingGroup which will keep "sums" of working time by
weeks or
months
Hope that will clarify the needs !
Hans Bakker a écrit :
In ofbiz always look what can be re-used before you create new....
clocking in and out looks like a workeffort with a start and end
date/time?
please also explain what anomaly and group should do?
On Mon, 2009-05-04 at 15:58 +0200, Erwan de FERRIERES wrote:
Dear all,
We have to develop an application based on OFBiz. In this
application, there will be a system for clocking in/out for the
employees.Once this new feature will be created, it will be
submitted
to the community.
So I just want to give the right name to the entities, to be sure
it
is understandable for everyone.
We were thinking of :
* ClockingEntry (one entry)
* ClockingAnomaly (one anomaly)
* ClockingGroup (a group of rules)
If those names are Ok for you, then we will keep with them. If
you've
got a better idea, don't hesitate to tell me !
Cheers,
--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.
