Hi All, Need your Help. Could we remove asterisk (*) sign from appian text field as a validation, Please suggest if anyone have any idea on this. Thanks Amit

Yes you can. If you put that textField in a validation group, it removes the asterisk (*) sign from the text field. For more information on validation, please look for validationGroup

You can (as per Harshit's post)...but I'm curious as to why? What's the use case?

Actually Client wants such scenario, so i am looking for the same.

Did validationGroup help you?

(*) symbol is used to validate the required data, if you do no want to use required as true, you can have field level validation or you can use section validation at the end of the page, which can display once you click on Submit button.

The bigger question would be WHY?  Why do you want to remove the clearest indication you could possibly have to the user that this is a required field?

Incidentally, I think you can include validations for any number of things whether the field is required or not.  You could make the field not required, but a validation message appear in red text when it's null, you'll get the red validation text in addition to the field being surrounded by a red line when you attempt to submit, and the red text may appear when the form first loads.  But again, what is the advantage of not showing the user the requiredness of the field?

Thanks for information !

Thanks for information !

At least for my use case it has to do with 508 compliance. When the users that is visually impaired is going though a form with a bunch of fields that have required = true all they hear is "is required asterisk". So they want the asterisk removed

brianaj0155 said:

all they hear is "is required asterisk".

Seems like this is an issue you should take up with the people who maintain your screen reader software.  I don't see any advantage in NOT notifying users that a particular field is required, but if the style of the current notification is too cumbersome, then they should try to remedy that issue where the issue lies, instead of breaking appian to sidestep the issue (and potentially increasing confusion and user frustration as they miss required fields they didn't know about).