New Features 2017Project Type: software

New Features 2017

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

COSB - Contigency Rule is not working correctly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Bug Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
      None
    • Environment:
      Stage
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Client
    • Company:
      COSB
    • Item State:
      Stage QA - Production Deployment on Hold
    • Reported by Customer:
      BCC

      Description

      COSB dental is required if they enroll in medical. We have the Dental contingency rule set to "eligible if enrolled in the Medical benefit type" and the benefit type set to required.

      We can not set the contingency rule to required because there is more than on medical plan.

      The issue that we are having is that if an employee changes their medical plan the system terminates their dental. It does not give you a pop up or anything that warns the employee that the dental has been dropped.

      This group goes live on Monday and I need help with this asap

        Attachments

          Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. WT-11602 COSB - Contigency Rule is not working correctly

          • Critical - This problem will block progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jyoti.mayne Jyoti Mayne added a comment -

            Hi Sachin Hingole,

            Fix is deployed on CodeMap. Please verify.

            Cc: Amruta Lohiya

            Show
            jyoti.mayne Jyoti Mayne added a comment - Hi Sachin Hingole , Fix is deployed on CodeMap. Please verify. Cc: Amruta Lohiya
            Hide
            Permalink
            mahendra.mungase Mahendra Mungase (Inactive) added a comment -

            We have verified same issue on CodeMap with below scenario

            We have executed below scenario
            1. Contingency only on benefit type
            2. Contingency on benefit type and benefit plan
            3. Contingency only on benefit plan

            and observed that it did not terminate dental plan.

            Thanks,
            Mahendra

            Show
            mahendra.mungase Mahendra Mungase (Inactive) added a comment - We have verified same issue on CodeMap with below scenario We have executed below scenario 1. Contingency only on benefit type 2. Contingency on benefit type and benefit plan 3. Contingency only on benefit plan and observed that it did not terminate dental plan. Thanks, Mahendra
            Hide
            Permalink
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - - edited

            Verified on Azure Environment consider below scenarios.

            #scenario1 Benefit type contingency
            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            #Senario2 Contingency on benefit type and benefit plan
            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            #Scenario3 Contingency only on benefit plan

            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            Cross verified on Enrollment summary and confirmation statement
            Working fine as expected

            Show
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - - edited Verified on Azure Environment consider below scenarios. #scenario1 Benefit type contingency 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination #Senario2 Contingency on benefit type and benefit plan 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination #Scenario3 Contingency only on benefit plan 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination Cross verified on Enrollment summary and confirmation statement Working fine as expected
            Hide
            Permalink
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment -

            Verified below scenarios on Production :-

            #scenario1 Benefit type contingency
            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            #Senario2 Contingency on benefit type and benefit plan
            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            #Scenario3 Contingency only on benefit plan
            1]Force contingency: Enrollment and Termination
            2]genral contingency: Enrollment and Termination

            Cross verified on Enrollment summary and confirmation statement
            Working fine as expected

            Show
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment - Verified below scenarios on Production :- #scenario1 Benefit type contingency 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination #Senario2 Contingency on benefit type and benefit plan 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination #Scenario3 Contingency only on benefit plan 1]Force contingency: Enrollment and Termination 2]genral contingency: Enrollment and Termination Cross verified on Enrollment summary and confirmation statement Working fine as expected

              People

              Assignee:
              sachin.hingole Sachin Hingole (Inactive)
              Reporter:
              umesh.kadam Umesh Kadam (Inactive)
              Account Executive:
              Debbie Kulling
              Developer:
              Jyoti Mayne
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 10h
                  10h
                  Remaining:
                  Time Spent - 9.75h Remaining Estimate - 0.25h
                  0.25h
                  Logged:
                  Time Spent - 9.75h Remaining Estimate - 0.25h
                  9.75h