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

Duplicate election was caused by Reduction Schedule Service

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Bug Type:
      Functional
    • Bug Severity:
      Critical
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Data Audit
    • Issue Importance:
      Must Have
    • Sprint:
      WT Sprint 35 - Bugs

      Description

      Duplicate election was caused by Reduction Schedule Service, on 01/24/2017 RSS reduce coverage and insert two enrollments with same effective date.

      Company Name:- BDG
      Employee:- Brenda Osorio
      Plan Name:- Basic Life and AD&D Hourly

      Company Name:- Mendocino Coast District Hospital
      Employee:- NICOLA BOYNOFF
      Plan Name:- Basic Life and AD&D Non-Exempt

      Employee:- Kyle Siler
      Plan Name:- Basic Life and AD&D Exempt Employee

      CC-- Amruta Lohiya,Satya,Vijay Siddha

        Attachments

        1. 1stScenario.png
          1stScenario.png
          66 kB
        2. 2ndScenario.png
          2ndScenario.png
          72 kB
        3. 3rdScenario.png
          3rdScenario.png
          83 kB

          Activity

          Hide
          snehal.shabade Snehal Shabade (Inactive) added a comment -

          Hi,
          We tried scenarios for following issue :

          Duplicate election was caused by Reduction Schedule Service
          Company Name:- BDG
          Employee:- Brenda Osorio
          Plan Name:- Basic Life and AD&D Hourly

          We did some analysis on production and observe that even though the enrollment table has duplicate elections ,the ReductionDetailsForReductionSchedule table has only one entry of coverage Reduction.

          For reproducing this issue we tried following scenarios:

          1. Enroll EE with Effective Date 2015/01/01 on 2017/08/22
            Update DOB of EE such that age of EE >65 on 2017/08/22 and Run the Reduction service
            Result : Election is enrolled properly with no duplication
          2. Enroll EE with Effective Date 2015/01/01 on 2017/08/22
            Update DOB of EE such that age of EE = 65 on 2017/08/22 and Run the Reduction service
            Result : Election is enrolled properly with no duplication
          3. Enroll EE with Effective Date 2015/01/01 on 2017/08/22
            Update DOB of EE such that age of EE is one day minus of 65 on 2017/08/22 and Run the Reduction service
            Result : Election is enrolled properly with no duplication

          Please find the attached screen shot for all scenarios :

          Cc: Jyoti Mayne Avnish Yadav Gaurav Sodani Hrishikesh Deshpande Prasad Pise

          Thanks,
          Snehal Shabade

          Show
          snehal.shabade Snehal Shabade (Inactive) added a comment - Hi, We tried scenarios for following issue : Duplicate election was caused by Reduction Schedule Service Company Name:- BDG Employee:- Brenda Osorio Plan Name:- Basic Life and AD&D Hourly We did some analysis on production and observe that even though the enrollment table has duplicate elections ,the ReductionDetailsForReductionSchedule table has only one entry of coverage Reduction. For reproducing this issue we tried following scenarios: Enroll EE with Effective Date 2015/01/01 on 2017/08/22 Update DOB of EE such that age of EE >65 on 2017/08/22 and Run the Reduction service Result : Election is enrolled properly with no duplication Enroll EE with Effective Date 2015/01/01 on 2017/08/22 Update DOB of EE such that age of EE = 65 on 2017/08/22 and Run the Reduction service Result : Election is enrolled properly with no duplication Enroll EE with Effective Date 2015/01/01 on 2017/08/22 Update DOB of EE such that age of EE is one day minus of 65 on 2017/08/22 and Run the Reduction service Result : Election is enrolled properly with no duplication Please find the attached screen shot for all scenarios : Cc: Jyoti Mayne Avnish Yadav Gaurav Sodani Hrishikesh Deshpande Prasad Pise Thanks, Snehal Shabade
          Hide
          snehal.shabade Snehal Shabade (Inactive) added a comment -

          Hi Avnish Yadav,

          Issue: Duplicate Coverage string
          Company Name:- Mendocino Coast District Hospital
          Employee:- NICOLA BOYNOFF
          Plan Name:- Basic Life and AD&D Non-Exempt

          We did some analysis on production and we found that the duplicate coverage string is present in enrollment on 2015-12-03 and this issue is not present after 2015-12-03 .
          This is due to data corruption.We need some data correction for this.

          We also tried this but it is not getting reproduced.

          Cc: Jyoti Mayne

          Thanks,
          Snehal Shabade

          Show
          snehal.shabade Snehal Shabade (Inactive) added a comment - Hi Avnish Yadav , Issue: Duplicate Coverage string Company Name:- Mendocino Coast District Hospital Employee:- NICOLA BOYNOFF Plan Name:- Basic Life and AD&D Non-Exempt We did some analysis on production and we found that the duplicate coverage string is present in enrollment on 2015-12-03 and this issue is not present after 2015-12-03 . This is due to data corruption.We need some data correction for this. We also tried this but it is not getting reproduced. Cc: Jyoti Mayne Thanks, Snehal Shabade
          Hide
          snehal.shabade Snehal Shabade (Inactive) added a comment -

          hi Prasad Pise,

          We tried above scenarios for reproducing issue "Duplicate election was caused by Reduction Schedule Service" but it is not getting reproduced.

          Could you please help to reproduce this issue?

          Cc: Jyoti Mayne

          Thanks,
          Snehal Shabade

          Show
          snehal.shabade Snehal Shabade (Inactive) added a comment - hi Prasad Pise , We tried above scenarios for reproducing issue "Duplicate election was caused by Reduction Schedule Service" but it is not getting reproduced. Could you please help to reproduce this issue? Cc: Jyoti Mayne Thanks, Snehal Shabade
          Hide
          prasadp Prasad Pise (Inactive) added a comment -

          Hi Rashmita Dudhe

          Could you please try to reproduce this issue and share your findings with dev team?

          Thanks
          -Prasad

          CC: Hrishikesh DeshpandeRakesh RoySachin Hingole

          Show
          prasadp Prasad Pise (Inactive) added a comment - Hi Rashmita Dudhe Could you please try to reproduce this issue and share your findings with dev team? Thanks -Prasad CC: Hrishikesh Deshpande Rakesh Roy Sachin Hingole
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Hi Avnish Yadav,

          CC:Satya,Hrishikesh Deshpande,Rakesh Roy,Gaurav Sodani,Jyoti Mayne

          Try to reproduced Above issue but it is not getting reproduced tried below scenarios:

          Company Name:- BDG
          Employee:- Brenda Osorio
          Plan Name:- Basic Life and AD&D Hourly

          1] As per Employee view history, Employee data inserted through Import and core plan allocated to employee.
          Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014
          Basic Life and AD&D Hourly: 1/1/2015 - Null

          after data imported cross verified on view history It showing two Entries
          Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014
          Basic Life and AD&D Hourly: 1/1/2015 - Null

          when reduction serviced run on Employee birth day
          It reduced Employee Coverage and insert New entry.

          2] Employee data inserted through Import and core plan allocated to employee.
          Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014
          Basic Life and AD&D Hourly: 1/1/2015 - Null

          verified for Age band change and reduction same time
          run reduction service and appyAgebandchange service
          It reduced Employee Coverage and New entry.

          3] Add employee through Ui core plan allocated to employee
          verified on view history It showing two Entries
          Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014
          Basic Life and AD&D Hourly: 1/1/2015 - Null

          verified for Age band change and reduction same time
          run reduction service and appyAgebandchange service
          It reduced Employee Coverage and New entry.

          4] Verified Plan View history and found Plan Basic Life and AD&D Hourly: 1/1/2015 - Null is cloned from Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014

          So created same scenario on Company Create New Life plan with date 01/01/2014 - 12/31/2014 and clone paln with 1/1/2015 - Null

          Employee data inserted through Import and core plan allocated to employee.

          after data imported cross verified on view history It showing two Entries
          verified for Age band change and reduction same time
          run reduction service and appyAgebandchange service
          It reduced Employee Coverage and New entry.

          5] Add employee through Ui core plan allocated to employee

          verified for Age band change and reduction same time
          run reduction service and appyAgebandchange service
          It reduced Employee Coverage and New entry.

          Thanks,
          Rashmita

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Avnish Yadav , CC: Satya , Hrishikesh Deshpande , Rakesh Roy , Gaurav Sodani , Jyoti Mayne Try to reproduced Above issue but it is not getting reproduced tried below scenarios: Company Name:- BDG Employee:- Brenda Osorio Plan Name:- Basic Life and AD&D Hourly 1] As per Employee view history, Employee data inserted through Import and core plan allocated to employee. Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014 Basic Life and AD&D Hourly: 1/1/2015 - Null after data imported cross verified on view history It showing two Entries Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014 Basic Life and AD&D Hourly: 1/1/2015 - Null when reduction serviced run on Employee birth day It reduced Employee Coverage and insert New entry. 2] Employee data inserted through Import and core plan allocated to employee. Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014 Basic Life and AD&D Hourly: 1/1/2015 - Null verified for Age band change and reduction same time run reduction service and appyAgebandchange service It reduced Employee Coverage and New entry. 3] Add employee through Ui core plan allocated to employee verified on view history It showing two Entries Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014 Basic Life and AD&D Hourly: 1/1/2015 - Null verified for Age band change and reduction same time run reduction service and appyAgebandchange service It reduced Employee Coverage and New entry. 4] Verified Plan View history and found Plan Basic Life and AD&D Hourly: 1/1/2015 - Null is cloned from Basic Life and AD&D Hourly :01/01/2014 - 12/31/2014 So created same scenario on Company Create New Life plan with date 01/01/2014 - 12/31/2014 and clone paln with 1/1/2015 - Null Employee data inserted through Import and core plan allocated to employee. after data imported cross verified on view history It showing two Entries verified for Age band change and reduction same time run reduction service and appyAgebandchange service It reduced Employee Coverage and New entry. 5] Add employee through Ui core plan allocated to employee verified for Age band change and reduction same time run reduction service and appyAgebandchange service It reduced Employee Coverage and New entry. Thanks, Rashmita
          Hide
          gaurav.sodani Gaurav Sodani (Inactive) added a comment -

          Hi Avnish,

          Could you please look into the issue

          Thanks
          Gaurav

          CC SatyaVijay SiddhaRashmita DudheJyoti Mayne

          Show
          gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi Avnish, Could you please look into the issue Thanks Gaurav CC Satya Vijay Siddha Rashmita Dudhe Jyoti Mayne
          Hide
          avnish.yadav Avnish Yadav (Inactive) added a comment -

          As this is not reproduce by QA and Dev. So we are marking as close.

          Show
          avnish.yadav Avnish Yadav (Inactive) added a comment - As this is not reproduce by QA and Dev. So we are marking as close.

            People

            Assignee:
            avnish.yadav Avnish Yadav (Inactive)
            Reporter:
            avnish.yadav Avnish Yadav (Inactive)
            Developer:
            Snehal Shabade (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Dev Due Date:

                Time Tracking

                Estimated:
                Original Estimate - 20h Original Estimate - 20h
                20h
                Remaining:
                Time Spent - 19h 25m Remaining Estimate - 2h
                2h
                Logged:
                Time Spent - 19h 25m Remaining Estimate - 2h
                19h 25m