[JIRA] Closed: (OFBIZ-665) Extend CommEvent Entities to handle complex (real world) emails

["Si Chen (JIRA)" <ji...@ofbiz.org>]

     [ http://jira.undersunconsulting.com/browse/OFBIZ-665?page=all ]
     
Si Chen closed OFBIZ-665:
-------------------------

    Resolution: Fixed

This has been done a while ago, so I'm closing it out.  

> Extend CommEvent Entities to handle complex (real world) emails
> ---------------------------------------------------------------
>
>          Key: OFBIZ-665
>          URL: http://jira.undersunconsulting.com/browse/OFBIZ-665
>      Project: [OFBiz] Open For Business
>         Type: Improvement
>   Components: content, party
>     Versions: SVN
>     Reporter: Si Chen
>     Assignee: Jira Administrator
>      Fix For: SVN

>
>
> CommunicationEvent right now can be used to record emails and even send emails from OFBIZ (OFBIZ-438), but it can only handle very simple emails.  In the real world, we send emails of different MIME types (text, HTML) with attachments to a list of parties and contacts mechs (using CC and bCC).  Furthermore, our emails may be associated with various things (Quotes, Orders, Sales Opportunities, etc. etc.)  We need entities which could handle all of the above.
> To support additional parties and contact mechs:
> o CommunicationEventRole can support more parties, but roleTypeId is not necessarily useful.  What we really need to know is the party's role in the CommunicationEvent (Primary, Secondary recipient, etc.), so we need to add another field for that.
> o A new CommunicationEventContactMech entity to store the email addresses (contactMechIds).  Right now only contactMechIdFrom and contactMechIdTo can be stored.
> To support more complex emails:
> A model similar to ProductContent: CommunicationEvent.content will serve as an override field.  New entities for CommEventContent and CommEventContentType are created.  A CommEvent could be associated with multiple Content entities, so one could be main body, several could be attachments.  The content would be created using the OFBIZ content manager.
> We'll still need a field on CommunicationEvent to denote whether the MIME type of CommunicationEvent.content, so a new field for CommunicationEvent.contentMimeTypeId should be added.
> To relate emails to various things in the system:
> Following the pattern of CustRequestCommEvent, new entities such as OrderCommEvent, InvoiceCommEvent, QuoteCommEvent, SalesOpportunityCommEvent, to be created as needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.undersunconsulting.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira