COmanage Users List

[Benn Oshrin <>]

Well, if they want to change something or they forgot, disallowing an 
additional enrollment seems like the correct behavior. Admin 
intervention sort of makes sense. I think the question here is what 
behavior are you expecting?

Right now, petitions are simply not modifiable once submitted. I suppose 
we could allow someone to go back and change something, but only until a 
petition is reviewed. This would require a fair amount of development.

If the user forgot they submitted a petition, isn't the correct thing to 
reject the second attempt? What are they trying to accomplish? Perhaps 
they need a new confirmation link?

We can't really trap this earlier because until we have the 
authenticated identifier we can't know it's them. We do have plans to 
improve identity match during petition data entry, but that really only 
conceptually works for administrator driven enrollment, not self 
service. (It's also plausible we could grab the identifier earlier, but 
I'd have to review the existing flows to confirm. I vaguely recall 
something complex that makes it difficult to do so.)

Thanks,

-Benn-

On 6/20/14 7:56 PM, 

 wrote:
> Users are going thru self-enrollment, and are sometimes enrolling twice.
> Sometimes this is because they want to change some detail, or they simply
> forgot.
>
> We are using email confirmation, and when they try to confirm either
> invitation, they get an "identifier already in use" error.
>
> It looks like a person record gets created for each enrollment, and before
> confirmation.  The user is stuck until we delete one of the people records.
>
> Is there anyway we can trap this scenario earlier so admin intervention is not
> required?