Add CommunicationEvent.fromString, toString, ccString, headerString
------------------------------------------------------------------- Key: OFBIZ-704 URL: https://issues.apache.org/jira/browse/OFBIZ-704 Project: OFBiz (The Open for Business Project) Issue Type: Improvement Components: content Reporter: Si Chen Priority: Trivial Add new string CommunicationEvent.fromString, toString, and ccString to store literal from/to/cc of emails, instead of putting them into Notes if they do not match an existing contact mech. Add new CommunicationEvent.headerString as a separate text field to store the actual header of emails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[ https://issues.apache.org/jira/browse/OFBIZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Si Chen reassigned OFBIZ-704: ----------------------------- Assignee: Si Chen > Add CommunicationEvent.fromString, toString, ccString, headerString > ------------------------------------------------------------------- > > Key: OFBIZ-704 > URL: https://issues.apache.org/jira/browse/OFBIZ-704 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: content > Reporter: Si Chen > Assigned To: Si Chen > Priority: Trivial > > Add new string CommunicationEvent.fromString, toString, and ccString to store literal from/to/cc of emails, instead of putting them into Notes if they do not match an existing contact mech. > Add new CommunicationEvent.headerString as a separate text field to store the actual header of emails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471423 ] Chris Howe commented on OFBIZ-704: ---------------------------------- Is this the best way to model it? fromString, toString and ccString seem to be for specific types of comunication events as opposed to a generic communication event. > Add CommunicationEvent.fromString, toString, ccString, headerString > ------------------------------------------------------------------- > > Key: OFBIZ-704 > URL: https://issues.apache.org/jira/browse/OFBIZ-704 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: content > Reporter: Si Chen > Assigned To: Si Chen > Priority: Trivial > > Add new string CommunicationEvent.fromString, toString, and ccString to store literal from/to/cc of emails, instead of putting them into Notes if they do not match an existing contact mech. > Add new CommunicationEvent.headerString as a separate text field to store the actual header of emails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Si Chen closed OFBIZ-704. ------------------------- Resolution: Fixed > Add CommunicationEvent.fromString, toString, ccString, headerString > ------------------------------------------------------------------- > > Key: OFBIZ-704 > URL: https://issues.apache.org/jira/browse/OFBIZ-704 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: content > Reporter: Si Chen > Assigned To: Si Chen > Priority: Trivial > > Add new string CommunicationEvent.fromString, toString, and ccString to store literal from/to/cc of emails, instead of putting them into Notes if they do not match an existing contact mech. > Add new CommunicationEvent.headerString as a separate text field to store the actual header of emails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
Free forum by Nabble | Edit this page |