Template name: JE DUNN_Discovery Cobra QB_IN_Use_NEW 2017
11/3 file
1. Timothy Benbow is the EE; ISABELLA PIPARO - dependent Child removed during OE:
2. Jesus Plata is the EE, we sent Eryn Eberlein - Divorce QE VERY OLD 2016 Divorce, back in 2016:
11/10 file:
1. EE is Dirk Schafer, removed child Carolyn Schafer form Medical/RX this also went over as a Divorce QE
Can you look at the settings? We dont think this should pass this way
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.
Rakesh Shahane (Inactive)
added a comment - - edited 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
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.
Vinayak Kulkarni (Inactive)
added a comment - 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.
Rajendra Pawar (Inactive)
added a comment - 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 .
Swapnil Eksambekar (Inactive)
added a comment - 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 Dev Rakesh Roy Hrishikesh Deshpande Rajendra Pawar Vinayak 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
Damion M Velasquez
added a comment - 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 Dennis Kristi Smith Kevin Walker Vinayak Kulkarni Rajendra Pawar Hrishikesh Deshpande Aniruddha Dev
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.
Vinayak Kulkarni (Inactive)
added a comment - 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.
Getting server error while changing EE status as terminated
Cause
In "JE Dunn" company, 'Terminated' employee status is not selected for any New Hire / Re-Hire Rule due to which terminated employee is not eligible for any rule. And hence system gets 'null' value for effective date which is causing server error
Correction
Select 'Terminated' status for respected new hire / re-hire rule.We have tested the same in local and it is working fine. Please check and confirm.
Snehal Shabade (Inactive)
added a comment - - edited Hi Swapnil Eksambekar ,
Please find below 3Cs:
Concern
Getting server error while changing EE status as terminated
Cause
In "JE Dunn" company, 'Terminated' employee status is not selected for any New Hire / Re-Hire Rule due to which terminated employee is not eligible for any rule. And hence system gets 'null' value for effective date which is causing server error
Correction
Select 'Terminated' status for respected new hire / re-hire rule.We have tested the same in local and it is working fine. Please check and confirm.
Thanks,
Snehal Shabade
Cc: Umesh Kadam
Swapnil Eksambekar (Inactive)
added a comment - 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 Dev Hrishikesh Deshpande Rakesh Roy
-Discussion with umesh related to issue
-Company attach to local,script execution,
-Code debug fro EE status change,
-Analysis on generic eligibility rule of New/Re-Hire Rule And SP of calculating effective date,
-Share the details with umesh
-update the jira
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.
Swapnil Eksambekar (Inactive)
added a comment - 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 Dev Hrishikesh Deshpande Rakesh Roy Vinayak Kulkarni
Swapnil Eksambekar (Inactive)
added a comment - 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 Dev Rakesh Shahane Hrishikesh Deshpande Rakesh Roy Gaurav Sodani
Swapnil Eksambekar (Inactive)
added a comment - - edited 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 Dev Hrishikesh Deshpande Rakesh Roy Vinayak Kulkarni
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.
Swapnil Eksambekar (Inactive)
added a comment - 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 Dev Hrishikesh Deshpande Rakesh Roy Gaurav Sodani Vinayak Kulkarni
Bug
Critical
Jennifer Reed (Inactive)
made changes -
Gaurav Sodani (Inactive)
made changes -
Khandu Kshirsagar (Inactive)
made changes -
Shailendra Honrao (Inactive)
made changes -
Snehal Shabade (Inactive)
added a comment - - edited Hi Swapnil Eksambekar ,
Please find below 3Cs:
Concern
Getting server error while changing EE status as terminated
Cause
In "JE Dunn" company, 'Terminated' employee status is not selected for any New Hire / Re-Hire Rule due to which terminated employee is not eligible for any rule. And hence system gets 'null' value for effective date which is causing server error
Correction
Select 'Terminated' status for respected new hire / re-hire rule.We have tested the same in local and it is working fine. Please check and confirm.
Thanks,
Snehal Shabade
Cc: Umesh Kadam 
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