methodology
2 posts • Page 1 of 1
methodologyI think that it would be good to provide a number of standard methodologies with the invoicing module. To make the system easier to understand, it would be great if there was space to add a short description of the purpose and requirements of each methodology.
I am not sure whether i have understood what your sample does, but it seems to expect developer time to be allocated to the agreement. We have a number of services that are regular payments within specific allocation of work to the contract. (For example a hosting contract with a monthly fee, but no time commitment). It would be good if we could collect a set of common requirements and make these part of the base module.
Re: methodology
It is complicated in a matter that the code is being generated from entered values. So even if somebody would want relatively simple methodology one would probably want invoicing on specific other OpenERP data model. So consequently they (methodologies) should be created by some sort of wizard, where one can choose predefined methodology template and define only a data model. Which of course is possible to develop, but is pretty complicated and for now is a major improvement. It should probably be implemented as separate module.
Basically it invoices partner based on the language (defined in partner section) the services are being done for him. For French speaking customers 20% discount are being applied.
It is pretty simple task for Invoicing module. We are considering this as an example, because it is common task.
It could be implemented as a demo data. I have no idea how to export data from OpenERP as an XML to be able to use it as a demo...
2 posts • Page 1 of 1
|
Copyright © 2001 Alistek Ltd., ALL RIGHTS RESERVED