On Jul 25, 2008, at 4:18 PM, Adrian Crum wrote:

David E Jones wrote:
Some options might be:
1. use the FixedAsset owner (and similar concepts) to identify who to send it to, either directly or through a PartyRelationship to someone in the organization in charge of managing fixed asset maintenance (and similar concepts in other areas); the idea would be to use the natural organization and relationships that companies would want to setup anyway, and use that for as much as possible, including these notifications; this reduces setup and maintenance complexity and makes the system in general easier to use and understand, and if flexibility points are needed for funny situations in the future we can look at that then

So, go from fixed asset to the related party in the role of owner, then look for a party related to the owner in the role of Maintenance Manager? When that party is located, which email address is used? Or do we assume they have only one?

Probably just the primary email address. I don't know if it's worth having a special purpose for this... is it common in your situation to need a separate email for this sort of thing?

One thing to consider is that the related party (Maintenance Manager) could be a PartyGroup, with a special email address used just for this purpose, but that would be chosen by the user depending how they want to setup that relationship.

2. create a central set of Party or just ContactMech/email records with different purposes, and look up the one to use for the relevant area; this could be tied to the set of notifications available when those are configured so simplify and centralize administration

Do you mean set up a contact mech type specific to each notification process, then list all contact mechs matching that type for the user to choose from? In that case, I'll need an entity to make the connection from FixedAsset to ContectMech.

No, this would be more like what Jacopo suggested with the communication configuration per company. Along with configuring outgoing emails we would configure the fromPartyId or a fromContactMechId.

-David


Reply via email to