I have been presented with an interesting problem in FIM. As it stands, I've rolled out a change in production that allows users with company email to search for and request to join manual distribution groups (open and owner-approved). This adds their user resource which sends to their primary SMTP by default, BrianFIM@contoso.com. They cannot see criteria-based or manager-based distros still. Open distros are completely open for both joining and leaving and owner-approved distros require an approval process. The change matched the original request and specs but they are now requesting to allow for pager contacts to be added. These contacts are specifically for pagers (hello 1980's) and can take the form of either an email address that goes to the pager such as pgBFIM@contoso.com or a phone SMS contact 555555555@vtext.com. What is the best way to tackle this problem? Adding the contact as a proxy address or a pager string and modifying the search in "Members to Add" to include those fields would ultimately result in the user resource and primary SMTP being added only. Should I add a drop down menu for a set "All email users with pagers" to select email, pager, or both? My original thought is to create a separate "Pager" resource and flow the contents of that OU back into FIM. Should that be tied to the FIM person or separate? By creating a separate resource I wouldn't need to build a drop down menu like the above scenario. Any suggestions? Has anyone worked through a similar issue?

It is often better in the long run the create the seperate object type, even though it's more work up front. The user can then presumably choose to add both themselves and their pager, or just themselves, or just the pager. You can have a reference attribute that links the pager to it's owner, which would allow you to develop a custom workflow which clears out the pager as part of deprovisioning the person's user account. http://www.wapshere.com/missmiis