Hi Amannda Johnson,

We have verified your above mentioned concern. Please find our observations as below:-

1] When a new dependent is added in the New Hire window the EAP updates automatically the enrollment with newly added dependent. This is as per expectation
2] When a new dependent is added in the QE window applies only when QE effective date is less than that of New Hire effective date then also the system is working as per expectation.

We have tested this on HSPL copy of Bio-Rad. The system is automatically updating the dependent in both New Hire and also in QA window. Could you provide us more information if still find this as an issue.

Thanks,
Venkatesh

QE will always have the effective AFTER the new hire effective date. The dependent newly added in the QE should then auto enroll in the EAP plan with the new effective date of the QE.

Hi Amannda Johnson,

We have verified above mentioned issue. please find below details:

1. We have added a Test EE, he get auto enrolled in EAP plan with NH.
2. Again we have added a Test dependent with QE having the effective date after the new hire effective date.
3. In this case, dependent get added automatically in EAP plan.
   

Can you please provide us list of affected employees? So that we can do more analysis for affected employees.

Thanks,
Shailendra Honrao

Cc:Amruta Lohiya,Jyoti Mayne,Umesh Kadam,Venkatesh Pujari

Test employee: ajQEtest Test
This test record was added in stage site BioRad with a date of hire of 07/26/2010. I opened up a QE date of 11/22/2017 added a new child named adminqe test. New child did not automatically get enrolled into EAP plan. Checked confirmation statement today, 11/26/2017, to see if the child got auto enrolled thinking maybe a service ran and got them auto enrolled into the EAP but NO this child is still not showing auto enrolled in the EAP plan.

Please review this test record and help test the same scenario to help duplicate the concern.

Jyoti Mayne I added another child to EE 'ajQEtest Test' and I don't see the new child autoenrolled into the EAP. Please advise.

Hi Amannda Johnson

Reported EE 'ajQEtest Test' is currently having following enrollment.

You are trying to add third child with Effective Date 11/27/17 which is between 7/1/17 and 11/30/17 (first terminated election EE tier). Hence system is not adding 3rd child .

Note: If you try to add third child with Effective date >=12/1/17, then system is automatically adding child with that date.

Note : Please add new employee and child. System is working fine. We have verified same. Please confirm from your end.

Consider following example,

• EE had election as 7/1/17 to NULL with EE tier.
• Then you add first child with 11/17/17 effective date. He will get following election.

  Sr.No	Effective Date	Termination Date	Enrollment Tier
  1.	7/1/17	11/16/17	EE
  2.	11/17/17	NULL	EE+CH1

• Again if you add second child with 11/27/17 effective date, EE will get following elections:

  Sr.No	Effective Date	Termination Date	Enrollment Tier
  1.	7/1/17	11/16/17	EE
  2.	11/17/17	11/26/17	EE+CH1
  3.	11/27/17	NULL	EE+CH1+CH2

Thanks And Regards
Abhilash Warkari

CC : Jyoti Mayne, Amruta Lohiya, Umesh Kadam

Abhilash Warkari please confirm the following: if a dependent is added prior to latest effective date for the auto enroll EAP plan the dependent will not get auto enrolled at the time of add and will not get auto enroll by any service run. We are trying to confirm that this is by system design since there could be cases were a dependent might be added prior to the latest effective date. For example if an employee were to open up a QE for Marriage add their spouse on 11/30/2017 then 2 days later open up a child birth QE and adds their newborn that was born on 11/2/2017, by system design, the newborn will not be auto enrolled into the EAP plan, Correct?

Hi Amannda Johnson,

Yes, you are right.

Cc: Satya,Amruta Lohiya,

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Hi Rashmita Dudhe,

To resolve this bug, we have made code changes in core routines of Enrollment. Please find below the impacted areas

• Core plan allocation
• Enroll Now
• Terminate employee election screens
• Pending Queue (accept/reject scenarios)
• Pending EOI (accept/reject scenarios)
• Effective/Termination date rule(s)
• Workflows of all Modes (i.e. OE, QE, New-Hire, Re-Hire)

All the above impacted areas need to test using following screens with retro, current and future date scenarios

• Enroll now
• Employee data (like - Demographics, Dependent Demographics)
• Terminate employee elections
• Import module
• SA utility

Please note : Performance must to be observed using Import and SA utility as there is change in Bulk Operation Routines.

Thanks and Regards,
:: Umesh Kadam

CC : Samir, Satya, Gaurav Sodani, Rakesh Roy, Amruta Lohiya, Jaideep Vinchurkar, Jyoti Mayne, Prasad Pise, Hrishikesh Deshpande

Hi Umesh Kadam,

CC:Hrishikesh Deshpande,Amruta Lohiya,Jaideep Vinchurkar,Jyoti Mayne,Gaurav Sodani,Prasad Pise,Samir

Verified this on Lb Environment.

1]Core plan allocation not working through UI — Current, retro, and future date
2]Core plan allocation not working through Import Also — Current, retro, and future date
tried on more than 4 companies.

For other scenarios testing in progress..

Thanks,
Rashmita

Hi Rashmita Dudhe,

Please find below 3C's :

Thanks and Regards
:: Umesh Kadam

CC : Gaurav Sodani, Amruta Lohiya, Hrishikesh Deshpande, Prasad Pise

Hi Umesh Kadam[~jaideep.vinchurkar]

CC:Hrishikesh Deshpande,Rakesh Roy,Gaurav Sodani,Jyoti Mayne

LB environment For OA MATT

#Scenario 1 Core plan allocation

1]Add Employee through UI – with Retro, Current and future date
2]Insert employee through Import – with Retro, Current and future date
3]Core plan allocation through SA utility more than 3000 employee
4]ineligible core plan by changing class through UI with retro, current and future date

5]Try to ineligible core plan through Import by changing class but it is not working: Failed.
through synchronous mod import getting failed. through asynchronous mode file imported successfully
But change in plan not happened

refer below error log:

ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->CopyFileFromServer.CopyFileFromServer
ErrorMessage: Could not find file '\\10.0.2.125\Temp\Encrypt_umesh_class_change12_20_2017 05_27_56 PM.txt'.

Continue testing for other scenarios.

Thanks,
Rashmita

Verified all attached scenarios on LB environment.
working fine as expected.

Hi All,

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

Regards
Gaurav

Verified all attached scenarios on Stage environment.
working fine as expected.

Hi Amannda Johnson,

This is deployed and verified in a Stage environment.
You can check now.

Thanks,
Rashmita

Rashmita Dudhe I have tested this on stage and the client has as well. All is working as expected YAY! Thank you! Let me know if there is anything else that is needed to help move this to production.

Hi Amannda Johnson

As part of the production deployment review of WT-12291 scheduled on 12/29/17, we found that a specific code block (employee enrollment HASH) was not deployed on production as it was part of WT-11746 and WT-11744, As we do not have approval for production deployment of WT-11746 and WT-11744 we were not able to deploy WT-12291 on production as the code would break and throw server error.
We would need to deploy WT-11746 and WT-11744 to production in order for this issue to be resolved

Regards
Gaurav

CC: Nagini IndugulaJennifer ReedSatyaUmesh KadamJyoti MayneAmruta Lohiya

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

As discussed with Gaurav Sodani and Jaideep Vinchurkar moved this ticket from WT to NF project

As discussed in Stand-up meeting, covert back this ticket from NF to WT.

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Verified all attached scenarios on the Production environment.
working fine as expected.

This is deployed and verified on Production.
Kindly, Update Jira accordingly.