WORKTERRAProject Type: software

WORKTERRA

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

WT -> Add Employee -> Server Error cause of auto enrolled plan

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin, Platform
    • Labels:
      None
    • Environment:
      QA
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed

      Description

      1. make a Life plan as auto enrolled plan
      2. have the cost and coverage options as salary multiple
      3. try adding an employee

      Actual result : Server Error

      employee gets created though

      When I go to the above Life plan - plan is not getting auto enrolled

      Error Log -

      ErrorID : 0
      ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->EmployeeData.Save->EmployeeData.UpdateEmployeeProfile->
      EmployeeData.CreateUserForEmployee->CorePlanAllocation.CorePlanAllocationForOptimization->CorePlanAllocation.ActualCorePlanAllocation->
      Eligibility.FetchCheckEligibilityForPlanDesign->Eligibility.IsDatingEligibilitySatisfied
      ErrorMessage: Conversion from type 'DBNull' to type 'Integer' is not valid.

        Attachments

          Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. WT-2287 City of Bellevue - Stage - Custom Payroll Schedule

          • High - Serious problem that could block progress.
          • Closed
          is caused by

          Enhancement - An improvement or enhancement to an existing feature or task. ST-102 Plan Design Screen and Generic Eligibility Screen

          • Medium - Has the potential to affect progress.
          • New Request

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            alankar.chavan Alankar Chavan (Inactive) added a comment - - edited

            Amnesh Goel -

            WT 2287 is tested - all working well
            I want to test one scenario with the auto enrolled plan - which I can not do because of WT 2375
            Please fix this as earliest - so as WT 2287 can be move to Stage

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - - edited Amnesh Goel - WT 2287 is tested - all working well I want to test one scenario with the auto enrolled plan - which I can not do because of WT 2375 Please fix this as earliest - so as WT 2287 can be move to Stage
            Hide
            Permalink
            aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

            My findings after analysis for this bug is :

            Cause: When there is NULL value in ZipCodeRuleID and system try to convert NULL into Int, Exception occurs.
            Page: Eligibility.vb
            Method: IsDatingEligibilitySatisfied(

            Show
            aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - My findings after analysis for this bug is : Cause: When there is NULL value in ZipCodeRuleID and system try to convert NULL into Int, Exception occurs. Page: Eligibility.vb Method : IsDatingEligibilitySatisfied(
            Hide
            Permalink
            prasanna Prasanna Karlekar (Inactive) added a comment - - edited

            Concern:
            When there is NULL value in ZipCodeRuleID and system try to convert NULL into Int, Exception occurs.

            Cause:
            As per discussion with Aditya, Default Rule was mapped to core plan due to which error occured.
            Script for Default Plan was incorrect. It had ZipCodeEligibility set to 1 with ZipCodeRuleID set to NULL.
            From screen this will never happen.

            Correction:
            Script for Default Rule is corrected. It will be deployed in next patch.
            This issue is on LB only as Generic Eligibility changes are on LB environment only.
            Fix is deployed on LB. Please verify.

            File Changes:
            Script to insert Default rule: 33_ST1_WTB_NewData_GenericEligibilityRules

            Impacted areas:
            Enroll Now screen for Plans / Rates / Credit Pool where "Default" Rule is mapped.

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - - edited Concern: When there is NULL value in ZipCodeRuleID and system try to convert NULL into Int, Exception occurs. Cause: As per discussion with Aditya, Default Rule was mapped to core plan due to which error occured. Script for Default Plan was incorrect. It had ZipCodeEligibility set to 1 with ZipCodeRuleID set to NULL. From screen this will never happen. Correction: Script for Default Rule is corrected. It will be deployed in next patch. This issue is on LB only as Generic Eligibility changes are on LB environment only. Fix is deployed on LB. Please verify. File Changes: Script to insert Default rule: 33_ST1_WTB_NewData_GenericEligibilityRules Impacted areas: Enroll Now screen for Plans / Rates / Credit Pool where "Default" Rule is mapped.
            Hide
            Permalink
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            FYI Prasanna Karlekar Deepali Tidke Rakesh Roy

            This is tested on WT Stage - 13th May 2016

            1. No server error on Add Employee
            2. Employee's are getting their auto enrolled plans (plans where default eligibility rule was saved)
            3. also tested this with couple of more pages where there was a default rule mapping

            Working well

            As discussed with Prasanna, this exists on LB only - hence closing this issue at LB level only

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - FYI Prasanna Karlekar Deepali Tidke Rakesh Roy This is tested on WT Stage - 13th May 2016 1. No server error on Add Employee 2. Employee's are getting their auto enrolled plans (plans where default eligibility rule was saved) 3. also tested this with couple of more pages where there was a default rule mapping Working well As discussed with Prasanna, this exists on LB only - hence closing this issue at LB level only

              People

              Assignee:
              alankar.chavan Alankar Chavan (Inactive)
              Reporter:
              alankar.chavan Alankar Chavan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: