El 26 d’abril de 2012 11:33, Cédric Krier <[email protected]> ha escrit:
> > And what is in the *real* world a "Timesheet Sheet"? For example, it is a form with all entries of employee (or work/customer) for each day with the sign of responsible wich is presented to Customer if there are conflicts with the hours of service. It's a use case of a Cleaning Service company. But it's not my current case (it's an old project in OpenERP)... Therefore, when I have it I will think about it. > Yes, that's the other alternative. I thought that add an 'state' field > > (maybe a workflow?) to timesheet.line could be a difficulty for future > > developments. But it's the simplest solution. > > Indeed with the current workflow design it will be quite simple. > But I'm not sure it deserve a workflow, it could be just a checkbox that > the user can edit (+ a wizard to update a list). Ok. For my current use case it's enough so I will implement it. I proposed the other option because I thought that anybody could have a more complex validation process. But if it's not the case, It's easier to me. > In this case, I think the best is add this field and wizards to confirm > > lines in the 'timesheet' module. > > Why? I think it can be well done in a new module: timesheet_validation? Because I thought it's easier and clear because the timesheet fields will have a conditional readonly in it's main definition (and the default behaviour: timesheet validated by default or not, could be configurable in the company). But if it isn't a general requirement, the best way is in a separate module. I will do in the 'timesheet_validation' module. Thanks! -- Guillem Barba http://www.guillem.alcarrer.net -- [email protected] mailing list
