How do I configure the layout of a catalog task form so both request and requested item display?

sbh
Tera Guru

So far, we've only been attaching catalog tasks to requested items. We're going to start using an order guide soon and that will involve attaching catalog tasks to requests and not to requested items generated by the order guide. But when I try to add the request field to the catalog task form layout, requested item disappears, and vice versa. I need to show both fields on the form.

 

Thanks in advance for your help!

1 ACCEPTED SOLUTION

Community Alums
Not applicable

That is from a very useful browser extension called SNUtils.  I highly recommend it. 

Have you also checked client scripts? 

You could also try using the field watcher to see what is hiding it.  Instructions for watching hidden fields are about halfway down this page:

https://docs.servicenow.com/bundle/tokyo-api-reference/page/script/debugging/concept/c_FieldWatcher....

View solution in original post

6 REPLIES 6

Community Alums
Not applicable

This should be straightforward and easy to do. 

Open the sc_task.form and coose Configure > Form Layout

Ensure that both Request and Request Item are selected.

Save the form layout.

 

DustinWatkins_0-1686260156434.png

 

 If you have them both selected, and you still do not see them both, check your UI policies to see if something is hiding them.

Thank you for your speedy response! 

 

Both are selected and there are no UI policies affecting either field, but your screenshot looks a little different from mine. Your slushbucket lists both label and field name, and mine only lists the label. Does that mean anything? 

 

sbh_0-1686260772712.png

 

Community Alums
Not applicable

That is from a very useful browser extension called SNUtils.  I highly recommend it. 

Have you also checked client scripts? 

You could also try using the field watcher to see what is hiding it.  Instructions for watching hidden fields are about halfway down this page:

https://docs.servicenow.com/bundle/tokyo-api-reference/page/script/debugging/concept/c_FieldWatcher....

Thank you, @Community Alums !

 

I don't have the option to use the field watcher. (I see it's not supported for Next Experience in Tokyo, though I don't use Next Experience in dev.) But a client script turned out to be the culprit. I think I'm going to deactivate it - do you think that would cause any problems? Sorry for the tiny screenshot

 

sbh_0-1686319407984.png