Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-10853

Election Imports - Creates duplicate history records each time import loads

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
    • Environment:
      Production
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Import
    • Reported by:
      Support
    • Company:
      STSLLC
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 37 - Bugs, WT Sprint 38 - Bugs, WT Sprint 40 - Bugs, WT- Sprint 43

      Description

      When importing the same election file multiple times while nothing has change on the import file a new history record is being created for every load.

        Attachments

        1. 10853Testcases_updated.xls
          15 kB
        2. 10853Testcases.xls
          15 kB
        3. 6.png
          6.png
          12 kB
        4. image-2017-08-28-18-25-58-220.png
          image-2017-08-28-18-25-58-220.png
          30 kB
        5. ImportFail.jpg
          ImportFail.jpg
          173 kB
        6. ImportFail.txt
          0.4 kB
        7. import failed.png
          import failed.png
          118 kB
        8. WT-10853 Analysis document.doc
          42 kB

          Issue Links

            Activity

            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            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

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - 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
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            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

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - 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
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            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

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - 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
            Hide
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - - edited

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

            Show
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - - edited Trying to mark ticket as Done.  Can you please change the Resolution to Done.  I am unable to change this value.  Thanks!
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Hrishikesh Deshpande,

            Can you please look into above Cindy's request.

            Thanks,
            Sanjana Jadhav

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Hrishikesh Deshpande , Can you please look into above Cindy's request. Thanks, Sanjana Jadhav

              People

              Assignee:
              sanjana.jadhav Sanjana Jadhav (Inactive)
              Reporter:
              Cindy.Wibbing Cindy Wibbing (Inactive)
              Developer:
              Suraj Sokasane (Inactive)
              QA:
              Sanjana Jadhav (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Dev Due Date:
                Pre-Prod Due Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 73h Original Estimate - 73h
                  73h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 185.75h
                  185.75h