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

Application did not terminate EE benefit effective with end of the current pay period.

    Details

    • Type: Bug
    • Status: Rejected
    • Priority: High
    • Resolution: System Behaviour
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
      None
    • Environment:
      Others
    • Bug Type:
      Functional
    • Bug Severity:
      Critical
    • Level:
      Employee
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Company:
      City of Bellevue

      Description

      URL --> https://10.0.2.71/BenAdmin
      Company --For QA-City of Bellevue-Azure
      SSN- 300000720

      Medical --> Group Health Cooperative HMO Plan

      General Plan design - Termination Policy – Current pay period end date

      Step:-
      1.ADD new employee with employment date -01/01/2017
      2.Start OE
      3.Navigate to Enroll Now
      4.Auto Enroll into - Group Health Cooperative HMO Plan
      5.Log out
      6.Login with Partner
      7.Navigate to EE dashboard
      8.Change EE status to Terminated with retro date (10/15/2017)

      Actual - Plan did not get terminated

      Expected - It should get terminated with Current pay period end date

        Attachments

          Issue Links

            Activity

            Hide
            umesh.kadam Umesh Kadam (Inactive) added a comment -

            Hi Mahendra,

            As discussed, please find below our analysis :

            • Employee status was changed on '2017-11-29 12:41:24.967'.
            • On '2017-11-29 12:41:24.967' generic eligibility rule set on 'Group Health Cooperative HMO Plan' plan was 'All Status Rule'
            • According to current rule set on plan at the time of termination employee was eligible for given plan hence system didn't terminate his election in 'Group Health Cooperative HMO Plan' with current period end date.
            • On '2017-11-29 12:48:04.850', it means on same day, generic eligibility rule for 'Group Health Cooperative HMO Plan' plan was changed to 'Mahendra_Rule'.
            • As per 'Mahendra_Rule', employee is not eligible in 'Group Health Cooperative HMO Plan' plan.
            • Therefore if you repeat the same scenario, system will terminate EE's enrollment in 'Group Health Cooperative HMO Plan' plan with 'Current Period End Date'

            I have checked with same steps, system is terminating elections as per termination policy set on general plan design. Please check and confirm.

            Thanks and Regards,
            :: Umesh Kadam

            CC : Satya, Nidhi Kaul, Gaurav Sodani, Amruta Lohiya, Jyoti Mayne, Hrishikesh Deshpande, Sachin Hingole

            Show
            umesh.kadam Umesh Kadam (Inactive) added a comment - Hi Mahendra, As discussed, please find below our analysis : Employee status was changed on '2017-11-29 12:41:24.967'. On '2017-11-29 12:41:24.967' generic eligibility rule set on 'Group Health Cooperative HMO Plan' plan was 'All Status Rule' According to current rule set on plan at the time of termination employee was eligible for given plan hence system didn't terminate his election in 'Group Health Cooperative HMO Plan' with current period end date. On '2017-11-29 12:48:04.850', it means on same day, generic eligibility rule for 'Group Health Cooperative HMO Plan' plan was changed to 'Mahendra_Rule'. As per 'Mahendra_Rule', employee is not eligible in 'Group Health Cooperative HMO Plan' plan. Therefore if you repeat the same scenario, system will terminate EE's enrollment in 'Group Health Cooperative HMO Plan' plan with 'Current Period End Date' I have checked with same steps, system is terminating elections as per termination policy set on general plan design. Please check and confirm. Thanks and Regards, :: Umesh Kadam CC : Satya , Nidhi Kaul , Gaurav Sodani , Amruta Lohiya , Jyoti Mayne , Hrishikesh Deshpande , Sachin Hingole

              People

              Assignee:
              mahendra.mungase Mahendra Mungase (Inactive)
              Reporter:
              mahendra.mungase Mahendra Mungase (Inactive)
              Developer:
              Umesh Kadam (Inactive)
              QA:
              Mahendra Mungase (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 3h
                  3h