High 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.
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.
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(
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
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