We have a metadata field assigned to a template that is meant to gather social security numbers. We have noticed that some people entering the information are mistyping the SSN. Is there a setting on a field level to require the user to input the value twice to make sure they match as a level of QA?
Question
Question
Answer
I file an enhancement request to have some way of validating manual user input of metadata. It may not necessarily be re-typing the field value, but we'll look into it.
Replies
When you say mistyping, are you referring to formatting, i.e. they are only entering in eight digits instead of nine for the SSN? Or do you mean that users are just entering in the wrong digits in general although the format itself is fine?
They are entering the correct number of digits, just the wrong ones. I think this would happen less often if we could make them have to enter the SSN twice.
I file an enhancement request to have some way of validating manual user input of metadata. It may not necessarily be re-typing the field value, but we'll look into it.
I think just adding an option when setting up a field called "Double Entry" would suffice. So if checked, any time something is typed into the field and they move from that field, it would give a prompt to re-enter the value. If it doesn't match it removes the value that was entered.