I recently applied some field security on two UD boolean fields. The fields are on the Job Entry form as ‘Tag’ components (checkbox with a color bar).
I expected that because the control is linked to the data field via EpBinding, the control state would be Read Only or Disabled when the field security defines the field as Read Only.
Instead, the control behaves normally (acts editable), but upon saving, the field value resets itself.
Am I missing a step? Is the control state (enabled/disabled/readonly) supposed to be managed automatically, or do I need to do it manually somehow in App Studio?
Per your screenshot you’ve set the default access to Read.
At the bottom I can see the PLANNING security group has default access,i.e Read.
PLANNING_APPROVAL has full access. Any user in this group will have read/write access the field, regardless of what you have the default access set to.
Are users in PLANNING group only still able the check the box? That would be unexpected behavior. Expected behavior is that the checkbox would appear as read only as long as the user is not a member of a group with full access (or a security manager)
Correct, PLANNING_APPROVAL is the only group that has read/write access to that field. Every other group has read only access.
What we are seeing is that anyone that is not part of the PLANNING_APPROVAL group is still able to interact with the checkbox normally, but when they save the record, the checkboxes revert to their previous value. So they are being prevented from committing any changes to the field, but from a UI standpoint it appears like they can still check/uncheck it.
