I did and it worked as you explained. The Email Engine has the ability to receive a username in the AR System Email Messages form and find the email address at run time. If an email address isn't found then it will try the username as is and well in your case that is a valid email address so an email is sent.
I think there might be a little confusion around the dependencies though. The Email Engine doesn't care about CTM:People or the Notification Engine ( NTE) for that matter. People and NTE are apps built on ARS . The Email Engine is core AR functionality (more or less). The Email Engine works with or without People and/or NTE. These two forms/apps need the Email Engine but the Email Engine doesn't need them. The apps are designed to utilize the a core feature of AR, the Email Engine. People and NTE give the Email Engine the data it needed to email somebody. Over simplifying... the Email Engine could be thought of as a subroutine. I think in your second paragraph you explained how the Email Engine is designed to work. If a filter's mechanism is User Profile Default, AR System looks to the User form to see what the mechanism should be. This is before the Email Engine is even involved. If the filter is set to Email it does not look to find the mechanism in the User record and sends the notification to the Email Engine no matter what. I suspect this is what is happening in NTE. There are filters that are hard coded to send an email, alert and even page if I remember correctly. The Run If is based on ITSMapplication defaults or a more granularly specified CTM:People preference. Since the ITSM app default is email or the People records is configured to use email I believe the NTEEmail filter Run If is true based on ITSM data and therefore being sent to the Email Engine. The issue isn't necessarily and issue with the Email Engine, it is just being fed data. If there is a defect it is in the ITSM side of things where ITSM shouldn't be sending notification data to the Email Engine. That doesn't mean you don't still have an issue in your environment but I hope it clarifies where I believe the problem lies. Jason On Fri, Sep 27, 2013 at 1:40 AM, Ray Gellenbeck <[email protected]>wrote: > It is really using the user name. Try it. Create a User record with no > email address value but a valid-formatted email address for the Login ID > field. > > The notify action is not paying attention to which mechanism is selected, > I selected "email" in the construction of the notify action in the filter. > It will only check notification preference if I leave it set to "default" > when I make the notify action. That is also something to bear in mind when > testing and you have VIP's that don't want to be bothered. > > The short answer is: Email engine uses the User form and ignores > CTM:People. Worse, email engine's methodology leads to unexpected action > in this unique case. In ANY case, it will ignore the notification > preference in CTM:People if your filter is set to EMAIL and it WILL send > messages to people who are not Disabled in the User form. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
