question Re: Should variables carried over to the RITM be read only? in ServiceNow AI Platform forum

Should variables carried over to the RITM be read only?

paw2 — Thu, 28 Jul 2016 13:07:48 GMT

After submitting a request, the variables are carried over to the RITM record as editable. Do most companies leave as editable or make read only? What are the ramifications either way? If best practice is to make read only, what is the best way?

Re: Should variables carried over to the RITM be read only?

Chuck Tomasi — Thu, 28 Jul 2016 13:14:28 GMT

Hi Patricia,

Most make them read-only as they are part of the original request, may be used as FYI for approvals, etc. and should not be changed once the process has begun. There are exceptions to every rule, of course.

The best way to make the variables read-only is with a catalog UI policy. You can have it apply only to the request item (and not to the catalog item when the user is filling it out.)

Service Catalog UI Policy - ServiceNow Wiki

Re: Should variables carried over to the RITM be read only?

Uncle Rob — Thu, 28 Jul 2016 13:53:13 GMT

I take a far more liberal view of what variables are and should be used for.

I tend to make variables read only via UI Policy / Script when I specifically want them read only. Otherwise I leave them open or hidden.

On many an occasion I've used variables as a "just in time" data element.

Say we're on the 4rth step of an onboarding workflow. This task is for someone to see if the network jack needs patching. If yes, the workflow splits down a new path. If not, continue forward. What do you do in this case? Add a new field to your sc_task table? No. I use a variable that will appear only on that sc_task.

Re: Should variables carried over to the RITM be read only?

sundeep6 — Fri, 12 Aug 2016 23:20:07 GMT

If you don't want to individually set each catalog item to read-only by using Service Catalog UI Policy, and instead want all variables on a particular form (request item, SC task, etc) to be read-only for everybody after the request is submitted, the script shown at the bottom of this page works well (incl in Geneva): http://www.servicenowguru.com/scripting/business-rules-scripting/variables-form-readonly/

I've copied it below for ease of reference:

All Variables Readonly Client Script
Name: All Variables Readonly
Table: Incident, Change request, Request item, Catalog task, wherever!
Type: onLoad

Re: Should variables carried over to the RITM be read only?

jamesmcwhinney — Mon, 15 Aug 2016 14:55:14 GMT

I just tried this in Helsinki against requested items (sc_req_item) but it didn't work.

Also the article mentions this workaround shouldn't be used from Calgary onwards

Re: Should variables carried over to the RITM be read only?

lionelcomandini — Mon, 19 Sep 2016 14:09:11 GMT

Hi Patricia,

Yes I do agree, most of our clients have this requirement.

I would suggest to avoid any customization in order to stay aligned with the product (cost, maintenance, performance, upgrade...),

I recommend to use the SNC OOTB feature, managing access by role.

Open the variable form
Add "Write role" to the form/list
Add "admin" role to the variable

The variable won't be editable anymore after the submission by a non-admin user.

Tips and tricks : Set it up as default value.

Configuration :

Result :

Thanks,

Regards,

Lionel COMANDINI

ITEO

Skype : lionel.comandini.iteoconsulting

Email : lionel.comandini@iteoconsulting.com

Re: Should variables carried over to the RITM be read only?

JerryJ071847183 — Tue, 17 Dec 2019 06:18:27 GMT

I found the most appropriate solution for this , incase there are lot of catalog items and you want to implement on all the variables.

Then just create one UI policy on sc_req_item table

and in condition "select state is "one of" and "select all states" , so that it will always be true

keep onLoad checbox checked and then in script put this

ONce this is created , raise any catalog item and when you see RITM variables all of them will be readonly by default.

And no need to worry abt worknotes and additional comments as people can still log into that.

And most important you can test in different views as well like default and workspace it will be success.

Mark my ANSWER as CORRECT and HELPFUL if it works