-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CBAT Offer Letter - Fall
-
Labels:None
-
Company:All Clients/Multiple Clients
Environment: Preprod
Login: Admin and Candidate
Browser: FF and Chrome
It is observed that User name after mapping multiple, all the instances of First is appearing redundant.
Pages:
1. Preview of HTML/ PDF or TEXT document
2. Candidate login > Profile page
3. Candidate login > review and Sign
For all document types.In DB it has only one instance.
Refer few screen capture.
3C's
Concern: Multiple mapping - Updating Multiple Mapped field should not be allowed.
Cause: When data of multiple fields are sent for saving, combined value gets saved in DB against that table resulting in double or redundant data.
Correction:
- While applying permission to multiple mapped fields, "View only" and "No rights" is allowed. Other radio button have been disabled. A note has been added for the same on permission popup.
- When document is sent, fields having view only rights have been omitted so that their data is not saved in DB.
Changes done under : DMS-1684
Ramya Tantry (Inactive)
added a comment - 3C's
Concern: Multiple mapping - Updating Multiple Mapped field should not be allowed.
Cause: When data of multiple fields are sent for saving, combined value gets saved in DB against that table resulting in double or redundant data.
Correction:
While applying permission to multiple mapped fields, "View only" and "No rights" is allowed. Other radio button have been disabled. A note has been added for the same on permission popup.
When document is sent, fields having view only rights have been omitted so that their data is not saved in DB.
Changes done under : DMS-1684 Environment: Prod
Login: Admin and Candidate
Browser: FF and Chrome
Points covered in testing:
1. Able to map multiple fields
2. Validation for multiple mapped fields permission checked
3. Able to Preview document
4. Mapped fields doesnot appeared double
5.Able to send teh document
6. candidate login > Able Review and sign document successfully
All scenarios worked as expected. So, marking jira done.
same issue exists on Production Environment as Well.
Login : CBADAD/CBADAD