The CreatorCon Call for Content is officially open! Get started here.

Link to alternate table in a Notification

Vlad_Rozic
Kilo Contributor

Hey all

I have setup assessments within Service Now and have setup a small mail notification to alert several users when a survey has been completed.

Currently it simply offer these users:

*So and So* has completed a survey based on the original ticket: *Original Ticket that the survey is triggered from is shown* (Use {Trigger_ID})

Now, what I'd like to do is make the ticket number clickable so that the user can click it and view the original ticket right from the email, but using the standard {URI_REF} won't work since the notification itself is triggering off of the assessment table.

If I use {trigger_ID} it links that ticket number fine. Is there any script available that can be entered to make the output of "trigger_id" link to the original ticket?

Thanks for any suggestions!

1 ACCEPTED SOLUTION

Vlad, I think your best course of action from here is to submit an incident in HI.   It seems like you have everything setup and should be able to use ${trigger_id.URI_REF} and ${trigger_id.URI}.   The support team should be able to help you further by taking a closer look at your instance and it's logs.



If you do submit an incident please be sure to post back here and let us know!



Thanks


Brian


View solution in original post

10 REPLIES 10

Is your notification setup to send when a record is inserted or updated on the "Assessment Instance" table, or is it setup to be sent out based on an event?



In my test system, I have it configured to send out when a record is inserted or updated on the "Assessment Instance" table.


Hey Brian,



Yes I had a look and its set to "when a record is inserted or updated"



Really weird why it isn't working for me


Vlad, What patch/hotfix of Eureka are you on?   And can you post a screen shot of the top part of of the Notification?   It should look something like this:


SurveyNotification.PNG


Hey Brian,



Here is a SS as requested.   As for version, we are eureka - patch5


Survey.jpg


Vlad, I think your best course of action from here is to submit an incident in HI.   It seems like you have everything setup and should be able to use ${trigger_id.URI_REF} and ${trigger_id.URI}.   The support team should be able to help you further by taking a closer look at your instance and it's logs.



If you do submit an incident please be sure to post back here and let us know!



Thanks


Brian