ACLs do not set readonly and disabled attributes on fields - Known Error

ACLs do not set readonly and disabled attributes on fields Description Under some circumstances, fields set to readonly do not set consistent attributes on form inputs. Steps to Reproduce

Create a new ACL with the following values:

Type : record Operation : write Admin overrides : false Advanced : true Name : incident.category Script : false;

Open an incident form.

The Category field will be readonly.

Write a client script to log g_form.isDisabled('category') or open the browser console and execute g_form.isDisabled('category'). (Ensure that gsft_main frame is selected.)

The g_form functions isReadOnly and isDisabled both return false, they should return true.

Execute g_form.getControl('category').

The DOM element does not have these attributes: class="disabled readonly" readonly="readonly" disabled=""

Execute g_form.setReadOnly('category', true)

isDisabled and isReadOnly functions will now return true

The element returned by g_form.getControl('category') will have these attributes: class="disabled readonly" readonly="readonly" disabled=""

Workaround Use a client script to manually set g_form.setReadOnly(field, true) so that the form API properly recognizes the field as readonly.