why should we use entity for contact.
--- Present system is using node content type for the all contact which is kind of unclear scenario
Problem :- the problem of this approach is that first our contacts are not a node or content, they are physical entity and different kind of business has different kind of contacts like suppliers, consultancy, legals etc which should be differently store and sorted. we could edit the field property for achieving this kind of list and edit the conditions but again problem rises as in every type of contact need a some mandatory fields to achieve a quality of data but in present system it lacks because all field is attached to a single node type and we are just hiding other field for showing up and if we make some field mandatory than it will cause a problem in saving node.
Proposed Solution (not clear):- though i am not a developer but we could find some kind of solution for this to make better ditro like commerce kickstart
1. we are using profile2 module so we could use its profile type entity and use as a contact but problem again rises with this solution is that profile2 is right till the extend of person but how we will save data of organization is not clear with it. (we could build a pseudo profile for this kind of need but this will again look ugly)
2. we could use other crm module to full-fill this issue like redhen, civi after all we are in drupal ecosystem this will benefits both the projects( i used redhen module and its pretty clear what is contact type its just a suggestion)
3. we could build with eck module.
4. custom build which again re-inventing the wheel and extra cods to maintain

------And for the work flow managment of the project we could use module like maestro or worlflow or Rules. with this wo could build this project more flexible so it can support any kind of projects for any kind of business.

thank you

Comments

manuelBS’s picture

Thanks for these good ideas! I fully agree that separating the content types into entities would be great benefit for ERPAL. Also reusing some existing modules like redhen or CRM Core could be a benefit. But as this would be much work to migrate I think we should keep this for the next version in drupal 8. We are currently planing how the structure can be build more flexible with rules and custom entities. So if you have other ideas and figured out some other problems, just get in contact again to discuss.

manuelBS’s picture

Status: Active » Needs work

Set this to needs work, we will do this in the next version.

manuelBS’s picture

Status: Needs work » Closed (won't fix)

We will do this on the next version that we will introduce in a view weeks in detail called ERPAL platform. For this version its to much work to migrate and it works well as it is.