Need to modify Survey URL

[Billy Strohm]

We have a self-hosted instance that has our own URL https://servicenow.company.com vs the normal https://company.service-now.com.   When viewing the Survey URL inside the survey definition we see https://company.service-now.com/xxx.   This is also true for the link in emails when we assign a survey to someone.   We have already changed the glide.email.override.url property and that fixed the link to incidents but did not change the survey feature.   Thanks in advance for any assistance.

[chennessy]

As far as I can tell, this question is still not answered correctly.   I have gone through every suggestion (I have the same issue) and I am not seeing any place where I can actually type in the correct URL.     The View Survey URL does not allow you to edit it.   I've checked the email notification, and the script includes, etc.   and I see no place to make that correction.     I've searched values in the sys_properties.list, etc.     Any other ideas, Community?

[chennessy]

As far as I can tell, this question is still not answered correctly.   I have gone through every suggestion (I have the same issue) and I am not seeing any place where I can actually type in the correct URL.     The View Survey URL does not allow you to edit it.   I've checked the email notification, and the script includes, etc.   and I see no place to make that correction.     I've searched values in the sys_properties.list, etc.     Any other ideas, Community?       Billy Strohm, have you found a solution?       Thanks!

[Billy Strohm]

Cheryl,

The problem has been solved in our instance.   Unfortunately we aren't able to pinpoint exactly what setting did the trick.   We believe the value is being cached somewhere and the change doesn't show up right away.   We have a suspicion that the glide.properties file located in /glide/nodes/{instance}/conf directory on the server is the culprit but have been unable to prove it.

[chennessy]

Thanks for the response, Billy.       The sys admin for our system sent me a note to say that there is a script in the background that needs to get run; he did it for dev and voila, the URL is correct.     Not sure what script that is, but apparently you are correct in that cached values need to be updated; it's out of 'our' (developers) control.       Thanks again!