[Vtigercrm-commits] [Vtiger development] #8476: Feature requests for next version of vtiger

[Vtiger development]

#8476: Feature requests for next version of vtiger
-------------------------+-----------------------
 Reporter:  uma          |      Owner:  developer
     Type:  enhancement  |     Status:  new
 Priority:  major        |  Milestone:  6.3.0
Component:  vtigercrm    |    Version:  6.2.0
 Severity:  Medium       |   Keywords:
-------------------------+-----------------------
 1. Fix address handling. It's a mess. Every module has a different way of
 storing address data in inconsistently named tables and columns. There is
 a bunch of hardcoded spaghetti code to enable address propagation between
 modules.

 I recommend taking a fresh approach to this and essentially creating an
 Address Module with one set of fields. These addresses can then be related
 to what ever modules are required. Propagation becomes easy and doesn't
 need to be hardcoded. This means that when a customer wants to change the
 format of the address fields (using vtlib) we won;t have to re-engineer
 loads of code just to get the "copy address" function to work. Or to get
 an Address passed between a Quote and a Sales Order...

 We have implemented something like this for a couple of customers and it
 seems to be working well. In an Organisation record they needed to store
 several different types of address such as Legal, Primary, Correspondence
 etc. and for a Contact they needed different types of addresses like
 Office, Home etc.


 2. Split the Create & Edit privileges of the Profile. I am frequently
 asked by customers that they want certain user roles to be able to create
 new records but once the record is saved that they are not then able to
 edit it. This is very hard to achieve right now.

--
Ticket URL: <http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/8476>
Vtiger development <http://trac.vtiger.com/>
Vtiger CRM