hat will result in emails going out in this case even though the
>> email address field is $NULL$
>> b. The email engine totally ignores CTM:People settings of Status as
>> well as User settings of Disabled/Enabled and Default Notification in this
>> case.
>>
>>
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
e
gt;
> Ray
>
> ----------
> *From:* Vyom Labs Support
> *To:* arslist@ARSLIST.ORG
> *Sent:* Friday, September 27, 2013 6:32 AM
> *Subject:* Re: Notifications firing unexpectedly - Odd case
>
> Hi,
>
> We can overcome this by enabling the option
n in this case.
Ray
From: Vyom Labs Support
To: arslist@ARSLIST.ORG
Sent: Friday, September 27, 2013 6:32 AM
Subject: Re: Notifications firing unexpectedly - Odd case
Hi,
We can overcome this by enabling the option "None" for the field "Default
Notify Mechanism
Sorry, but that has zero effect on this case. Already tested and proven.
From: Vyom Labs Support
To: arslist@ARSLIST.ORG
Sent: Friday, September 27, 2013 6:32 AM
Subject: Re: Notifications firing unexpectedly - Odd case
Hi,
We can overcome this by
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 fi
That is an interesting issue. It does make sense to me though. I am a fan
of the email address = username when you have people that are not from your
company.
What I think is happening is the people record is set to use email as the
preference by default. The notification engine is going to ref
I have ITSM installed but have customer workflow installed. At one point, all
members of a given group are sent a email notification via filter.
An unexpected behavior happens.
Details (this is tricky, so read carefully)
7.6.04 server (Remedy OnDemand system, not that it matters except to descr
8 matches
Mail list logo
