Hi Damion M Velasquez,

Concern: Cobra reason went as Divorce for removed child.

Cause: We have checked the details of mentioned employee, As per analysis we found that When EE Timothy Benbow Removed child, Enrollment got terminated but on the event builder, There is no such event present which can be captured due to termination, However after that EE Change the Spouse relationship from spouse to Ex-Spouse, So because of this Divorce event got satisfied and that reason went over the file.

Same scenario happened with other mentioned employees.

Correction: We need to discuss this with Amit Thorve.

CC-Prashant Samal, Ganesh Sadawarte, Rajendra Pawar, Vinayak Kulkarni

Hi Damion,

We have checked this and found that records for child should not have been populated on file.

However they are populated and that too with incorrect reason code. We are working on fix and will let you know once it is done. Please ask discovery benefits to ignore this event. Thanks.

Tracy Kot Do you have anymore to add fort this one?

Please advise
thanks

Vinayak KulkarniThe Fix can you link the support ticket?

Thank you

CC Deborah Mascot

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Attached is the unit testing document - Dev Tested Scenarios.xls

Below cobra events has been tested in unit testing.

• Employee Termination
• Divorce- Spouse to Ex-Spouse
• Overage Dependent
• Retired
• Class Change

Getting server error ,while verifying following scenarios
1)Employee termination
2)Retired
3)Class change

Hence,It is* blocked* to test this bug .

*Error Log- *
ErrorID : 0
ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->Employee.Save->Employee.UpdateEmployeeClass->Employee.GetEffectiveDateForEnrollmentMode
ErrorMessage: Conversion from type 'DBNull' to type 'Date' is not valid.

Hence assigning this to you,once it gets fixed , reassign back to me .

Thanks,
Swapnil Eksambekar.

CC-Aniruddha DevRakesh RoyHrishikesh DeshpandeRajendra PawarVinayak Kulkarni

Umesh Kadam A new issue that I am not sure relates to this or not Steven Golubski terminated COBRA Eligible Benefits 11/20 and should have rolled out in the file 11/24. This was done in the OE Window I think as an Employee Data Change. Can you tell us why his record didnt pass? This is is a VP that termed so it is a Highly Sensitive issue

Thank you

CC Andrea DennisKristi SmithKevin WalkerVinayak KulkarniRajendra PawarHrishikesh DeshpandeAniruddha Dev

Hi Damion,

here are details for Steven Golubski not populated on cobra file.

Steven Golubski is terminated from WT on 11/15/2017 via scheduled import, see below

But employee's enrollment did not terminate due to import back-end routine failed and file exported on 11/17/2017, so for this export it found enrollments active and thus it did not roll out on file

and on 11/20/2017 SA terminated elections as part of data correction.

Note: We found one more employee "Brandon Stanley" terminated on same import and did not populate on cobra file.

let us know if you want these records to be forced on next cobra file. Thanks.

As discussed, We have forced these records from back-end, it will populate on next export. Thanks.

Hi Swapnil Eksambekar,

Please find below 3Cs:

Thanks,
Snehal Shabade

Cc:Umesh Kadam

Verified following COBRA EVENT scenarios -

• Employee Termination
• Overage Dependent
• Retired
• Class Change

Above mentioned scenarios are working as expected.
Testing is in progress for Ex-Spouse or Divorced Cobra event.

CC-Aniruddha DevHrishikesh DeshpandeRakesh Roy

Verified for Ex-spouse or Divorced Cobra event along with all mentioned scenarios in above comment,It is working as expected.
Ready for Stage deployment.

CC-Aniruddha DevHrishikesh DeshpandeRakesh RoyVinayak Kulkarni

Hi All,

This ticket has been approved for stage deployment on 12/21/17.

Regards
Gaurav

This Issue is deployed on Stage. We will test it and update on Tuesday, 12/26.

Below cobra events has been verified on Stage :-

• Employee Termination
• Divorce- Spouse to Ex-Spouse
• Overage Dependent
• Retired
• Class Change

It is working as expected.Ready for Production deployment.

CC-Aniruddha DevRakesh ShahaneHrishikesh DeshpandeRakesh RoyGaurav Sodani

Unable to test below scenarios ,

• Employee Termination
• Divorce- Spouse to Ex-Spouse
• Overage Dependent
• Retired
• Class Change

It is blocked to test due to wt-12931 ,as It is getting server error.Once it gets resolved , reassign to me.

CC-Aniruddha DevHrishikesh DeshpandeRakesh RoyVinayak Kulkarni

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Hello Damion M Velasquez,

We have deployed and verified this fix on production today
Verified all below scenarios :-
Employee Termination -Pass
Divorce- Spouse to Ex-Spouse -Pass
Overage Dependent -Pass
Retired -Pass
Class Change -Pass

Can you please check this at your end and close this JIRA ?
Please let us know in case of any queries or issues.

CC-Aniruddha DevHrishikesh DeshpandeRakesh RoyGaurav SodaniVinayak Kulkarni