New applicant portal - limiting contact input to one

Kayte Wisor

We have encountered in our testing what is apparently already a known issue - even if you limit the applicant to only entering one contact, the system will let them keep entering them, and not show an error until they go to submit. When corrected (and the applicant goes back to delete the additional contacts that shouldn't have been permitted) we found that the application froze and the user was unable to submit. This happened multiple times in testing and support told me it was “known and intentional”, so just wanted to let others know. Ideally if you limit to one entry, people would only be able to enter one entry.

Valerie Marshall

@Kayte Wisor
As of mid-January, it still allows applicant to enter > 1 contact, but does display the error. We did not freeze with that error, thankfully.

Kayte Wisor

@Valerie Marshall Thanks for the update Valerie. What I heard from Support is “According to Product Management, this is working as-designed. They do understand that it is counter-intuitive, and are conferring with the development teams, but for now this is how it works.”

Monica Jordan

@Kayte Wisor Thanks for sharing your experience. I also find it counter-intuitive that the system doesn't flag the error to the grantee at the time. I'm running into this with project start/end dates. The applicant is able to submit the application, but then I'm unable to consider the request due to the error! I have to send back to the applicant for resubmission….. it's just odd to me that the system can't flag the error sooner in the process….

Tonya Conaway

@Monica Jordan we ran into the same issue. The applicant typed to many characters for a designation, and it allowed them to submit without giving them an error but I was not able to consider the application.