This is implemented same way as it is on UI. This is only for dependents.

This jira is kept on Hold for testing till the related enhancement WT-6478 is completed. As we need to verify the change through UI as well. So, changing the Status accordingly.

Environment: LB
Company: Caiso and MBF
Import Template:
StarSSNImportForDependent_Child
StarSSNImportForDependent_Spouse

Scenarios Covered:
Existing Employee: Added Spouse, ExSpouse
Existing Employee: Added Child [Natural, Step], ExSpouse

For all above scenario * was imported successfully and no * is appearing on Spouse and Child page as required.

Need to check the Employee Template for SSN as *

Priya Dhamande, JUST FYI, this implementation is for Dependents only for employee we do not allow NULL SSN.

yes Jaideep Vinchurkar, for testing Impact I will be checking for employee as well.

Ankur Deshpande
This patch was already deployed 5 days back but in today's LB patch it went again.
Any code changes we made on it?

Please let me know, as I need to test again otherwise.

Environment: LB
Company: MBF
Import Template:
StarSSNImportForDependent_Child
StarSSNImportForDependent_Spouse

The Import for '*' for dependent is verified on LB and it is imported for multiple and single input. Above mentioned scenarios worked well, so moving jira on Stage.

Environment: Stage
Company: Wheaton Franciscan Healthcare OE 2017 For HSPL
Import Template:
StarSSNImportForDependent_Child
StarSSNImportForDependent_Spouse

The Demographics Import for '*' for dependent is verified on Stage and it is imported for multiple and single input. Above mentioned scenarios worked well, so moving jira on Production.

Environment: Production
Company: Wheaton Franciscan Healthcare OE 2017 For HSPL
Import Template:
StarSSNImportForDependent_Child
StarSSNImportForDependent_Spouse

The Demographics Import for '*' for dependent is verified on Production for Spouse and Child and it is imported for multiple and single input. So, closing jira on production.