Skip to main content
J
jsummers1-Visitor
1-Visitor
January 14, 2014
Solved

Integrity help needed for emailadvance.js script to send link pointing to the originating server

  • January 14, 2014
  • 1 reply
  • 1847 views

Want to know if anyone knows how to have the link that emailadvance.js sends in the body of the email to point back to the actual URL: location that the email was sent from.

In other words if I have an email rule that sends an email to someone from the staging server, I want the link to point back to the staging server not the production. It appears this is a hard coded process from the parameters passed in to the script.

This causes issues when testing and the test causes the trigger to fire it sends and email pointing to production instead of test. I know it can be done some way because if I use a link from the Issue number, ie. User id, on the staging side it sends the link pointing to the staging server not production

Best answer by LLawton

Which version of Integrity are you using, or more specifically of that script?

The version of emailAdvanced that has been shipping for a while (I think since 2009, but definitely 10), takes care of the hostname automatically if you use variables such as "<%hosturl%>" in the body of the e-mail.

Look at the description of the "Message Body" parameter for more on that.

For example, my trigger includes an item link with this syntax:

HREF='http://<%hostname%>:7001/im/editissue?selection=<%ID%>'

1 reply

L
LLawton16-PearlAnswer
16-Pearl
January 14, 2014

Which version of Integrity are you using, or more specifically of that script?

The version of emailAdvanced that has been shipping for a while (I think since 2009, but definitely 10), takes care of the hostname automatically if you use variables such as "<%hosturl%>" in the body of the e-mail.

Look at the description of the "Message Body" parameter for more on that.

For example, my trigger includes an item link with this syntax:

HREF='http://<%hostname%>:7001/im/editissue?selection=<%ID%>'

    J
    jsummers1-VisitorAuthor
    1-Visitor
    January 15, 2014

    It turns out we have old and new emailadvance.js being used, Thank you for pointing out that there is a new one.

    Terms & ConditionsAccessibility statement