-
Type:
New Feature
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Company:All Clients/Multiple Clients
-
Epic Link:
Below scenarios needs to be tested:
Data in below Person table columns for a use should come as encrypted when mapped in a document:
Ethnicity, DateOfBirth, LegalId
After mapping above columns in a document, admin and candidate is able to fill data for above fields, and submit.
After signing the docuemnt, data in above fields is coming fine.
- relates to
-
DMS-2366 Modify schema to support encryption
-
- In QA Testing
-
-
DMS-2367 Migrate existing data to new encrypted columns
-
- In QA Testing
-
-
DMS-2368 Update all SPs, Indexes to support encryption
-
- In QA Testing
-
-
DMS-2369 Update backend code to manage master key and store company Key in session
-
- In QA Testing
-
-
DMS-2370 Update SP calls to pass company decryption key
-
- In QA Testing
-
-
DMS-2371 Update all insert queries on code to support encryption
-
- In QA Testing
-
-
DMS-2372 Update update queries to support encryption
-
- In QA Testing
-
-
DMS-2373 Update get queries to support encryption
-
- In QA Testing
-
Hello Harshveer Singh,
I have tested the above scenario multiple times in DMS Workterra. After mapping of fields , submitting and signing the data, it is not Working as Expected. "Legal ID" column is still displaying NULL values.
Thanks,
Poonam Rana