Can we set the on-hold reason is mandatory even though value in On hold reason

[Srinivasu2]

Hi Community,

Requirement :

Whenever user select state as on hold and on hold reason is mandatory without 'None" value

I need to disable the "None value" but on hold reason should be mandatory with value 'Awaiting caller' or 'Awaiting vender' or 'Awaiting Problem' or Awaiting change

Is it possible to set On hold reason mandatory with value other than 'None' ?

Thanks & Regards,

Srinivasu Sagiraju

[Robbie]

Hi @Srinivasu2,

This is absolutely possible. A point to note... the reason why the 'None' value exists is to prompt the user into selecting a value. The record can never be saved with 'None' (Assuming it's been configured correctly).

If you want to remove the 'None' value, you will need to set a Default value.

This is easily achieved by simply:

- Right click against the 'On hold reason' field' and select the 'Configure Dictionary' option.

- From here, you can select what you would like to display against the 'Choice' field under the 'Choice List Specification' tab as shown below.

- Simply select 'Dropdown without --None--

- Now click on the 'Default' tab and enter the value of the default value - Tip. Look at the 'Choices' Tab and Related list at the bottom of the form for the values. If you want 'Awaiting Caller' as the default display, you need to enter 1 as the Default value.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

[Runjay Patel]

Hi @Srinivasu2 ,

Its simple rule, if you making filed mandatory and you filled with value then system it will not ask again to fill the value as it is already filled.

'Awaiting caller' or 'Awaiting vender' or 'Awaiting Problem' or Awaiting change these all are value for reason filed. What is your use case? why you wanna do it? if you can help me with detailed explanation i can help you with alternative solution.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Mark Manders]

What is your business case? What is the reason 'none' needs to be removed? It's very simple: only 'none' is seen as empty. If you remove it, the field will always have a value, so it is always filled and no 'mandatory' setting will apply (because mandatory means that you can only save the record with a value).

Your requirement is contradicting. Either you need it mandatory, which needs the 'none' or you proceed without 'none' and always have a value.