Adding additional choices to Change Request Status field

michaelcory
Giga Expert

One of our IT groups is requesting the addition of 7 more custom  Status values on Change Request form.   The additional status values would be used in workflow for this group, but may not apply to other groups that use Change Request.   My thought has always been that we should adhere to  a more global standard for all IT groups requesting changes, which means that we limit the Status selections to mostly out-of-box with a couple of exceptions.   Creating additional status values for certain groups seems to creep away from  the global standard approach.   One option I can think of to meet this group's workflow needs is to create a custom Status field that would be used by their group to drive their workflow, but not sure if this is better or if adding the 7 new Status options to the  existing 'state' field on the Change form is a  better option.

Is it  good practice to create additional Status fields on Change Request for specific groups,  or is it something that is recoommended NOT be done?   I don't know if it's something common that  other organizations do routinely, or if it leads to more congestion or  unforseen impacts.   Any guidance would be appreciated.

Thanks,

1 ACCEPTED SOLUTION

Thank you Mike for the update. The right solution is to use client scripts. Please also make sure you have "list_edit" ACL to prevent users from updating the records from the list.



Reference:


Client Scripts - ServiceNow Wiki


http://wiki.servicenow.com/index.php?title=Using_Access_Control_Rules



View solution in original post

7 REPLIES 7

angeliccharm
Giga Expert

Hey Mike,



I was going to suggest the same thing as Pradeep has already. Nice!


Thank you Lisa!


Matt Hernandez
Tera Guru

Here is the link for docs, Jakarta version..since the wiki will soon be gone this month and this article will be out of date.


Configure state field choice values