The analysis document is not ready as the approach was not fixed. It was fixed after discussion with Amit on Wednesday. We'll attach the document soon.

Affected Files: Affected Files.txt

Impacted areas :

• Employee Import Uniqueness
• Spouse Import Existinng / New
• Child Import Existing / New

only data import is affected and not the back end routines.

Unit Testing Done:

1. Child Import new Child with DOB not given
2. Child Import new Child with DOB given
3. Spouse Import new Child with DOB not given
4. Spouse Import new Child with DOB given
5. Child Import existing Child with DOB not given
6. Child Import existing Child with DOB given
7. Spouse Import existing Child with DOB not given
8. Spouse Import existing Child with DOB given
9. Spouse / Child Import with no unique field / one unique field / multiple unique fields
10. Employee Import with no unique field / one unique field / multiple unique fields

Environment: LB
Company: Symphony
Login: Partner
Template: spouse Effective and Child Effective

Scenarios covered are attached with jira along with updated Test cases

All scenarios worked as expected. So, moving jira on Stage.

Hi Suraj Sokasane,

Verified on Stage
Company- Caiso for hspl

Verified all the scenarios mentioned in Testcases_ScenariosUpdated document.
Working fine as expected.
But during testing we have encountered an issue of import fail when dependent effective date is marked as unique.
Please refer linked jira for the same.

Other scenarios are working well.
Marking item state as stage on hold till WT-9259 issue fixes.

Thanks,
Jayshree

CC: Rakesh Roy Prasad Pise Priya Dhamande Hrishikesh Deshpande

Hi Suraj Sokasane,

Verified on Production
Company - Long for hspl
Verified all the scenario
Working as expected.
Marking item state as production complete.

Thanks,
Jayshree

CC: Rakesh Roy Prasad Pise