On 20 Dec 08:17, Oscar Alvarez wrote: > El 20/12/13 06:01, Cédric Krier escribió: > >On 19 Dec 21:53, Oscar Alvarez wrote: > >>El 19/12/13 19:27, Cédric Krier escribió: > >>>On 20 Dec 01:19, Cédric Krier wrote: > >>>>On 19 Dec 19:09, oscar wrote: > >>>>>On 19/12/13 18:41, Cédric Krier wrote: > >>>>>>On 19 Dec 13:54, oscar_alvarez wrote: > >>>>>>>Hi, Devs > >>>>>>> > >>>>>>>I want to propose add new model "company departments" to company > >>>>>>>module, > >>>>>>>this model lets arrange employees for sections: stock, human resources, > >>>>>>>maintenance, sales/marketing, so it for to be used in reports of > >>>>>>>timesheets > >>>>>>>or worktime, and the in the future for a official staff and payroll > >>>>>>>module, > >>>>>>>to including a CRM module, etc. > >>>>>>> > >>>>>>>What do you think about? > >>>>>>For me, it is bloated if the only usage is reporting for timesheet. > >>>>>> > >>>>>When a company has more of 300 employees, this topic is not trivial, > >>>>>for the managers the reports in a ERP is a important factor for that > >>>>>they take to decision of get it, so if for example a manager need to > >>>>>view a report sales for departaments (because each employee is > >>>>>related with a department "M2O") with a this model is easy to create > >>>>>a report. > >>>>Reporting is not really the goal of Tryton. > >>I am not talking about of introduce a new report, i am talking the > >>add a feature for classification of employees > >for the only purpose of reporting. > > > >>same way like category parties, > >Not exactly the same because it is M2M and so very flexible. > >But indeed, it should not have been introduced because it is bloated, > >that's a early mistake. > > > >>category products, > >That's different because product categories are to share common > >properties. > > > >>so ¿then for this reason the category of > >>parties is it bloated? I never has used this feature, but I think > >>that maybe is important, for any company, not for all companies, so I > >>don't see where this feature (category of party) reduce flexibility? > >As I said, it is a mistake but at least it is flexible. > > > >>>Also for me, there are so much company structure that forcing to have > >>>one is bad for the flexibility of Tryton. > >>> > >>>https://en.wikipedia.org/wiki/File:%22Org_charts%22_comic_by_Manu_Cornet.png > >>> > Cedk, I have developed the company department model add to company > module, and this moment I am using with several modules: > > CRM: Let's direct the request customer to specific people in a > department (department is a domain for select the employee) so and it > brings a clear vision of charge/quantity of work for each department, > so it could to let view performance for employees/departments. > > Maintenance Module: When we create a new request order (works > maintenance order) is necessary to define which department the work > requested is required. > > Staff Module: This module use the deparment field in Employee Form, > for to classify its and for example to define domains by employees, > that setting Workday, Overtime, Type Payroll, to apply or > preliquidations, etc, and any the industrial companies using a > indicators of HSE by departments > > Yes I know this modules aren't officials, but I am working (tesing > code) for that both staff and CRM mainly it being including in the > releases in the future but the piece key that is missing is company > department. > > In addition, in the timesheet would be useful. > > It is not just one reason, there are severals reasons.
No, you are talking about modules that doesn't exist. And for most of your reasons, I have many doubts about the design and the choise of your department model. More over, you even don't consider one of my main concern about the different organizations that exist for companies. So your solution is not flexible at all. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpozSTA9rSuE.pgp
Description: PGP signature
