+1 for party
not sure framework needs the contactlist to operate but considering the
pattern of putting things in common that is a possibility.
if put in framework a text readme should include where it was put for
those that may look for it in party.
=========================
BJ Freeman
Strategic Power Office with Supplier Automation
<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Bruno Busco sent the following on 12/18/2010 1:31 AM:
IMO the complete contactlist package should be moved away from the marketing
component and put in party.
The reason of this is that a contactlist could be used to notify a group of
users of something appening in ANY application.
This could be also considered for the framework-only installation.
What do you think about?
Regards,
Bruno
2010/12/14 BJ Freeman<bjf...@free-man.net>
Contact list can be used for many operations.
with a many to many relationship then it is achieved with out extra
entities.
Unless you are adding other fields then there maybe a reason.
the model from the data model book is to use enumeration and types to
define extra info.
just sharing, not against you doing it that way.
=========================
BJ Freeman
Strategic Power Office with Supplier Automation<
http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com<http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Ean Schuessler sent the following on 12/13/2010 4:10 PM:
MarketingCampaignContactList makes more sense to me.
It seems in line with tables such as PartyContactMech or
ProductStoreCatalog.
On 12/13/10 10:33, BJ Freeman wrote:
the appl as I understand it is a many to many interface.
to my knowledge no one has discussed migration, in detail, as an
(semi)automated process but I think it would be a good thread.
