Read Only Option - Instance Configured: Where is this set up?

[tahnalos]

For the rich_description field on sn_hr_core_case form, I noticed this option:

I am already aware of the system property glide.read_only.legacy_read_only_behavior which is set to client_script_modifiable.  But how was this Read Only Option set in the first place to Instance Configured in the first place?  If I choose a different option, then Instance Configured disappears and I can no longer select it.  On a PDI, the Instance Configured option is not selectable.  I'm assuming that a second property is involved but I am unsure as to what that property is.

[Tanushree Maiti]

Hi @tahnalos 

Check 

Configuring read-only security options 

The Instance Configured read-only option maintains backwards compatibility for read-only fields created prior to the Australia release, and also enables you to test other read-only options on a non-production instance before implementing them on your production instance.

When the Read only option is set to Instance Configured, read-only behavior is determined by the glide.read_only.legacy_read_only_behavior system property. The default value for the glide.read_only.legacy_read_only_behavior system property is client_script_modifiable, which means the field appears as read-only in the UI, but can still be changed by a client script.

You can test read-only behavior on a non-production instance by updating the system property with the following values and then validating that your fields and client scripts work as expected.

• display_read_only
• client_script_modifiable
• strict_read_only