- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 01:03 PM
Hi Experts,
When I submit a catalog item in the Service Portal, it redirects to the default landing page with the generated REQ number. I would like to redirect to the RITM number instead. How can I achieve this?
Can anyone share the code for this? Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 11:28 PM
Hello @rajibosss11 !
A streamlined approach to redirecting users to RITMs without introducing complex customizations that could negatively affect the Portal (especially after future upgrades) is to leverage Page Route Maps.
Fortunately, a few years ago, @Kieran Anson published an update set (and a community post) that simplifies this process. It allows redirection to RITMs instead of the request record, all without the need to clone widgets, write additional client scripts or implement other custom logic. You can find the update set here: https://developer.servicenow.com/connect.do#!/share/contents/6143266_redirect_to_ritm?t=PRODUCT_DETA...
By committing this update set, you will be able to configure each catalog item individually to redirect to the request item record rather than the order status/request page just by toggling the 'Redirect to RITM' field on the RITM form.
Additionally, a global system property (x_295070_req2ritm.redirect_override) allows you to enforce redirection to RITMs regardless of item-level settings.
Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 11:58 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 07:03 PM
Hi @rajibosss11, you can try with a msg after your submit you form
add a business rule, after with the condition your item
and the script you insert gs.addInfoMessag()
something like that:
“var str ='<a href="https://www.google.com" target="_blank" >Google </a>';
gs.addInfoMessage(str );”
Open the url page of your RITM and get the URL, probably will contains the RITM id there
you change to “var ritmSysId = current.sys_id”
as i know is not possible to change of REQ to RITM, but with it every time that you create a gs info message will be disparates with a link to direct in the RITM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 11:28 PM
Hello @rajibosss11 !
A streamlined approach to redirecting users to RITMs without introducing complex customizations that could negatively affect the Portal (especially after future upgrades) is to leverage Page Route Maps.
Fortunately, a few years ago, @Kieran Anson published an update set (and a community post) that simplifies this process. It allows redirection to RITMs instead of the request record, all without the need to clone widgets, write additional client scripts or implement other custom logic. You can find the update set here: https://developer.servicenow.com/connect.do#!/share/contents/6143266_redirect_to_ritm?t=PRODUCT_DETA...
By committing this update set, you will be able to configure each catalog item individually to redirect to the request item record rather than the order status/request page just by toggling the 'Redirect to RITM' field on the RITM form.
Additionally, a global system property (x_295070_req2ritm.redirect_override) allows you to enforce redirection to RITMs regardless of item-level settings.
Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 11:58 PM
Works like a charm!