-
Type:
Bug
-
Status: In Progress
-
Priority:
High
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Company:All Clients/Multiple Clients
Environment: Pre Prod
There are some scenarios where we can update the user's primary email, that should not happen.
Create a document template, map the user email and other fields as optional.
**
1) During sending the form.
If you will update the user's email with random text it will allow you to put any text and save it. And this will update the user's primary email with that text.
2) During review and sign
**the same scenario here. If the user will replace his email with random text, the system allows updating that.
poonam.rana Please verify it again and update the status accordingly.
Hi Narendra Kumar,
Above reported scenarios are still exists , Can you please have a look and fix them.
Thanks,
Hi Samir
I have fixed the issue in the way we discussed in the call. Now I just need the info message that we need to put for the email address view-only.
Hi Samir
I did the analysis on this flow and found this.
CASE 1:
If a registered candidate updates the email with a new email that is not in the system. It will update the email with the new one.
Now if you send any document to an old email, it will treat it as a new user and create a new user which is fine.
CASE 2:
If a registered candidate updates the email with the new email that is already into the system. It will update the email with the new one. (That should not happen).
Now we will have the two accounts with the same email id.
Now if the admin sends any document to this email, it will always go to the older account which was created first.
Created card for this: DMS-2470
CASE 3:
If Admin or candidate updates the email with random text or any number, the system will update it. (That should not happen). Because for the next time admin could not send any document to that candidate on that random text. In this way, we lost the candidate for always.
Created card for this: DMS-2469
Hi Prateek
Please test this issue again, Check if it still exists.