The "is empty string" operator in a UI Policy may not work as expected - Known Error

The "is empty string" operator in a UI Policy may not work as expected Description In a UI Policy, the "Is empty string" operator may not work as expected, as opposed to the "is empty" operator.

Steps to Reproduce

Navigate to Incident > Create New . Right-click on the header bar and select Configure > All . Go to the UI Policies section or tab. Click New . In Short Description , add text. In When to Apply , set any string field to Is empty . Right-click in the header bar and select Save . In the UI Policy Actions section or tab, click New . Add a condition for any field. For example, set the Knowledge field to read only. Click Submit . Navigate to Incident > Create New . Create a new incident. The UI Policy is not applied. Workaround This is expected behaviour. Unless it is set with a script, a field should not contain the empty string. We use null for fields that have no value, which the operator "is empty" will match. Use "is empty" instead. The operator "is empty string" is designed to do something different from comparing with null.