Masked Text Field
see Text Field for more information
Last updated
see Text Field for more information
Last updated
The masked text input is a single-line plain text editor control in which the text is masked by replacing each character with a dot (•) symbol, providing a way for the user to enter data without people over their shoulder being able to see what they are entering.
Use the maxlength
and minlength
attributes to specify the maximum and minimum length of the value that can be entered.
Attribute | Type | Required? | Description |
| String | Yes | Identifies the input content. |
| String | No | Specifies a short hint that describes the expected value of the input field. |
| Boolean | No | If |
| Boolean | Yes | In case you want to include a text field with masked characters [hidden by asterisk (*) symbols] , you must set |
| Integer | No | The |
| Integer | No | The |
| String | No | Regex String to match for input validation |
| String | No | Error message returned to user if |
| It accepts a simple text and | No | The description that will be displayed when clicking the tooltip icon located on top of the Masked Text Field Element. Max length: 256 characters. Available from Symphony v20.8 and above. |
| String | Not required but it is recommended if | Definition of the label that will be displayed on top of the Masked Text Field Element. Available from Symphony v20.8 and above. |
With Symphony v20.6, bot developers can use Regex to validate text fields
and text areas
using the pattern
and pattern-error-message
attributes.
For more information and examples, refer to Regular Expressions - Regex.
The masked text field has a max number of 128 characters.
The masked text field must be a self-closing tag or have no children.
The masked text field is a feature that only hides the content in the UI. Even though it is masked in the UI, the text will be submitted in clear and processed & encrypted the same way as any other text entered in Symphony.
Compliance Officers have access to the content of the masked text field.
The following examples show masked text-fields being used as follows:
The first masked text-field (init) shows how to display a default text ("With initial value"). Note that the default text would have been sent to the payload if it had not been deleted before submitting the form.
The second masked text-field (placeholder) shows how a placeholder text ("Only Placeholder") is displayed in the UI. Please note the placeholder text is not masked nor sent in the payload if no text has been entered in the field by the enduser.
The third masked text-field (noreq) shows how a user can interact with a non-required field. Even if the field is empty (only a placeholder text is present but does not count as a value), it does not prevent the enduser from submitting the form.
The fourth masked text-field (req) shows the behaviour of the unique required field of the form, which cannot be submitted in case it is not filled; an error is displayed under the field in case the user submits the form with this empty field.
The fifth masked text-field (regex) shows the behaviour of the field when a regex pattern is entered. You can note that the pattern-error-message is displayed under the field if the input does not follow the pattern required by the bot developer.
The sixth masked text-field (min) shows how to force users to enter an input with a minimum number of characters, and how an error message is displayed under the field if the input does not respect the minlength required.
The seventh masked text-field (label) shows how a label text ("My Label") is displayed.
The eighth masked text-field (tooltip) shows how a title text ("My Tooltip/n With a second line") is inserted in the UI under the (i) icon, and how the text entered in the title parameter is displayed when the enduser clicks on the icon.