Standard Change Propose/Modify - ALL Change Request Values are read-only

[stevejarman]

Standard change proposal, modification should be available to users with itil or admin role.

I'm experiencing an issue where as someone with admin role, everything is working fine when Proposing or Modifying Standard Changes, but as a user with only itil role (not admin), ALL of the "Change Request Values" object becomes read-only.

I can't find where this is coming from or locate anything that's causing it.

Anyone have any thoughts?

[Community Alums]

HI @stevejarman ,

That's a Expected Behavior , nothing wrong in it !!

The fields are set read-only from the client script - Mark standard change fields read only

Since Standard Changes are pre-approved, low risk, they are normally read only. However, I know that sometimes the std change contains some generic info and needs updating before implementing.

Here are the steps I took to accomplish this allowing certain std changes to be editable before implementing. Maybe these steps will helps you :

Added new checkbox field to Change Request- STDCHG hold.
Clone client script - Mark standard change fields readonly - and added && g_form.getValue('u_stdchg_hold') == false) - which will prevent the fields from being read-only on submit IF STDCHG is true.
Clone UI action - Schedule - and added - g_form.setValue('u_stdchg_hold',false); - which will set the new field to false once the change is Scheduled thus making the fields read-only.
Created new UI Policy to hide new field since it has to be on form for Client Script to work.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[stevejarman]

Hi Sandeep - that applies to fields on Changes spawned from the template. Not to the template itself - i.e. that's on change_request table.

I'm talking here about the Proposal and Modification Catalog Item/Template.

(see screenshot in original post)

[stevejarman]

I'm now wondering if it's related to this -

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0636146

Though I'd hate to think that "bug" has been around since the Jakarta days and hasn't been fixed...?

(I'm asking the customer to add security_admin role to me so I can test the proposed workaround in DEV and see if it solves the issue).

[Community Alums]

It's not related to https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0636146  and it's not a bug , you can use the solution i proposed.

Glad to see @stevejarman  my answer helped You. 
Kindly mark the applicable answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep