- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 02:44 AM
In the SOW when viewing an incident there is the resolve button which when clicked brings up the modal for resolution. How do I go about setting this same thing up but for sc_request?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 03:07 AM
I don't think you should alter the OOTB process.
I suggest to stick to OOTB process.
If you still require then check the OOTB code for Resolve button and implement something similar for sc_request table
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 02:49 AM
Hi @joshmorris
There is no "Resolve" button on the SC_Request. You need to check the OOTB configuration for the "Resolve" button on incidents and then make the necessary changes.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 02:50 AM
but why?
Requests are not incidents which are created for something is not working or something is broken, so they are not meant to be resolved.
They are meant for closure only.
what's your business requirement?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 03:00 AM
We have a custom case where we use requests with resolved states rather than closed complete so would be very useful for us to get the functionality for request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2025 03:03 AM
Hi @joshmorris
Technically, you're violating the process and its core concepts. A request is never "resolved"; it is always "fulfilled," whereas an incident is resolved, not fulfilled. By using the wrong process, you're making things more difficult. As you mentioned, it’s a custom solution, so you need to review how the "Resolve" button is built in OOTB and apply the same approach to requests. However, it’s better to stick with OOTB to avoid potential issues in the future, especially during upgrades
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************