UI policy error Unable to set security read-only field's mandatory state to true

[Sheryl Lyke2]

I'm experiencing some strange UI policy behavior on change request. As an admin user, I'm not having the issue but an itil user is. 

Process: create a new change request and use UI actions to update the state of the change.

The field I'm looking at is close_notes. The user has access to it while the change is New, Scheduled, Planning, In Progress. But when the UI action "Change Complete" is pushed to update the state to change complete, the close_notes field is read only. The debugger just shows "Unable to set security read-only field's mandatory state to true". But the UI policy should be making the field mandatory at this point not read only. I know it's not an ACL issue because they have access to the field until the state changes to change complete. There aren't any other UI policies on the field that would be colliding with it. 

State = planning, field is editable. Same for In Progress and New

State is in progress - error in debugger

Here's the UI action that sets the state to change complete

And here's the UI policy that sets the field to mandatory

Does anyone know what would be causing this?

[Sheryl Lyke2 · Accepted solution]

It was the business rule "mark task closed" that was causing the record to become inactive

[Sherman Ignacio]

Hi Sheryl,

I know this is from long time ago, but Iam experiencing the same issue in Change Form. Its the configuration item field for me this time and the error is "Unable to set security read-only field's read-only state to false". I tried to deactivate the UI Policy that prevent the user to change the CI value when state is not new but still the CI field is still on read only. How did you traced your issue ? i checked the logs from field watcher, and i cant find any issue that might causing the problem. Thanks!

[Sherman Ignacio]

Hi Sheryl,

Nevermind this. I already found what causing the issue Iam experiencing, as per checking the Dinctionary Entry of the field, the Read-Only checked box was active. So I created a Dictionary Override and override the read-only. Thanks! 🙂

[rajneeshbaranwa]

You should also check Client Script if changing states to closed complete makes this field 'Read Only'.

From the functionality point of view, I think the field should be read only on form load for closed Change Requests but seems like somehow field has been made readonly on change(Not onload) of state field to Closed Complete

[Sheryl Lyke2]

Thanks for the response, there aren't any client scripts running on this field.