Is it possible to validate that an input is of type email, so that if the user enters something that is not an email, a warning can be showed?
Discussion posts and replies are publicly visible
Usually for validating email we use Regex code , it is going to check the format of the entered email text . Not sure what you are looking for , can you give more details of your usecase?
and how do u use a regex code in an input?
lumi29 Replace the value in the "^[a-z0-9]+(\.[a-z0-9]+)*@[a-z0-9]+(\.[a-z0-9]+)*(\.[a-z]{2,5})$" with a constant.
if( a!isNullOrEmpty(ri!input), null, if( regexmatch( "^[a-z0-9]+(\.[a-z0-9]+)*@[a-z0-9]+(\.[a-z0-9]+)*(\.[a-z]{2,5})$", ri!input ), "", "Please enter a valid email address" ) )
if( regexmatch( pattern: "\b[\w\.-]+@[\w\.-]+\.\w{2,4}\b", searchString:ri!your_Variable, regexFlags: "si" ), "", "Please Enter Valid Email" )
On validations , regex code gonna check whether entered email is in right format or not. Search online for better Regex codes which suites you.
The function 'regexmatch' is unavailable. :(
https://community.appian.com/b/appmarket/posts/regular-expression-functions , Use this plugin
Do you have access to admin console in your environment? If yes, then navigate to Plug-ins and add new plugin "Appian Regular Expression Functions"
If you mean you want to validate that a particular string is a valid email address, the People Funcitons plug-in currently has a function, validateemailaddress(), which validates email addresses as well as any Regex pattern or OOB appian expression can do (and i know because i've written both in the past from scratch).
If you go with the RegEx approach as other commentors have suggested here, the best pattern I've found so far which accepts the largest range of valid email addresses, is as follows (this is the actual expression rule I currently use):
regexmatch( pattern: "^[A-Z0-9\'\+\&\%_-]+(\.{0,1}[A-Z0-9\'\+\&\%_-]+)*[@]{1}[A-Z0-9.-]*[A-Z0-9-]+[.]{1}[A-Z]{2,6}$", searchString: ri!email, regexFlags: "si" )
Note, the "validateEmailAddress()" function in People Functions currently passes the same extensive list of test cases as the above expression rule, and is a little easier to use routinely.