Please find below the screen shot of the error they are receiving.

Hello Swapnil

Please take this ahead

Hi Niteen Surwase ,

Please check this today.

Thanks,
Swapnil P.

Hello Rohan J Khandave,

I did analysis on this issue and observed that this issue is related to Enrollment, so assigning this ticket to you. Please find the attached error log and observations regarding issue -

1. This issue is for specific employee(s) only.
2. Issue is getting reproduce during New Hire Workflow for both CA and Employee logins.

Please find below Employee Details, for which issue getting reproduce at HSPL copy -

10001596
Password@1
UVU For HSPL

CC: Sheetal Bodhale, Swapnil Pandhare, Jyoti Mayne, Umesh Kadam, Satya

Thanks & Regards
Amit K.

Hello,
What should we do on our end? Please advise.

Than you,
Yashau

Hello,
Has this be resolved? Please advise.

Hello Yashau MacShate,

We are analyzing this issue. Right now there is no alternative to fix this.

We need code changes to resolved this & details analysis is still in progress.

Thanks,
RohanK

Thank you so much! I will let the C.E. know.

Yashau

Below is issue details.

Concern : Server error on form saving.

Cause : When we save form core plans are getting allocated. While allocating core plans one of variable has null value. Which is causing issue.

Correction: We have handle this scenario.

Affected Files :
APP SERVER [ EligibilityEngine.dll --> EnrollmentBulkInsert.vb]

We did get development approval for this to begin working on it, so we'll add it to this sprint.
Satya If you can keep me updated on expected deployment dates - not sure if we will be able to get it into our scheduled deployments or if we will need to do a hot fix.

Hi Jennifer Reed,

This ticket has development due date of 12th Feb 2018. After QA testing of this ticket, we will move to stage & production environment during next week.

Rakesh Roy Please will confirm on stage & production deployment dates.

Regards,
Satya Prakash

Cc: Rohan J Khandave Yashau MacShate

Jennifer Reed Satya

Stage deployment date would be Feb 15th and Production deployment would be Feb 19th along with other QA points.

Please check after LB deployment.

Environment: LB
Company: For QA JE dunn for hspl
Login: Partner and Employee

Customization done. Testing in progress.

Hrishikesh Deshpande Rohan J Khandave

Hello,
Per the C.E., Deborah Larue:
Hi, This is still happening . My client called and sent this email .
I just received a call from one of our 2/1 benefit eligible employees and she is stuck on the smoker status question in OnlinEnroll. It is the same error as before telling her to contact the administrator. The employees name is Caridad Bargamento (10836214). Denise also just mentioned to me that Patricia Perkes (10526688) completed her enrollment but then went back and made changes and had the same issue with the smoker status.

This ticket was for:
The admins have to enroll the new hires because when the EE goes through the flow to enroll they get stuck at the smoking question and the site it gives an error... server encountered an internal error. Please contact your administrator.
Can you please advise if this is being worked on?

Yashau MacShate Sorry I thought this was more clear, but yes we are currently working on it and it is in QA testing. This will require a hot fix deployment to stage for testing and then to production. We will let you know when those dates have been finalized.

Environment: LB
Company: Je dunn for hspl
Login: Partner and Employee

Scenario:
Partner Login > New Hire Employee > Auto-Enrolled on Core plan P1 [New Hire Effective Date 01/01/2018]
Plan term Date 06/30/2018 > Employee get auto enrolled in Plan P2 with Effective date [07/01/2018]

Employee login > New Hire Work flow > Additional Form changed and Saved > No error occured.

Also, run other test cases like core plan allocation with services, Employee not eligible to plan and later after class change.

As able to complete Employee flow without any error moving this jira on Sage.

Rohan J Khandave Hrishikesh Deshpande

This will be deployed to stage tomorrow, and will be moved to production once completing stage testing. We will update this ticket with the prod deployment date when finalized.

Hello,
Per Yami:
Can we also get confirmation that the fix that is being worked on will prevent it from happening again. This is a high profile client and they will not hesitated to escalate their concerns. Appreciate your help. Thank you.

CC:Yamilka Coca
Jennifer Johnson

Hi Yashau,

Development has been completed for this & fix is getting deployed on Stage today(2/15).

QA team will update its testing status by EOD.

This has been planned for production deployment on Monday(2/19).

Regards,
Satya Prakash

Cc: Rakesh Roy Rohan J Khandave Jennifer Reed Yamilka Coca Jennifer Johnson

Environment: stage
Company: Utah Valley University For HSPL
Login: Partner and Employee

Verified following scenarios:
1.Two employees one through UI and another through Add Employee

• Both should have enrolled in auto enrolled plan
  2.Two employees one through UI and another through Add Employee
• Both should have enrolled in auto enrolled plan with same coverage
  3.New Hire Employee getting auto enrolled in core plan
  4.New Hire Employee confirmation Statement Effective date and Term date updated as expected
  5.Employee login > Edit and Save Additional Form
  6.Employee login > Complete work flow
  8.Employee login Continue through Auto enrolled plan page
  Working properly.
  Testing In progress.

Thanks,
Sanjana Jadhav

CC: Priya Dhamande Prasad Pise Rakesh Roy Satya

Environment: stage
Company: Utah Valley University For HSPL
Login: Partner and Employee

Scenario:
Partner Login > New Hire Employee > Auto-Enrolled on Core plan P1 [New Hire Effective Date 01/01/2018]
Plan term Date 06/30/2018 > Employee get auto enrolled in Plan P2 with Effective date [07/01/2018]
Employee login > New Hire Work flow > Additional Form changed and Saved > No error occured.
Also, run other test cases like core plan allocation with services, Employee not eligible to plan and later after class change.
As able to complete Employee flow without any error moving this jira on production.

Thanks,
Sanjana Jadhav

CC: Priya Dhamande Prasad Pise Hrishikesh Deshpande Rakesh Roy

Verified on production.
Company: UVU for hspl
Login: Partner and Employee

Scenario:
Partner Login > New Hire Employee > Auto-Enrolled on Core plan P1 [New Hire Effective Date 01/01/2018]
Plan term Date 06/30/2018 > Employee get auto enrolled in Plan P2 with Effective date [07/01/2018]
Employee login > New Hire Work flow > Additional Form changed and Saved > No error occurred.
Verified all attached test cases.Working properly.
PFA,
TestCaseWT_13207_prod.xls

Thanks,
Sanjana Jadhav

CC: Prasad Pise Priya Dhamande Hrishikesh Deshpande Rakesh Roy