When you declare an employee you can add a category to an employee. In the hr_contract module, a contract uses a reference to the partner->function, a flat table of functions. It seems logical that a contract should hold the employee's function as this is likely to change over time. But shouldn't the employee->category be used instead because this supports hierarchy which can be consulted in the employee structure? A conflict would however arise with the category field in the employee object which does not depend on a contract. For me it is therefore unclear how to reflect the employee's job position which may vary over time. Another argument why the partner function is inadequate is that this naming is more used like a title for the partner contacts and not under control of the company. An option could further be to let the contract function refer to a (to be created) company organization chart so a contract could be linked to a certain position. Or is this the aim of the employee->category field?
Any opinion on this topic? -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=50789#50789 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
