Incident Management
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
9 hours ago
I have a question regarding the Service Catalog and Incident Management configuration.
Currently, we manage our services in the ServiceNow Service Catalog. I need to create a new service that will initially be used only by Infrastructure and Application teams to raise and manage Changes related to the installation and setup of new machines and applications, ensuring full traceability.
However, during this initial phase, I do NOT want this new service to be available for end users or support teams in the Incident reporting module.
The idea is that the service should become available for Incident logging only after:
Only at that point should the service be activated and visible for Incident creation.
What is the best practice in ServiceNow to control the visibility or availability of a service for Incident reporting while still allowing it to be used for Change Management?
Should this be handled through service status, service offering configuration, user criteria, or another recommended approach?
Thank you very much for your guidance.
Currently, we manage our services in the ServiceNow Service Catalog. I need to create a new service that will initially be used only by Infrastructure and Application teams to raise and manage Changes related to the installation and setup of new machines and applications, ensuring full traceability.
However, during this initial phase, I do NOT want this new service to be available for end users or support teams in the Incident reporting module.
The idea is that the service should become available for Incident logging only after:
- The infrastructure has been fully deployed
- The application has been implemented
- The service documentation and architecture diagram are completed
- The SLA management team has received proper training and validated the service readiness
Only at that point should the service be activated and visible for Incident creation.
What is the best practice in ServiceNow to control the visibility or availability of a service for Incident reporting while still allowing it to be used for Change Management?
Should this be handled through service status, service offering configuration, user criteria, or another recommended approach?
Thank you very much for your guidance.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
35m ago
As per my understanding, once it is created, it will be visible in all modules. To control this behavior, you can add a UI Policy—for example, if CI = Name XXX, then show an error message. That would be the best way to handle it.
*************************************************************************************************************
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
