Send Email Based off of A Catalogue Variable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2015 11:42 AM
I need to send an email notification - based on a name that is populated on a Task. The Task originated from the Service Catalogue.
My first idea was just to copy that variable into a field on a Task form and use that Field to trigger a notification. Not much luck there. I can't get the variable to copy from the Request to the Task.
Do I keep trying to copy that variable into a field on the Task form? If so how?
or
Can I use that variable as a send to via an email notification?
Any help is welcomed!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2015 01:32 PM
ok i am a little confused as to how you want to trigger the email..... is it by the workflow hitting a certain point or what??
generally for a catalog item email i want it to fire at a certain point in the email.. so i will put in an event trigger at that point in time.. in parm 1 pass in the catalog variable that has the recipient and write the notification based on the event.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2015 02:06 PM
Can you create an email notification that fires on insert against the Catalog Task table?
Use the advanced condition: current.variables.your_variable_name == 'whatever'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2015 02:10 PM
catalog variables aren't on the catalog task table so no you can't
catalog variables are stored on the mtom table... what are we trying to accomplish again?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2015 02:13 PM
I think what Benn meant was, the trigger point that you were talking about is the insert of the catalog task..
I think he meant current.request_item.variables.your_variable_name == 'whatever'.
I think writing a business rule on mtom table is counter intuitive as the business rules condition will be evaluated to a *lot* of inserts/updates..