cmdb_ci field read only on Change Requests after upgrading to Xanadu Patch 4

[chrisshellhamme]

We upgraded our non-production instances to Xanadu Patch 4 last month and our Change Request forms now have the cmdb_ci field read-only for Draft Change Requests.  When the form loads, at first the cmdb_ci field appears as editable but it gets locked before one would be able to write to the record, which leads me to believe that this is happening client side.  This occurs both when creating a new Change Request or opening an existing one.  Note that when you request approval, the field opens up and becomes mandatory, though I believe that is custom configuration for our instances.  I believe that this is related to Xanadu, as we just cloned towards the end of last month and upgraded our non-prod instances immediately after, and this behavior is not exhibited in our Production instance.  I could not find a UI or data Policy or Client Script that would cause this behavior.

[Dr Atul G- LNG]

Hi @chrisshellhamme 

Could you please try to repair the change management plugin once again. 

[chrisshellhamme]

@Dr Atul G- LNG 

I tried repairing the Change Request plugin (com.snc.change_request) but the issue remains.

[Dr Atul G- LNG]

Hi @chrisshellhamme 

It could be related to a BR or script issue. It's best to log a support case with Now Learning, as you are on the latest Xanadu patch. This may be a product-related issue.

[Ankur Bawiskar]

@chrisshellhamme 

when form loads it shows editable and then it gets locked -> it means some client script or UI policy is doing this

Did you debug the client side code?

The code could also be in some UI script and the function of UI script might be invoked from client script or ui policy

If my response helped please mark it correct and close the thread so that it benefits future readers.