Vijay SiddhaSatya FYI

Hi Jaideep Vinchurkar

Lets discuss this today, Needs to taken on priority

Regards,
Samir

Jaideep Vinchurkar: Can you please update next action items based on your discussion with Amit.

Cc: Suraj Sokasane Vijay Siddha

Hi Amit Thorve ,

Currently we are looking into this issues and will update you accordingly.

Thanks !

Hi Amit Thorve

This issues can divided in two sub request,

1. Election record is getting overwritten : With current implementation of import , we update existing election of employee as per his new tier (E , E+S, E+S+C etc). so his current election are getting wipe out and only spouse or children (or both) come into picture. ideally current election must be term and employee should get new election with respect to his new tier (E , E+S, E+S+C etc).

2. If any Employee's spouse or child goes to bad, respective employee should also goes to bad : When we import any file contains employee and spouse or child (or Both), in this case if spouse goes to bad file then employee got enrollment with E Tier Only. after re-imported corrected bad file, either records goes to bad if dependent enroll separately set to "No" or got enrollment with spouse only. In this scenario, All records should goes to bad file with Employee. this request is critical and need more time to change current implementation, so we have to take this request as enhancement. we have created separate JIRA for this request WT-9056. with this implementation If any spouse or child goes to bad file , All records for respective employee will goes in bad file.

Will take #1 point with this ticket and #2 will be covered in WT-9056 and will share development plan for WT-9056.

Please let us know if you have any query.

Thanks !

CC : Jaideep Vinchurkar Satya Suraj Sokasane

Started testing on LB.

Verified Scenarios :

1) Verified election for newly added employee with retro date for Health benefit types with different tiers
2) Verified election for newly added employee with Current date for Health benefit types with different tiers
3) Verified election for newly added employee with future date for Health benefit types with different tiers
4) Verified existing election is terminated properly and new election is updated properly as per imported tier
5) Verified dependents are not able to enrolled separately through import
6) Verified dependents are enrolled properly through direct import file.

Other benefit types testing is in progress

CC - Sachin Hingole

Verified below Scenarios for other benefit types on LB:

1) Verified election for Employee life plan with retro date , Current Date and Future Date
2) Verified election for Spouse life plan with retro date , Current Date and Future Date directly through import and bad files.
3) Verified election for Child life plan with retro date , Current Date and Future Date directly through import and bad files.
4) Verified election for LTD Benefit Type
5) Verified election for HSA Plan dependent upon any other plan for retro date , Current Date and Future Date by changing tier
6) Verified election for HSA Plan
7) Verified election for service based plan
8) Verified multiple plan enrollment within same template

Working Fine.

CC - Sachin Hingole

Verified above mentioned scenarios on Stage.

Working Fine.

CC - Sachin Hingole

Verified above mentioned scenarios on Production.

Working Fine.

CC - Sachin Hingole

[~meghana.kulkarni] Are the scenario mentioned in the description tested?

Yes, Above mentioned scenarios are tested on Production.