please review use cases and implementation proposal

[Hans Bakker <ma...@antwebsystems.com>]

Review requested for implementing the following use cases:

Specific use case: 
As an addressee of an incoming email I would like to indicate that a
specific email should be deleted and further incoming emails from the
same sender should be ignored by the system and therefore not be shown
to me anymore.

Generalized use case: 
As the addressee of incoming information (commevent, invoices, order
etc) by any means (webservices, smtp, etc) i should be be able to
indicate that the information is not wanted and optionally indicate that
future incoming information from the same sender is blocked. This should
also be valid for outgoing information. (request from receiver)

In order to facilitate this function, the proposal is to add the
following entity:

PartyBlockedContactMech

fields:

senderRecipientPartyId (_NA_ for any sender/recipient within the system)
incoming/outgoing I/O/A (A = all)
contactMechId
fromDate
thruDate

This could potentially replace the order black list.

Regards,
Hans

-- 
Ofbiz on twitter: http://twitter.com/apache_ofbiz
Myself on twitter: http://twitter.com/hansbak
Antwebsystems.com: Quality services for competitive rates.