Set invalid message of email input field

Function: Set invalid message of email input field

This action allows you to define a specific error message that appears when a user enters invalid information into an Email Input Field on your application. Instead of a generic error, you can provide a custom, helpful message that guides the user to correct their input.

Input

• UI element (PART): This is the specific Email Input Field on your form or page that you want to target. You must select an existing Email Input Field from your application's design.
• Invalid message (STRING): This is the custom text message that will be displayed to the user if their input in the selected Email Input Field is considered invalid (e.g., not a valid email format). If this field is left empty, any previously set custom message will be cleared, and the field will revert to showing a generic system error or simply being marked as invalid without specific text.

Output

This action does not return a direct value. Instead, it modifies the behavior of the selected Email Input Field by setting the custom error message that will be shown when the field's content is invalid.

Execution Flow

Real-Life Examples

Example 1: Customizing a standard email field for user registration

Imagine you have a user registration form with an email input field. You want to provide a very specific instruction if the user enters an invalid email format.

• Inputs:
  • UI element: User_Registration_Email_Field (an Email Input Field on your registration form)
  • Invalid message: "Please enter a valid email address, e.g., [email protected]. We need this to send you a confirmation."
• Result: If a user types "myname" into the User_Registration_Email_Field, the custom message "Please enter a valid email address, e.g., [email protected]. We need this to send you a confirmation." will appear below the field, guiding them to correct their input.

Example 2: Providing specific feedback for a newsletter subscription form

On your website, you have a newsletter subscription form. You want to make sure users understand the email format required for subscription.

• Inputs:
  • UI element: Newsletter_Signup_Email (an Email Input Field on your newsletter subscription page)
  • Invalid message: "Oops! This doesn't look like a valid email for our newsletter. Double-check your entry to receive updates."
• Result: If a user submits the Newsletter_Signup_Email with an incorrectly formatted email (e.g., missing "@" symbol), the specified message will be displayed, prompting them to re-enter their email correctly for subscription.

Example 3: Clearing a previously set custom message

You previously set a custom invalid message for an email field, but now you want to remove it and let the system handle generic error messages.

• Inputs:
  • UI element: Contact_Form_Email (an Email Input Field on your contact us page)
  • Invalid message: (Leave this field empty)
• Result: Any previously set custom invalid message for the Contact_Form_Email will be removed. If the field becomes invalid, it will now show a generic system error message or simply be highlighted as invalid without specific custom text.