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
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
Discussion and try to reproduce issue on local environment
Check reports on productions
Check scope and discussion related to optimization in existing queries
Unit testing
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.
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.
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
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
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.
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
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.
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
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
Bug
Critical
Vijay Siddha (Inactive)
made changes -
Gaurav Sodani (Inactive)
made changes -
Parmeshwar Jumbad (Inactive)
made changes -
Sachin Hingole (Inactive)
made changes -
Khandu Kshirsagar (Inactive)
made changes -
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 
file for current implementation and bug resolution approach. 
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