Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-5864

Election Imports - Creates duplicate history records each time import loads

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Bug Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
    • Environment:
      Production
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Import
    • Reported by:
      Client
    • Company:
      All Clients/Multiple Clients
    • Item State:
      LB QA - Ready for Stage

      Description

      Updated development status.

        Attachments

          Issue Links

            Activity

            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

            Hi Abhilash Warkari,

            Please check this.

            Thanks,
            Ganesh

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - Hi Abhilash Warkari , Please check this. Thanks, Ganesh
            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

            Hi Sanjana Jadhav,

            Please check this is deployed on UiRefresh LB.

            Thanks,
            Ganesh

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - Hi Sanjana Jadhav , Please check this is deployed on UiRefresh LB. Thanks, Ganesh
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Verified on Codemap.
            Company: For QA-El Camino Hospital-Azure

            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 pre production.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Verified on Codemap. Company: For QA-El Camino Hospital-Azure 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 pre production. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            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
            Working as expected.
            Testing In-progress.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - 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 Working as expected. Testing In-progress. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Completed testing on production.
            Verified all scenarios mentioned.Working as expected.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Completed testing on production. Verified all scenarios mentioned.Working as expected. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy

              People

              Assignee:
              sanjana.jadhav Sanjana Jadhav (Inactive)
              Reporter:
              Ganesh.sadawarte Ganesh Sadawarte (Inactive)
              Developer:
              Abhilash Warkari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 7h Original Estimate - 7h
                  7h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10.5h
                  10.5h