Hi Cindy Wibbing,

Please find below details.

Concern: Why Medical, Dental and Vision record's are exported on 01/19/2017 for Debra Touchette.

Cause: As we checked Debra Touchette previously enrolled in medical , dental and vision with EE+SP and on 1/6/2017 new coverage get added due to this new enrollment's get added to system with EE+SP+CH. The below templates are changes only templates and both template has previously exported on 1/5/2017 and above changes are made on 1/6/2017, due this it was roll out on 1/16/2017 export. Please find below medical,dental and vision enrollment details snap.

Templates:

• Payroll_El Dorado_DV_2016
• Payroll_El Dorado_Medical_2016

CC-Vinayak Kulkarni

Please let us know if require more details

Thanks,
Ganesh

Ganesh Sadawarte
The issue with Touchette is that the dental and vision came on the 1/5 file. They are saying the election was pending and should not have exported.

Also, did you have a chance to look at the other issue:
Angela Weide had no changes for any fields associated with the Medical file and did not export as expected but elections did come on the Dental/Vision file on 01/19/2017. Need to know why the elections for Angela Weide exported on the Dental/Vision export file.

Hi Cindy,

Please see below details,

For employee Debra Touchette, Dental and Vision was never pended, only Medical was pended and it was approved on 01/06. Dental and Vision should have pended and our enrollment team is looking into it.

For Angela Weide, dental and vision election were updated on 01/13/2017 due to employee data change. Actually there is no change in election information due to which it can't be seen on screen but we have seen record is modified which led it to populate on export file. Ideally this should not have been updated at all and our enrollment team is looking into this and will share the details.

Jyoti Mayne Can you take look into this. Thanks.

Jyoti Mayne
Do you have any updates on this ticket?
Thanks,
Cindy

cc Abhay Patil

Hi Hrishikesh Deshpande,

Issue 1 :
Election of Contingent Force Plans are not going in pending queue.

Employee Name : DEBORAH TOUCHETTE
Qualifying Event : BIRTH-ADOPTION
Qualifying Event settings :
IsVerifycationFlag is Yes.

this employee is enrolled in plan 'Kaiser HMO' (benefit type : medical) with Effectivedate '1/1/2017' .

Force Plan : -

1. Delta Dental PPO Premier
2. VSP Vision

this issue is not getting introduce at our end. Please help up to reproducing this issue and share your findings with client.

Issue 2 :
Force contingent enrollments are getting updated by employee data change.
there is no actual change in enrollment, it is just updating enrollment date-time stamp.
For this issue please refer WT-8485.

CC :Jaideep Vinchurkar

Hi Prasad,

Can you please take this forward with your team?

Regards,
Aniruddha Dev

Because of the other prioritized items - we have not started testing this yet.
We will take this to reproduce soon and update the status.

Hi Vinanti Yadav,

CC:Rakesh Roy,Hrishikesh Deshpande,Jyoti Mayne,Alankar Chavan,Jaideep Vinchurkar

I have verified this issue as per employee DEBORAH TOUCHETTE view history and it is getting reproduced below are the steps:

Admin Login/partner login:

1] Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan Kaiser HMO plan Dental and vision plan are contingent so it was also enrolled with same effective date.

Employee Login:

2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical Plan Kaiser HMO plan medical plan going for Admin Approval pending but force contingent plan Delta Dental PPO Premier and VSP Vision are not. refer below screen shots:

Thanks,
Rashmita

Hi,

Please find below 3Cs details :

Please find below Impacted scenarios/areas :

• Accept/Reject scenarios (for child and parent)
• Approval Pending added on Parent only, QE only, both parent and QE, none of parent and QE
• Forced and normal contingency scenarios for parent and child plans

Impacted areas should be tested using :

• Enroll Now screen
• Employee Data Change
• Import
• Pending Queue
• Also using Admin and Employee Login
• Also test scenario(s) of related JIRA ticket i.e. WT-8485

Thanks and Regards,
:: Umesh Kadam

CC : Jaideep Vinchurkar, Jyoti Mayne, Vinanti Yadav, Hrishikesh Deshpande

Verified this issue on Lb Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
Scenario 1: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision

Scenario 2: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.

Scenario 3:Pending Queue when we Reject Medical plan then contingent plan should be rejected also.

this scenario 3 is not working it will not reject contingent plan
refer pending queue screen shots

Hi Rashmita Dudhe,

As discussed, issue which you have reported in your recent comment is scenario specific and not caused due to code fix of this bug. Please check and confirm.

Thanks and Regards,
:: Umesh Kadam

CC : Jyoti Mayne, Hrishikesh Deshpande, Prasad Pise

Verified this issue on Lb Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision

Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.

Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected

found one scenario specific issue created jira :WT-10501 with this known issue changing status as ready for stage

Verified this issue on Stage Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision

Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.

Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected

found one scenario specific issue created jira :WT-10501 with this known issue changing status as ready for production

Verified this issue on Production Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision
Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.
Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected

Hi,

This is deployed and verified on Production.
While testing found one existing issue Jira:WT-10501 which is under development.

Kindly, Check and Update this jira accordingly.

Thanks,
Rashmita

I have not had any additional issues reported. Closing ticket