An employee replacement wizard would certainly help (including not only replace but also when a position is closed) but does not allow for the definition of more than one structure (such as one for office structure, matrix hierarchy, asset location, etc.).
Your proposal of using a wizard to simplify/secure the operation also holds for managing the abstraction layer. It is just the same as defining your organizational structure (chart) with all the positions, headcounts and descriptions if you like but without putting a name (employee-name) on it first. Then, when you create/modify the employee it is just a matter of putting the employee at the right place in the organizational chart. For those who wish, you could imagine the same principle for office allocation, membership to some committee or whatsoever. The additional complexity is to be weighted against the additional security you can achieve. You can assign the modification access rights of the structure to a special role whereas the allocation could be performed by lower levels. I agree however that such an approach may be most attractive to medium to large size organizations. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=51130#51130 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
