-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Enrollment
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
A new Credit- Credit 0429 A is created in credit pool. Rule set for 'Demographic eligibility Rules' is Credit Rule 0429 A with criteria-
All Class + All Class + All Employee Status. Additional eligibility criteria set is 'Employee ID is Null'
New Rate is created Rate 0429 A;Sub Rate 0429A, rule set for 'Demographic eligibility Rules' is Rule0429 B with criteria-
All Class + All Class + All Employee Status
New Plan- Plan 0429 A (Plan uses credit pool-Y) is designed, rule set for 'Demographic eligibility Rules' is Rule0429 B with criteria-
All Class + All Class + All Employee Status
Benefit Type under which Rates and Planned are created is- 'BT 0429 A'. Rate 0429 A and Plan 0429 A are mapped.
Also, Credit 0429 A is mapped with BT 0429 A.
When Employee with Null EmpID is enrolled he gets enrolled successfully but Spending Credits shown is 0.
Expected Output-
Spending credits should get adjusted as per amount set under credit pool and should not be 0.
Affected File:
\WT\WORKTERRAweb\App\BusinessLogic\EligibilityEngine\GenericEligibilityRule.vb
Please find below 3'c
Concern: Eligibility additional field is not saving for field which is having value as NULL.
Cause: There was condition was missed for NULL criteria.
Correction: We have handled this scenarios properly.
In next LB patch this patch will move.
Please assign this ticket to QA team.
Verified below scenarios on LB.
Added additional criteria as Employee ID IS NULL on Credit Pool :
1) Verified credit pool allocation when Employee having Employee ID
2) Verified credit pool allocation when Employee does having Employee ID
Added additional criteria as Worked Hours IS NULL on Credit Pool :
1) Verified credit pool allocation when Employee having Worked Hour
2) Verified credit pool allocation when Employee does having Worked Hour
Working Fine
Verified on Stage and it is working Fine.
Item status is not updated because it is depend upon eligibility components.
This will deploy on production with production build.
Verified below scenarios on Production and all are working Fine.
Added additional criteria as Employee ID IS NULL on Credit Pool :
1) Verified credit pool allocation when Employee having Employee ID
2) Verified credit pool allocation when Employee does having Employee ID
Verified Credit pool allocation without addition of any criteria
Hi Amit,
As per analysis, tried above scenario. Following are the analysis:
When Additional eligibility criteria is set to 'Employee ID is Null', wrong query is getting generated. Due to this, on Eligibility check, server error is thrown for incorrect syntax.
We need to check and correct the Eligibility query generation.
Please find attached log for the same.
429201640900PM_1_12911.txt
Assigning ticket to Amruta as currently not working on Generic Eligibility Changes.