When a Password (2 way encrypted) field is not populated on a record, the form still renders a value in the text box.DescriptionWhen a two-way encrypted field Password is not populated on a record, the form still renders a masked value in the text box, creating confusion for users, and not allowing options to set or check if mandatory or if auto-populated. Steps to Reproduce 1. Create a new field on the Incident table, of type Password (2 way encrypted)2. Add the field to the default view on the Incident form.3. Create a new incident record. Do not populate the new password field.4. Save the new incident record. Observe the Password field content shows asterisks, as if auto-populated with some value in the background.5. If running a background script to query the content of the password field, this shows blank.WorkaroundThis behavior is by design. As a workaround, you can create a new UI Policy as described below for non-scoped applications only (i.e. Incident) NOTE: The client-side GlideRecord API is not supported in scoped applications. Instead, create a script include and use the GlideAjax API, or use the REST APIs. - No conditions- Run Script = Checked- Execute Script if true: var gr = new GlideRecord("<table>");gr.get(g_form.getUniqueValue());if(!gr.<password_field>) g_form.clearValue('<password_field>');Related Problem: PRB1250313