The user is able to submit a form without filling out mandatory fieldsIssue The users are able to submit a form without filling out mandatory fields that are set as mandatory via a UI Policy.ReleaseAll releasesCauseThe field is set as read-only for the user, who can submit the form, via ACLs. The fields that are set as read-only via ACLs or dictionary entry options can not be set mandatory. So, the users are able to submit a form even if there is a UI policy or a client script that is set up to make the field mandatory. Otherwise, the user would not be able to edit the field since it is read-only and never be able to submit the form in any case. Please see some of the rules about mandatory and read-only fields below: Setting a field both mandatory and read-only via the dictionary entry of the field: In this case, the field is set to read-only but NOT mandatory. The mandatory choice is ignoredSetting a field as read-only via the dictionary entry options or an ACL, and trying to set the same field as mandatory via a UI policy or a client script: In this case, the field stays read-only and the action of the UI policy or the client script is ignored.Setting a field, which is already set read-only by a UI policy or a client script, to mandatory via a UI policy or a client script: In this case, there are 2 conditions If the read-only field has some value: It becomes mandatory (* - Askteriks appears next to the field) but it still stays read-only. So, it can not be edited.If the read-only field is blank: it becomes both editable (loses read-only state) and mandatory. ResolutionThe fields that are set as read-only via the dictionary entry options or the ACLs can not be set as mandatory as it is ignored by the platform. So, the users can submit the form despite the fact that there is a UI policy that is set up to make the field mandatory. The action of the UI policy is ignored in that case.