Two of our partners discovered a quirk with the new Universal Login Access (ULA) Jump registration process this week; they had customers with two first names such as ‘Ann Louise’ or a two part last name such as ‘de Beer’. Both registrations failed to progress, instead they got that annoying little red prohibition sign:

It turns out that this is a known limitation of the new sign-in process. It is a character lock that does not accept special characters, including hyphens and spaces. So the solution is simple, stick with just one first name and one last name.
For the above examples, ‘AnnLouise’ would be fine, as would ‘deBeer’.
If their surname has a hyphen, we would take away the hyphen?
LikeLike
Yes, but don’t leave a space; a space is recognised as a forbidden special character.
LikeLike
Is there a plan to fix this please? It seems a shame to make even tiny adjustments to people’s names and feels like it could be problematic in the future -with accessing their accounts.
LikeLike
I have been advised that this is not an easy fix, I’m afraid, but is on the list.
LikeLike