Use custom field/variable for the To: email address in an Ad Hoc notification

Hi there....instead of using the email address variable for the requester, you can use the built in Requester variable to send ad hoc emails.

Thanks Michael,

Unfortunately, if I set the "To" value to "Incident Requester" and that Requestor email address is outside of my org's domain/directory, the Ad Hoc Email is never received at that address. 

This seems to only affect Service Catalog items. I can create normal tickets with an outside user's domain as the request and there is no issue. 

That may be a limitation of the Service Catalog ad hoc emails not allowing outside emails.  Service Catalogs are accessed via the portal so it makes some sense that outside emails would not be allowed.  You could try an automation rule to perform the same thing.  Or create a Group for 3rd Party Vendor and add members that are set to Service Task Users.  They would be able to receive the information from the ad hoc email in the catalog workflow.

That may be a limitation of the Service Catalog ad hoc emails not allowing outside emails.  Service Catalogs are accessed via the portal so it makes some sense that outside emails would not be allowed.  You could try an automation rule to perform the same thing.  Or create a Group for 3rd Party Vendor and add members that are set to Service Task Users.  They would be able to receive the information from the ad hoc email in the catalog workflow.