-
Type:
Bug
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Medium
-
Level:Partner
-
Module:BenAdmin - Report
-
Reported by:Harbinger
-
Company:EHMC
-
Item State:Production Complete - Closed
Check preview for 10/1/2017 to 10/312017--Server error
Error log--
ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->BenAdminControllerAppTier.SaveAndGetData->StaticReports.SaveAndGetData->OpenEnrollmentChangesReport.GetData->OpenEnrollmentChangesReport.FetchOpenEnrollmentChangesData->OpenEnrollmentChangesReport.FetchEnrollmentAndRatesData
ErrorMessage: Item has already been added. Key in dictionary: '35022~10' Key being added: '35022~10'
StackTrace: at WORKTERRA.BenAdmin.BenAdminControllerAppTier.SaveAndGetData(BenAdminControllerWebTierEntity objBenAdminControllerWebTierEntity)
at WORKTERRA.ControllerAppTier.SaveAndGetData(Int32 intProjectsId, String strInput)
TargetSite: System.String SaveAndGetData(ValueObjects.BenAdminControllerWebTierEntity)
Have re-opened the JIRA, as changes needs to be done in old code to make this report work.
Thank you!
Hi Sachin Hingole,
We were expecting WT-5940 to get deployed on Production. But its deployment is on hold as Generic Eligibility changes for Classwise OE are not going on Production.
On Production fix needs to be given with old code on which we are currently working. After the fix is done, code needs to be deployed and tested in Production environment directly as LB and Stage have Classwise OE customization with Generic Eligibility.
Removing the reference of WT-5940 from this JIRA. Also, changing, item state and status.
Thank you!
cc: Gaurav Sodani, [~parmeshwar.jumbade]
Hi Sachin Hingole,
Assigning this JIRA to you as no separate code fix is required for this.
This needs to be verified once WT-5940 is deployed in Production environment.
Thank you!
cc: Gaurav Sodani, [~meghana joshi], [~parmeshwar.jumbade]
Hi Sachin Hingole,
This issue is same as WT-5940.
It will get resolved once WT-5940 is deployed in Production Environment.
cc: Gaurav Sodani, [~parmeshwar.jumbade], [~meghana joshi]
Will provide an update for this on 13-Oct-2017.
cc: Gaurav Sodani
Vijay Siddha (Inactive)
added a comment - CC: Satya , Gaurav Sodani 
Concern:
Receiving a server error when attempting to preview the OE Changes Report.
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 for current as well as previous Open enrollment are getting populated.
Correction:
Now we are considering OE rule which is recently active. We are returning result only for recent active OE rule. Please note that, whenever OE report is executed with Enrollment Opening and Closing Date after OE period ends, it should fetch only the changes that were done between specified OE span.
Affected files:
/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_GetOEEffectiveDateForAllEmployees.StoredProcedure.sql
/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_OpenEnrollmentChangesAllBenefits.StoredProcedure.sql
Impacted Areas:
OE report when executed for classwise OE.
Unit tested scenarios:
1. Verified OE changes report with and without classwise OE setting.
2. Verified OE report for class wise OE, after the OE period completion.