Because processors are deprecated in Paris, I was curious if there is a way to accomplish this using the supported feature of Scripted REST APIs. We have yet to deploy to production, and we don't want to start down a path using a deprecated feature (processors), if possible.

Our use case is that we have published and marketed many short URLs in our current environment, pre-ServiceNow (e.g. https://askit.ttu.edu/phishingexamples). They are much simpler for customers to type, agents can remember them easily, and they are guessable. Most of them link to common KB solutions, while a few redirect to a website of our choice. We need all of these existing URLs to continue working when we move to ServiceNow. This askit.ttu.edu hostname will be our service portal address in ServiceNow.

Our current environment accomplishes this using Tomcat URL rewrite rules.

We plan to use the custom URL feature for our ServiceNow instance so that we keep the host name the same, and for the exact paths the solution at https://community.servicenow.com/community?id=community_question&sys_id=01e3cfa5dbd8dbc01dcaf3231f96... was tested by us and works great.

From reviewing the documentation about Scripted REST APIs, it seems like we don't have full control over the exact URL.

Can anyone help with this?