Number Maintenance - incident number in the sequence, causing gaps

[MominA]

In ServiceNow, when you create a new incident, the system generates an incident number based on the configured number maintenance settings. However, when you create a new incident and then cancel it without saving it, the system can still "consume" the incident number in the sequence, causing gaps like

INC000001, INC000002, INC000003 ---> These all incidents cancelled without saving it.

If i click on New button then i want the number as "INC000001" not "INC000004".

I wanted to avoid this and it should not consume the unsaved incidents number. How can i achieve it?

[Dr Atul G- LNG]

Hi @MominA 

It is not feasible to achieve this, and I strongly recommend against attempting it. The number generation process relies on internal code and is reset if the record is not saved. Implementing your requirement would increase technical debt. The best approach is to adhere to the Out-of-the-Box (OOTB) functionality.

[HasanM]

Hi @MominA 

There is a system property named "glide.itil.assign.number.on.insert" which will assign number after insertion of record . Initially its value is false make its value to true to get the functionality.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards
@HasanM