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?
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.
Those are both good suggestions - thanks! I just want to make sure I'm
understanding you correctly before proceeding.
-Adrian
