new entity: CommunicationEventSubscription

[hans_bakker]

I have a customer who would like to relate customer complaints against
subscriptions.   Currently it is possble to have a 1 to 1 relationship
between  a subscription and a communicationEvent, but not a 1 to n
relationship.

Anybody any objections to add the CommunicationEventSubscription entity
similar to the CommunicationEventProduct  entity?

if this is ok, shouldn't we remove the communicationEventid field from the
subscription entity?

please let me know your opinions.

--
Regards,
Hans Bakker
ANT Websystems Co.,Ltd (http://www.antwebsystems.com)

If you want to verify that this message really originates from
from the above person, download the public key from:
http://www.antwebsystems.com/hbakkerAntwebsystems.asc

[Yannick Thebault]

I think a relationship between contactList and subscription will be better.

Yannick

Le Mardi 31 Octobre 2006 06:45, Mailinglist a écrit :

> I have a customer who would like to relate customer complaints against
> subscriptions.   Currently it is possble to have a 1 to 1 relationship
> between  a subscription and a communicationEvent, but not a 1 to n
> relationship.
>
> Anybody any objections to add the CommunicationEventSubscription entity
> similar to the CommunicationEventProduct  entity?
>
> if this is ok, shouldn't we remove the communicationEventid field from the
> subscription entity?
>
> please let me know your opinions.

--
Yannick Thebault
Consultant
Tél : [phone]
Site projet : http://www.neogia.org/

Société Néréide
Tél : [phone]
Site : http://www.nereide.biz/

[David E Jones-2]

On Oct 31, 2006, at 3:56 AM, Yannick Thebault wrote:

> I think a relationship between contactList and subscription will be  
> better.

How would that address the requirement?

I think for this sort of need the original proposal sounds fine.  
Hans: just watch the length of the entity name.

-David

> Le Mardi 31 Octobre 2006 06:45, Mailinglist a écrit :
>> I have a customer who would like to relate customer complaints  
>> against
>> subscriptions.   Currently it is possble to have a 1 to 1  
>> relationship
>> between  a subscription and a communicationEvent, but not a 1 to n
>> relationship.
>>
>> Anybody any objections to add the CommunicationEventSubscription  
>> entity
>> similar to the CommunicationEventProduct  entity?
>>
>> if this is ok, shouldn't we remove the communicationEventid field  
>> from the
>> subscription entity?
>>
>> please let me know your opinions.
>
> --
> Yannick Thebault
> Consultant
> Tél : [phone]
> Site projet : http://www.neogia.org/
>
> Société Néréide
> Tél : [phone]
> Site : http://www.nereide.biz/