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

Prime_Healthcare: GGH. Server Error on OE Changes Report

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Bug Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
    • Environment:
      Production
    • Bug Severity:
      Critical
    • Module:
      BenAdmin - Report
    • Reported by:
      Harbinger
    • Item State:
      Stage QA - Production Deployment on Hold
    • Issue Importance:
      Must Have
    • Sprint:
      WT Sprint 33-Bugs

      Description

      Receiving a server error when attempting to preview the OE Changes Report for Prime_Healthcare: GGH company.

      Report Parameters:
      From Date = 10/10/2016
      To Date = 10/23/2016
      All Classes, All Status, All Benefit Provider, All Benefit Types, All Plan Design

      Vijay Siddha, Samir

        Attachments

          Issue Links

            Activity

            Hide
            prasanna Prasanna Karlekar (Inactive) added a comment - - edited

            Hi Shubhankar Joshi,

            Following are the 3Cs:
            Concern:
            Receiving a server error when attempting to preview the OE Changes Report for Prime_Healthcare: GGH company.

            Cause:
            This company has setting for Classwise Open Enrollment. In system, there is a database table to save Classwise Open Enrollment rules. For this company, it has entries for previous year Open Enrollment also. Employees are eligible for current year as well as previous year rule. Due to which elections with effective date 1/1/2016 and 1/1/2017 both are getting populated, which is causing the error.

            Correction:
            Need to check if Open Enrollment rules for previous years also exists in the "OpenEnrollmentRules" table. If yes, then implementation changes will required.

            As of now giving temporary fix for this issue to avoid server error. Permanent fix needs to be worked on at earliest

            cc: Satya, Samir, shyam sharma, Vijay Siddha

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - - edited Hi Shubhankar Joshi , Following are the 3Cs: Concern: Receiving a server error when attempting to preview the OE Changes Report for Prime_Healthcare: GGH company. Cause: This company has setting for Classwise Open Enrollment. In system, there is a database table to save Classwise Open Enrollment rules. For this company, it has entries for previous year Open Enrollment also. Employees are eligible for current year as well as previous year rule. Due to which elections with effective date 1/1/2016 and 1/1/2017 both are getting populated, which is causing the error. Correction: Need to check if Open Enrollment rules for previous years also exists in the "OpenEnrollmentRules" table. If yes, then implementation changes will required. As of now giving temporary fix for this issue to avoid server error. Permanent fix needs to be worked on at earliest cc: Satya , Samir , shyam sharma , Vijay Siddha
            Hide
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment -

            3C's:
            Concern and cause metioned in above comments
            Correction: Now we are considering OE rules for current date (i.e. OE rule which is open for current date). If any OE is available for today's date then we are returning results otherwise we will get no records screen. As per current implementation result on report only will display if OE period is in progress.

            Affected Areas: Open Enrollment Report

            Tested Scenarios:
            1. Checked reports in both conditions of ApplyOERules (i.e. Yes and No)
            2. Modified demographics of Employee and verified it displaying on report or not as expected.

            Afftected Files:
            /MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_GetOEEffectiveDateForAllEmployees.StoredProcedure.sql
            /MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_OpenEnrollmentChangesAllBenefits.StoredProcedure.sql

            Note: We could not able to reproduce issue on local environment but handled code to return only Current OE records.

            Show
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment - 3C's: Concern and cause metioned in above comments Correction : Now we are considering OE rules for current date (i.e. OE rule which is open for current date). If any OE is available for today's date then we are returning results otherwise we will get no records screen. As per current implementation result on report only will display if OE period is in progress. Affected Areas : Open Enrollment Report Tested Scenarios: 1. Checked reports in both conditions of ApplyOERules (i.e. Yes and No) 2. Modified demographics of Employee and verified it displaying on report or not as expected. Afftected Files: /MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_GetOEEffectiveDateForAllEmployees.StoredProcedure.sql /MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_OpenEnrollmentChangesAllBenefits.StoredProcedure.sql Note : We could not able to reproduce issue on local environment but handled code to return only Current OE records.
            Hide
            meghana.joshi Meghana Joshi (Inactive) added a comment -

            Verified below Scenarios on LB :

            1) Verified OE Changes report when class wise OE is in Progress for all employee
            2) Verified OE Changes report when class wise OE is in Progress by changing demographics data of employee
            3) Verified OE Changes report when class wise OE is in Progress by changing enrollment of employee
            4) Verified OE Changes report when class wise OE is not in Progress
            5) Verified OE Changes report when OE is in Progress for all employee

            Working Fine

            CC - Sachin Hingole

            Show
            meghana.joshi Meghana Joshi (Inactive) added a comment - Verified below Scenarios on LB : 1) Verified OE Changes report when class wise OE is in Progress for all employee 2) Verified OE Changes report when class wise OE is in Progress by changing demographics data of employee 3) Verified OE Changes report when class wise OE is in Progress by changing enrollment of employee 4) Verified OE Changes report when class wise OE is not in Progress 5) Verified OE Changes report when OE is in Progress for all employee Working Fine CC - Sachin Hingole
            Hide
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment - - edited

            Hi [~meghana joshi]

            Keep this JIRA on hold because it is blocked due to WT-4073 (Generic Eligibility changes). We can move this once Generic Eligibility changes get deployed on stage.

            -CC: Prasanna Karlekar

            Show
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment - - edited Hi [~meghana joshi] Keep this JIRA on hold because it is blocked due to WT-4073 (Generic Eligibility changes). We can move this once Generic Eligibility changes get deployed on stage. -CC: Prasanna Karlekar
            Hide
            vinanti.yadav Vinanti Yadav (Inactive) added a comment -

            Hi [~meghana joshi],

            JIRA WT-3747 is main Enhancement to implement 'Generic Eligibility Component for Class wise open Enrollment - UI and Business logic'. We can not move WT-3747 jira to stage in regular stage build. its require migration of Generic Eligibility for all companies. This will get deploy on stage when LB branch is move to Stage branch.

            Thanks & Regards,
            Vinanti.

            CC : Amruta Lohiya, Prasanna Karlekar, [~parmeshwar.jumbade], Satya, Vijay Siddha

            Show
            vinanti.yadav Vinanti Yadav (Inactive) added a comment - Hi [~meghana joshi] , JIRA WT-3747 is main Enhancement to implement 'Generic Eligibility Component for Class wise open Enrollment - UI and Business logic'. We can not move WT-3747 jira to stage in regular stage build. its require migration of Generic Eligibility for all companies. This will get deploy on stage when LB branch is move to Stage branch. Thanks & Regards, Vinanti. CC : Amruta Lohiya , Prasanna Karlekar , [~parmeshwar.jumbade] , Satya , Vijay Siddha
            Hide
            meghana.joshi Meghana Joshi (Inactive) added a comment -

            Now, Patch is Ready For Stage.

            CC - Sachin Hingole , [~parmeshwar.jumbade] , Prasanna Karlekar

            Show
            meghana.joshi Meghana Joshi (Inactive) added a comment - Now, Patch is Ready For Stage. CC - Sachin Hingole , [~parmeshwar.jumbade] , Prasanna Karlekar
            Hide
            meghana.joshi Meghana Joshi (Inactive) added a comment -

            Verified on Stage.

            Working Fine

            CC - Sachin Hingole

            Show
            meghana.joshi Meghana Joshi (Inactive) added a comment - Verified on Stage. Working Fine CC - Sachin Hingole
            Hide
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment - - edited

            Hi Gaurav Sodani

            Have added WT-5940- Issue and implementation Approach.xls file for current implementation and bug resolution approach.

            CC: Prasanna Karlekar Satya

            Show
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive) added a comment - - edited Hi Gaurav Sodani Have added WT-5940- Issue and implementation Approach.xls file for current implementation and bug resolution approach. CC: Prasanna Karlekar Satya
            Hide
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment -

            Verified this fix on Production. Working fine as expected

            Show
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment - Verified this fix on Production. Working fine as expected

              People

              Assignee:
              venkatesh.pujari Venkatesh Pujari (Inactive)
              Reporter:
              shubhankar Shubhankar Joshi (Inactive)
              Account Executive:
              Amber Love-Jones (Inactive)
              Developer:
              Parmeshwar Jumbad (Inactive)
              QA:
              Meghana Joshi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 59h
                  59h