Overview

This feature builds upon the standard text input by providing the option to make the email input field read-only. When an email input field is set to read-only, users can view the content but cannot modify or edit it. This functionality is particularly beneficial in several scenarios:

​

1. Preventing Errors in Customer Interaction:
   During a customer interaction, such as a call, an agent may input the customer’s email address based on verbal communication. Once entered, the field can be made read-only to ensure the email address remains accurate and protected from accidental changes. For instance, if a customer provides their email verbally, the agent can confirm it by setting the field to read-only, avoiding any unintended modifications.

2. Verifying Pre-Existing Email Addresses:
   When a company already possesses a customer's email address, making the field read-only ensures that customers cannot unintentionally alter it. For example, during a verification process, the company can display the stored email address in a read-only format to confirm its correctness with the customer while maintaining accurate records.

3. Enhancing Privacy and Security:
   A read-only email input field can help safeguard the customer’s email address by preventing unauthorized changes. This approach ensures better privacy and protects sensitive data during interactions.

Additionally, the component includes an option to define disability conditions, enabling the input to be entirely disabled for specific users when required. This feature provides added flexibility and control over how the email input field is used in various contexts.

​

Various Fields in Email Input

​

• Placeholder: It specifies the name of the field displayed in the system.  

• Regex Pattern: The Pattern attribute enforces that the value entered in a field adheres to a specified format by using a regular expression. This ensures that the input meets the required structure or syntax, reducing errors and maintaining data consistency. 

• Default Value: The default value for the component is a pre-populated entry displayed when the form or input field is initially loaded. This value can be either a static text entry or dynamically sourced from a variable.

• Restricted Keyword Lists: It is a multi-select configuration field. It enables you to assign one or more predefined keyword lists. If your input contains any terms from the selected restricted keyword lists, an error message will be triggered. This message is configurable once you enable the Configure Error Messages toggle. This feature helps you maintain better input quality control and enforce compliance with or content guidelines dynamically within your workflow.

• Enable Reporting: Once this feature is enabled, you can utilize email input for reporting purposes.

• Configure Error Message: This field allows you to create a warning message for users in the following conditions:

  • If the value is required.

  • If the value entered does not match with the regex supported.

  • If text entered has restricted keywords.

• Visibility Conditions: It is a rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 

    • Implementation: Visibility Condition: Ticket_Priority == 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets.