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

Qualifying event is not getting saved after termination of forced contingent plan election.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Item State:
      Production QA - Production Deployed
    • Issue Importance:
      Must Have

      Description

      Customization: HRA is force contingent on Medical plan.
      1. Employee is enrolled in Medical plan with effective date 01/01/2016 and due to forced contingency, EE got election and rate in HRA plan with 01/01/2016. Termination date for both election is NULL.

      2. QE is raised with Effective date 07/01/2016.

      3. Employee is enrolled in Medical plan with effective date 07/01/2016 and different health tier.

      4. Admin approve's enrollment from Pending queue.

      5. Ideally, Medical and HRA enrollments should terminate with termination date 06/30/2016 and with proper Qualifying event. As well as EE should get enrolled in Medical and HRA plan with effective date '07/01/2016'.

      And we are getting correct qualifying event for enrollment effective from '07/01/2016', but for terminated enrollments NULL value is inserted in DB for Qualifying event ID.

        Attachments

          Issue Links

            Activity

            Hide
            abhijeet.khandagale Abhijeet Khandagale (Inactive) added a comment -

            Please find 3C's of mentioned issue below,

            Concern: Qualifying event is not getting saved after termination of forced contingent plan election.

            Cause: In business logic, as per current logic, we are not getting Qualifying event ID passed in a function where enrollment
            is terminated. And in this function default value of Qualifying Event id is 0. Because of which, QE is not getting saved.

            Correction: We have made code changes in Business logic so that we can get correct Qualifing ID passed to a function where enrollment
            is terminated. We are testing this changed functionality on local environment.
            We will move this on LB after testing.

            Show
            abhijeet.khandagale Abhijeet Khandagale (Inactive) added a comment - Please find 3C's of mentioned issue below, Concern: Qualifying event is not getting saved after termination of forced contingent plan election. Cause: In business logic, as per current logic, we are not getting Qualifying event ID passed in a function where enrollment is terminated. And in this function default value of Qualifying Event id is 0. Because of which, QE is not getting saved. Correction: We have made code changes in Business logic so that we can get correct Qualifing ID passed to a function where enrollment is terminated. We are testing this changed functionality on local environment. We will move this on LB after testing.
            Hide
            vijays Vijay Siddha (Inactive) added a comment - - edited

            related ticket to WT-1763 "Must Have" so making issue importance as "Must Have"

            Show
            vijays Vijay Siddha (Inactive) added a comment - - edited related ticket to WT-1763 "Must Have" so making issue importance as "Must Have"
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment -

            Marking this as ready for stage as there are errors on script execution on UND for Banner Payroll testing on LB so this patch will be tested directly on Stage.

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - Marking this as ready for stage as there are errors on script execution on UND for Banner Payroll testing on LB so this patch will be tested directly on Stage.
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment -

            We got this company on stage at 5:50 PM today. We will continue our testing on Monday

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - We got this company on stage at 5:50 PM today. We will continue our testing on Monday
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment -

            Verified the fix on stage on UND banner payroll Test company . Proper QE codes for all plans (including for force contingent plans ) along with Qualifying event dates are getting exported on the file for Termination as well as for active records.
            Working as expected on Stage

            Ready for Production

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - Verified the fix on stage on UND banner payroll Test company . Proper QE codes for all plans (including for force contingent plans ) along with Qualifying event dates are getting exported on the file for Termination as well as for active records. Working as expected on Stage Ready for Production
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - - edited

            Hi Abhijeet Khandagale

            Verified the fix on Production on UND For Banner Payroll Testing for HSPL company on Production for QE-married scenario. which is working as expected.

            Observed one issue as below for another record exported on file other than my scenario.

            Issue on file : When Group file is exported found one record for HRB (2016 Health Reimbursement Account) for an Employee which have BLANK QE Code and QE Date on the file.

            Description:
            Employee has changed Child's status from 'Active' to 'Deceased' on 06/16/2016 due to this High Deductible Heath Plan CHA got terminated on 6/30/2016 and Continued from 07/01/2016 with another child.
            now the above mentioned Heath Plan CHA is force contingent on '2016 Health Reimbursement Account - Family - Prior to 7/1' .
            Can you please check why the QE date did not appear on the file.? Please find attached screenshot for your reference.
            (Note: QE Code for Employee Data Change is Configured as Blank on template so it will export as blank. But QE date should be exported on the file )

            Below are the employee Details
            Employee Name : Carolyn M Stohler
            Company Name: UND for Banner Payroll Testing

            Please let us know if any code change is required for this so that I'll create another JIRA for the same

            CC: Rohan J Khandave Ganesh Sadawarte Hrishikesh Deshpande Vinayak Kulkarni Jyoti Mayne

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - - edited Hi Abhijeet Khandagale Verified the fix on Production on UND For Banner Payroll Testing for HSPL company on Production for QE-married scenario. which is working as expected. Observed one issue as below for another record exported on file other than my scenario. Issue on file : When Group file is exported found one record for HRB (2016 Health Reimbursement Account) for an Employee which have BLANK QE Code and QE Date on the file. Description: Employee has changed Child's status from 'Active' to 'Deceased' on 06/16/2016 due to this High Deductible Heath Plan CHA got terminated on 6/30/2016 and Continued from 07/01/2016 with another child. now the above mentioned Heath Plan CHA is force contingent on '2016 Health Reimbursement Account - Family - Prior to 7/1' . Can you please check why the QE date did not appear on the file.? Please find attached screenshot for your reference. (Note: QE Code for Employee Data Change is Configured as Blank on template so it will export as blank. But QE date should be exported on the file ) Below are the employee Details Employee Name : Carolyn M Stohler Company Name: UND for Banner Payroll Testing Please let us know if any code change is required for this so that I'll create another JIRA for the same CC: Rohan J Khandave Ganesh Sadawarte Hrishikesh Deshpande Vinayak Kulkarni Jyoti Mayne
            Hide
            abhijeet.khandagale Abhijeet Khandagale (Inactive) added a comment -

            Hi Rohan J Khandave,

            Could you please check whether is breaking because of my code changes? I don't have much knowledge of Export functionality.

            CC: Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte Aniruddha Dev

            Show
            abhijeet.khandagale Abhijeet Khandagale (Inactive) added a comment - Hi Rohan J Khandave , Could you please check whether is breaking because of my code changes? I don't have much knowledge of Export functionality. CC: Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte Aniruddha Dev
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Hello Aniruddha Dev,

            We checked from back end enrollment of plan "2016 Health Reimbursement Account - Family - Prior to 7/1" added on 03/18 by "Admin Change" qualifying event.

            But in "RaisedQualifyingEvent" table only one entry exists for this employee on date "06/17/2016" of qualifying event "Death" and no entry for "Admin Change". Due to this in-consistent data blank QE date exported on file.

            CC – Abhijeet Khandagale Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Hello Aniruddha Dev , We checked from back end enrollment of plan "2016 Health Reimbursement Account - Family - Prior to 7/1" added on 03/18 by "Admin Change" qualifying event. But in "RaisedQualifyingEvent" table only one entry exists for this employee on date "06/17/2016" of qualifying event "Death" and no entry for "Admin Change". Due to this in-consistent data blank QE date exported on file. CC – Abhijeet Khandagale Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment -

            Closing this JIRA as above mentioned scenario is not an issue and it is due to Inconsistent Data . The fix is working as expected

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - Closing this JIRA as above mentioned scenario is not an issue and it is due to Inconsistent Data . The fix is working as expected

              People

              Assignee:
              aniruddha.dev Aniruddha Dev (Inactive)
              Reporter:
              abhijeet.khandagale Abhijeet Khandagale (Inactive)
              Developer:
              Abhijeet Khandagale (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Pre-Prod Due Date:
                Production Due Date: