[jira] Created: (OFBIZ-2536) make a relation between communicationEventType and contactMechType

[Nicolas Malin (Jira)]

make a relation between communicationEventType and contactMechType
------------------------------------------------------------------

                 Key: OFBIZ-2536
                 URL: https://issues.apache.org/jira/browse/OFBIZ-2536
             Project: OFBiz
          Issue Type: Improvement
          Components: party
    Affects Versions: SVN trunk
            Reporter: Hans Bakker
            Priority: Minor


I was planning to do this hardcoded but then realized it would be better to have this relation in the entities.

If i would know which contactMechTypes (email, telephone, postaladdress) where used with which communicationEventtypes (email, letter, telephone call) i would not have to have this hardcoded in the programs as it is now.

The proposal is to have a field added to the communicationEventType entity called contactMechTypeId to indicate that email addresses are used with emails and telephone numbers are used with telephone calls.

Any comments or objections?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker reassigned OFBIZ-2536:
----------------------------------

    Assignee: Hans Bakker

> make a relation between communicationEventType and contactMechType
> ------------------------------------------------------------------
>
>                 Key: OFBIZ-2536
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2536
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>            Assignee: Hans Bakker
>            Priority: Minor
>
> I was planning to do this hardcoded but then realized it would be better to have this relation in the entities.
> If i would know which contactMechTypes (email, telephone, postaladdress) where used with which communicationEventtypes (email, letter, telephone call) i would not have to have this hardcoded in the programs as it is now.
> The proposal is to have a field added to the communicationEventType entity called contactMechTypeId to indicate that email addresses are used with emails and telephone numbers are used with telephone calls.
> Any comments or objections?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker closed OFBIZ-2536.
------------------------------

       Resolution: Fixed
    Fix Version/s: Release Branch 9.04

Committed revision 780984

> make a relation between communicationEventType and contactMechType
> ------------------------------------------------------------------
>
>                 Key: OFBIZ-2536
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2536
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>            Assignee: Hans Bakker
>            Priority: Minor
>             Fix For: Release Branch 9.04
>
>
> I was planning to do this hardcoded but then realized it would be better to have this relation in the entities.
> If i would know which contactMechTypes (email, telephone, postaladdress) where used with which communicationEventtypes (email, letter, telephone call) i would not have to have this hardcoded in the programs as it is now.
> The proposal is to have a field added to the communicationEventType entity called contactMechTypeId to indicate that email addresses are used with emails and telephone numbers are used with telephone calls.
> Any comments or objections?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.