© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hello,
Here is a list of things to improve in trunk:
1. Develop distinct objects for all different type of cases:
- crm.meeting
- crm.lead
- crm.opportunity
- crm.phonecall
- crm.claim
- crm.fundraising
- crm.job
All these objects must _inherits from crm.case. Put standard fields in crm.case and others, more specific fields in each particular objects.
-> note that crm.bug has been removed from the crm module, see notes bellow.
Adapt the mailgateway definition, so that it creates a special kind of object (not a crm.case). So, in the mailgateway, you can choose which object it will create. Adapt the mailgateway script, but also the mail gateway definition as a client form.
2. Remove the domain related to the section of each menu/action. We don't need to use domains anymore as each type of record is set in a separate object.
3. The section on a crm.case must not be required anymore. We plan to use the same section for different type of cases. As an example, in a company, you may have the following structure in the section:
- Department A
- Department B
A lead from "Department A" will, most of the time, evolves to a business opportunity of "Department A", then evolves to a sale.order of "Department A"
4. In the module sale_crm, add a section_id, not required, on sale.order. When a business opportunity is converted to a quotation, the section of the sale.order created must be the one of the business opportunity.
5. Develop a module crm_project. Add two objects in this module:
- crm.project.bug
- crm.project.feature (For managing Feature Requests)
These two objects _inherits from crm.case. They add a "project_id" field, which is not required on the object, but required in the view.
-------
As to better understand these requirements, you can have a look at the attached file that described the new interface of OpenERP, v5.2. When the user will go the "Sale" application, he can choose a context (top-left) like "Department A" and everything is filtered according to this section "Departement A". It also fits well with the new improvements in trunk where a crm object (like crm.lead) can not be changed to a section for crm.business opportunity. (Now, in v5.2, a lead generate a business opportunity -> we keep traceability of all things on a record).