CC: Swapnil Pandhare

Hi Swapnil Pandhare,

Below are our findings on this issue.

1. After adding a new EE, the EE is not getting the Auto Enrolled Plans.

(Please refer the screen shot below)

2. When we made a change in Demographic page, the EE got the Auto Enrolled Plans.

(Please refer the screen shot below)

3. Also when we added the EE, the pop up doesn't show the username.

(Please refer the screen shot Below)

4. After EE login, the EE gets server Error instead of SS mode. However, the EE gets the New hire mode on Enroll now screen.

(Please refer the screen shots below)

Request you to please look into this issue.
Thank you,
------------------------------------------------------------------------------
CC: Mandar Kulkarni, Vijay Siddha, Jaideep Vinchurkar, Sumeet.Kolge

CC : Amruta Lohiya Satya

Hi Umesh Kadam,

Please check this issue as discussed.

Thanks,
Swapnil P.

Hi Monika Demla,

We are working on this .we will update you once analysis is done.

Cc: Umesh Kadam
Thanks,
Snehal Shabade

Hi Monika Demla,

As per our initial analysis, we have found that, there are two core plans present in "Charleys" company which are effective from 11/01/2017 and employee getting added before 11/01/2017 are not getting core plans on adding into system. But after making Demographics change, core plans are getting allocated as Effective date is getting set after 11/01/2017 as per New Hire rule.

We are working on finding other caused and will share more details on this.

Thanks and Regards,
:: Umesh Kadam

CC : Amruta Lohiya, Swapnil Pandhare, Snehal Shabade

Hi Monika Demla,

We found that,
If Effective Date of Core Plan is greater than Hire Date ,the system is not allocating the core plan. We are working on this issue. And will update you once we done .

Thanks and Regards,
Snehal Shabade

CC: Amruta Lohiya ,Umesh Kadam

Hi Snehal Shabade
I ran the Enrollment report for basic life and it did not capture EE cost and ER cost. Please see screen shot below and adivse if recalculation is required.
Thanks!
Monika.

This is not related to Auto Enrolling Issue here.

Thanks!
Please provide me update on Auto Enroll issue. Client is going live on 10/3

Hi Monika Demla,

Code has been fixed for Auto Enroll Issue, also deployed on LB and same is under QA testing. We will deploy it STAGE and Production after QA testing.

Thanks and Regards,
:: Umesh Kadam

CC : Satya, Amruta Lohiya, Snehal Shabade, Hrishikesh Deshpande, Prasad Pise, Rashmita Dudhe

Verified on LB Environment consider scenarios for core plan:

1] Core plan A with effective date 11/01/2017
2]Core plan B effective date 01/01/2018
3]Core plan C with effective date 07/15/2018
4]Core plan D with effective date 01/01/2017

Scenario #1
Add an employee with effective date 01/01/2017

Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date

Scenario #2
Add an employee with effective date 09/01/2017

Actual result: Employee enrolled in all core plan B, C with plan effective date

Scenario #3
Add an employee with effective date 01/01/2018

Actual result: Employee enrolled in all core plan A, B, C with plan effective date

Scenario #4
import 10 records with different Date of employment.
cross verified on confirmation statement employee enrolled in core plan with plan effective date

Scenario #5
Verified through core plan allocation service
cross verified on confirmation statement employee enrolled in core plan with plan effective date

Scenario #6
Verified through SA utility
cross verified on confirmation statement employee enrolled in core plan with plan effective date

Scenario #7
Verified by adding termination date.
cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.

working fine as expected

Verified on Stage Environment consider scenarios for core plan:
1] Core plan A with effective date 11/01/2017
2]Core plan B effective date 01/01/2018
3]Core plan C with effective date 07/15/2018
4]Core plan D with effective date 01/01/2017
Scenario #1
Add an employee with effective date 01/01/2017
Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date
Scenario #2
Add an employee with effective date 09/01/2017
Actual result: Employee enrolled in all core plan B, C with plan effective date
Scenario #3
Add an employee with effective date 01/01/2018
Actual result: Employee enrolled in all core plan A, B, C with plan effective date
Scenario #4
import 10 records with different Date of employment.
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #5
Verified through core plan allocation service
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #6
Verified through SA utility
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #7
Verified by adding termination date.
cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.
working fine as expected

Great! Thanks for updated.

Verified on Production Environment consider scenarios for core plan:
1] Core plan A with effective date 11/01/2017
2]Core plan B effective date 01/01/2018
3]Core plan C with effective date 07/15/2018
4]Core plan D with effective date 01/01/2017
Scenario #1
Add an employee with effective date 01/01/2017
Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date
Scenario #2
Add an employee with effective date 09/01/2017
Actual result: Employee enrolled in all core plan B, C with plan effective date
Scenario #3
Add an employee with effective date 01/01/2018
Actual result: Employee enrolled in all core plan A, B, C with plan effective date
Scenario #4
import 10 records with different Date of employment.
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #5
Verified through core plan allocation service
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #6
Verified through SA utility
cross verified on confirmation statement employee enrolled in core plan with plan effective date
Scenario #7
Verified by adding termination date.
cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.
working fine as expected

Hi Monika Demla,

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

Thanks,
Rashmita