Controlling visibility of a field through UI Policy/Client Script which is set to mandatory at dictionary level.SummaryFor a field that is set to mandatory at the dictionary level, you cannot hide it using a UI policy by simply setting visible = falseThe field will be hidden, but upon submission you would get a error message. From the dictionary level, you cannot set conditional properties (mandatory or read only) to a specific field.For conditional properties you should always go with Client Script or UI Policy.ReleaseAll releases.InstructionsScenario 1: Lets take the incident form, and the OOB (out of box) reference field - Configuration Item.Create a new field - Field 1 on incident form (reference field to any other table of your choice)Configure the dictionary entry for Field 1 and set to mandatory true.Now create a UI policy with condition Configuration Item ISNOTEMPTY (Set Global, Reverse if false, On load = true)In the UI policy actions, we create a action for Field 1 (Visible = false)6. Navigate to a new incident form.7. Give a value to Configuration Item 8. Field 1 should be hidden now9. Now try to submit or save the form. It will throw an error message.10. Now navigate to Agent Workspace.11. Click on Agent Workspace Lists, and create a new incident.12. Give a value in Configuration Item13. Field 1 is still visible and UI Policy is not honored. Correct way to implement this Lets take the incident form, and the OOB (out of box) reference field - Configuration Item.Create a new field - Field 1 on incident form (reference field to any other table of your choice)Configure the dictionary entry for Field 1 and set to mandatory true.Now create a UI policy with condition Configuration Item ISNOTEMPTY (Set Global, Reverse if false, On load = true)In the UI policy actions, we create a action for Field 1 (Visible = false, Mandatory = false)6. Navigate to a new incident form.7. Give a value to Configuration Item 8. Field 1 should be hidden now9. Now try to submit or save the form. You will be able to save the form successfully.10. Now navigate to Agent Workspace.11. Click on Agent Workspace Lists, and create a new incident.12. Give a value in Configuration Item13. Field 1 is hidden, and UI Policy is honored in this case. Related LinksThe reason for this behavior is dictionary will always have a higher precedence for the properties of a particular field.You need to explicitly mention the property in UI policy the if you wish to over ride a dictionary property.