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.

[chrisshellhamme]

@Ankur Bawiskar Thanks for the response.  I went through all of the UI/Data Policy actions for the cmdb_ci field and none met the criteria for setting the field read-only based on the conditions.

I also checked UI Scripts and Client Scripts for any where the script contains setReadOnly('cmdb OR setReadOnly("cmdb and no results were returned.

Did I miss anything else to check?

[Ankur Bawiskar · Accepted solution]

@chrisshellhamme 

Did you try to use field watcher and see?

[chrisshellhamme]

@Ankur Bawiskar 

Thanks for this!  Field Watcher helped to identify the Client Script that was locking it.  I forgot about using it!

Thanks,

Chris