This the case on Stage and Production. The attached screenshot was from STSLLC. We have checked multiple companies and see the same issue exists.

Hi Cindy Wibbing,

We are aware of this issue and have considered to be fix under WT-9056
We will try to schedule this in next sprint. which will starting from 09/11/2017

Hi Jaideep Vinchurkar
The explanation for the WT-9056 ticket is different from the issue on this ticket. Is the fix on WT-9056 going to eliminate the duplicate history entries per election import when the enrollment on the file load has not changed?
Thanks!
Cindy

cc Amit ThorveAbhay Patil

Jaideep Vinchurkar - this is regression. Earlier, when import file had a record that was IDENTICAL to one existing in the system, it used to leave that record alone. This behavior was consistent with UI. I.e. if one attempts to add an election via UI where the identical election exists in the system, it doesn't overwrite it.

You have mentioned WT-9056, where a different problem is being addressed. May be there is some common code fix between them. However, these are two different issues from the user perspective.

Jaideep Vinchurkar This issue is affecting all imports then why we are waiting to fix it till next spring? This is a bug and not an enhancement and we should not wait for sprint to commence for bug fixing.

CC-Abhay Patil, Cindy Wibbing

Modifying scope of this ticket. We are expecting below things as a fix of this issue,

1. Enrollment should get updated only if termination date is different
2. For any other change, current enrollment should get terminated and new enrollment should get added
3. If there is no change in enrollment, do not execute any sql query. i.e. do not create any history for such enrollment.
4. If there are 4 members given in file, but one of them is ineligible for the plan or a bad record, current gets kicked out. Now all 4 members should get kicked out.

Estimates and analysis document is attached

Jaideep Vinchurkar When the work is going to start on the same?

Suraj has started working this already. Please go through attached analysis document and estimates,

Van Nguyen, Cindy Wibbing, Nathaniel Cornejo-Walker, Chris Ellenberger, Damion M Velasquez

This is the ticket which tracks the import change which is currently being worked on for history record creation.

Also the issue related to bad records in enrollment (when one member goes to bad send entire family to bad record) is also getting worked on at the same time.

Suraj Sokasane correct me if I am wrong with above sentence or if there is any other JIRA ticket then point us towards the same.

Hi Amit Thorve, yes both the issues are being looked into under this ticket.

Hi Suraj Sokasane,

Could you please share 3C's

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise Jaideep Vinchurkar

Hi Jayshree Nagpure,

Please go through the document. There are multiple scenario's handled in this system and all are mentioned in document.

Hi Suraj Sokasane,

Verified on LB.
Company - For QA FDU.

Verified below scenario :
1)Effective date update-new record created, old election terminate with prior one day
2)Imported election data with no data change - No duplicate election record is created,Only one election is exists in system
3)Termination date is changed- Election is updated
4)For tier enrollment, Imported Emp+Sp+Child - Import done successfully
5)For tier enrollment, Imported Emp+Sp+Child And when duplicate election is imported - import done successfully, no change in history data
6)For Tier enrollment, when Emp+Sp+Child is enrolled, but Sp+Ch wents to bad(Does not satisfy eligibility or any other),Out of 3 records from file, Import status shows 1 Import done successfully(Employee record)
Two records from File wents to bad(Sp+Child)
In view history, employee election is not added.
In view bad file, if we correct the data of spouse ad child and re-import, then as per imported data only spouse and child data is shown in view history.
No employee records are shown.
7)Bad file record - When there is bad file, for 1 st bad record system shows proper Error message.
And for second one, its shows "Member send to bad(Needs error message)
8)When Employee is enrolled in life plan, we have to pass approved coverage amount - Import done successfully
9)When we import duplicate record of same employee in Life plan(With EE+SP+CH same, plan design same, coverage amount same)- Import gets fail :
Please refer attached error log: ImportFail.txt

As 6,7,9 scenario is not working properly.

Hence, re-opening this jira.

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise Jaideep Vinchurkar

Satya Can we get the 3C's on this one? I get the gist of the issue, but want to make sure I understand the root cause.

Concern: Election import creating duplicate records in history

Cause: A few months back we have a issue in election import, where import is allowing dependents to enroll separately though it not supposed to. To fix this issue, we have changed code to terminate enrollment each time we import and add new enrollment. This is how it works on UI. However, on UI enrollment get terminate only if there is change in enrollment. In import we do not have any such check. So for each import, import terminates current enrollment and adds new one.

Correction: We have changed code. Now we first check if their is any change in enrollment, then only we terminate current enrollment and inserts new. If no change found, we do not touch the enrollment.

Thanks Jaideep Vinchurkar so was this already changed? Meaning it will not happen moving forward? Or are we waiting to deploy the code change?

This fix is deployed on LB. Our QA found an issue in it and we working to fix it.

okay, thanks Jaideep Vinchurkar!

3c's for issues which re-opened the ticket:

Concern: Point no. 6, 7, 9 from Jayshree's comment.

Cause :
6: : First record of an Enrollment was not considered for bad record count, though it was added in bad file.
7: : The error message text was not fixed.
8: : Exist check was missing for duplicate enrollment.

Correction:
6: : First record of an enrollment was also maintained with it's row number and added to bad file count.
7: : An approved error message text was added.
8: : Added if exist check in code.

Hi Suraj Sokasane

Verified on LB.
Company: For QA FDU For HSPL

Sceanrios tested:
1.Added election template
2.Import election template for employee
3.Verified changes on view history page-Record created on view history page
4.Import same file without any changes-New record not created on view history page
5.Verified election import with different effective date
6.Update termination date for election import- Election record updated and shown on view history page
7.Update election effective date-New record created, and old election terminates prior of one day
8.For tier enrollment, Imported Emp+Sp+Child - Import done successfully
9.For tier enrollment, Imported Emp+Sp+Child And when duplicate election is imported - import done successfully, no change in history data
10.For Tier enrollment, when Emp+Sp+Child is enrolled,if any member go to bad,all other members of that employee enrolling into same plan will also be sent to bad and record not created on view history page and shown in view bad file
11.Proper error message shown for bad file records
PFA

12.Verified different effective date for differemt employee member-Proper error message shown
13.When Employee is enrolled in life plan, we have to pass approved coverage amount - Import done successfully
14.When we import duplicate record of same employee in Life plan(With EE+SP+CH same, plan design same, coverage amount same)- Import gets fail
PFA
ImportFail.txt

Attached updated test cases:
10853Testcases_updated.xls

Scenario 14 not working properly.
Hence, re-opening this jira.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Rakesh Roy Jayshree Nagpure

The actual error log was:

There was a missing '~' sign between approved and applied coverage, creating 1000.00001000.0000 as Approved coverage. Converting this to double, exception was thrown.

The code is corrected and will be deployed on LB in next patch.

Hi Sanjana Jadhav,

Please check this.

Thanks,
Ganesh

Hi Suraj Sokasane

Verified on LB.
Company: For QA FDU For HSPL

Following Scenarios tested:

1.Bad file record-When total fields in file does not match with template for spouse and child-Employee imported and spouse and child goes to bad -Fail(Works properly only for plan eligibility)
2.Enrollment added by import not reflected on Enroll now page,Confirmation statement and view enrollment summary page only shown on view history page.-Fail
3.When Employee is enrolled in life plan, we have to pass approved coverage amount - Import done successfully-Pass
4.When we import duplicate record of same employee in Life plan(With EE+SP+CH same, plan design same, coverage amount same)-Imported successfully-No duplicate election record is created
5.Verified validation message when coverage amount is not in range of flat amount -Pass

As scenarios 1 and 2 not working properly.
Hence, re-opening this jira.

Thanks,
Sanjana Jadhav

CC: Hrishikesh Deshpande Prasad Pise Rakesh Roy Jayshree Nagpure

Hi Sanjana Jadhav,

For issue no 1:
System identifies an enrollment on basis of three things:

• Employee SSN / EmpID
• Plan Name
• Effective Date
  Rows in file having same values for above 3 fields will be treated as part of single Enrollment. If we are enrolling Employee, Spouse, Child into an Enrollment, all three rows will have same values for SSN, Plan and Effective date.
  If any of three is different, we treat it as different enrollment.

In your case, due to extra field in file all fields were shifted by one place. Making 'a' as plan name. So if the file is enrolling Employee and Spouse into basic and Child into plan named 'a', those will be treated as different enrollments. So, Child will be kicked out and Employee and Spouse will be enrolled successfully.

Issue no 2
As discussed please check with future qualifying event.

Hi Suraj Sokasane

Verified issue no 2 with future qualifying event. Verified on Enroll now, Confirmation statement and view enrollment summary page.Working as expected.
Verified all test cases.Working properly.
Ready for stage.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Hrishikesh Deshpande Rakesh Roy Jayshree Nagpure Ganesh Sadawarte

Verified on Stage.
Company: City of Denton For HSPL

Scenarios tested:
1.Added election template
2.Import election template for employee
3.Verified changes on view history page-Record created on view history page
4.Import same file without any changes-New record not created on view history page
5.Verified election import with different effective date
6.Update termination date for election import- Election record updated and shown on view history page
7.Update election effective date-New record created, and old election terminates prior of one day
8.For tier enrollment, Imported Emp+Sp+Child - Import done successfully
9.For tier enrollment, Imported Emp+Sp+Child And when duplicate election is imported - import done successfully, no change in history data
10.For Tier enrollment, when Emp+Sp+Child is enrolled,if any member go to bad,all other members of that employee enrolling into same plan will also be sent to bad and record not created on view history page and shown in view bad file
11.Proper error message shown for bad file records
12.When Employee is enrolled in life plan, we have to pass approved coverage amount - Import done successfully
13.When we import duplicate record of same employee in Life plan(With EE+SP+CH same, plan design same, coverage amount same)-Imported successfully-No duplicate election record is created

Working properly.
Ready for production.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Hrishikesh Deshpande Rakesh Roy

Hi Cindy Wibbing

Verified on Production.
Company: Austin For HSPL

Scenarios tested:
1.Added election template
2.Import election template for employee
3.Verified changes on view history page-Record created on view history page
4.Import same file without any changes-New record not created on view history page
5.Verified election import with different effective date
6.Update termination date for election import- Election record updated and shown on view history page
7.Update election effective date-New record created, and old election terminates prior of one day
8.For tier enrollment, Imported Emp+Sp+Child - Import done successfully
9.For tier enrollment, Imported Emp+Sp+Child And when duplicate election is imported - import done successfully, no change in history data
10.For Tier enrollment, when Emp+Sp+Child is enrolled,if any member go to bad,all other members of that employee enrolling into same plan will also be sent to bad and record not created on view history page and shown in view bad file
11.Proper error message shown for bad file records
12.When Employee is enrolled in life plan, we have to pass approved coverage amount - Import done successfully
13.When we import duplicate record of same employee in Life plan(With EE+SP+CH same, plan design same, coverage amount same)-Imported successfully-No duplicate election record is created

Working properly.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Hrishikesh Deshpande Rakesh Roy Jayshree Nagpure

Trying to mark ticket as Done.  Can you please change the Resolution to Done.  I am unable to change this value.  Thanks!

Hi Hrishikesh Deshpande,

Can you please look into above Cindy's request.

Thanks,
Sanjana Jadhav