Best Practice & General Consensus for Ad-hoc Requests

Kieran Marsh
Tera Contributor

We are new to SN and we seem to be getting mixed advice on the where to, and how to record ad-hoc requests in SN.

The 2 options we have at the minute are;

-Create a custom table for ad-hoc requests

-Record in incident table and set categories as request.

                  The incident table OOB has prefix of INC which doesn't fit with a request and I am concerned this will have a negative impact on reporting. (We currently have this issue with existing                     product)

Version: Helsinki - latest patch

2 REPLIES 2

williamsun
Mega Guru

I have created a separate table, expanding the base [task] table, with the prefix of RFS (Request for Service) and manage a separate workflow that needs to go to a review team before being assigned.   This will depend on your process entirely, but my suggestion is that it is separate.


We also have a catalog item that is called "internal staff request" which is for simple tasks that are not in the catalog and are not a formal request, like for example making a report, updating a file, preparing a presentation for a client, etc.   This one is only available to the analysts and its usage is meant to be very light so that people can always have an option in order to register "all their work" on ServiceNow, especially if you are using Time Cards and want to tie most of it to task work.


Mike Malcangio
ServiceNow Employee
ServiceNow Employee

Many customers end up using, or building something like, the Service Desk Call functionality:


Service Desk Call



The intent was to able to field "a call" and then pick the appropriate process to follow -- whether that was incident or a Service Catalog request.