Makes sense. This is is probably the most straightforward way to model
it cleanly.
You probably want to make 2 EmployeeParts and still link them to same
Employee.
An EmployeePart is basically an employee for the entire time that he/she
works under the same regime.
A shift gets assigned to an EmployeePart.
Normally, an Employee has only 1 EmployeePart.
But depending on how much history you're loading in due to continous
planning (where xmas of last year might influece allocation of this
year's xmas), you might find that some employees had 3 or more parts
over that time span.
On 08-11-13 14:29, ns wrote:
Hi Geoffrey,
thanks for the reply and suggestions. I think I have found a work around
that works for me. I am going to consider a team switch as two employees and
make a planning for two separate employees. One ending at a certain point in
time and the other starting at a certain point. Afterwards I join the two
plans into one plan for that particular employee.
Kind regards,
Nick
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-forsee-mid-way-planning-team-cha...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users