-
Type:
Bug
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:QA
-
Bug Type:Functional
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
-
Sprint:WT Sprint 34-Bugs
Precondition
1) Dental Plan is Contigenct [ Eligible / Forced ] on Medical Plan
2) Employee having enrollment in Medical and Dental Plan
3) Create one benefit level import template
Replication Steps :
1) Navigate to Manual Import Export Page
2) Import Data
Issue : Medical Plan is waived but Dental plan is not waived
CC - Sachin Hingole
- relates to
-
WT-8262 Importing Waived Benefit Type data
-
- Production Complete
-
Verified this issue on LB
Company - QA FDU, QA Wheaton company
Verified waived enrollment.
Observed that waived enrollment are not properly updated on Enroll now screen.
And even termination date is not updating on view history page.
Also contingency scenario is not working.
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - Verified this issue on LB
Company - QA FDU, QA Wheaton company
Verified waived enrollment.
Observed that waived enrollment are not properly updated on Enroll now screen.
And even termination date is not updating on view history page.
Also contingency scenario is not working.
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise Hi Jayshree Nagpure,
Please refer to WT-10678. Contingency for waive import is handled in code fix for mentioned ticket. Also, I have provided the details there.
Thanks,
Snehal
Snehal Katkar (Inactive)
added a comment - Hi Jayshree Nagpure ,
Please refer to WT-10678 . Contingency for waive import is handled in code fix for mentioned ticket. Also, I have provided the details there.
Thanks,
Snehal Hi Snehal Katkar,
Verified this issue on LB
Company - QA Matt for hspl, QA wheaton
Verified below contingency scenario :
1)Medical Plan A - enroll this plan (With this plan, Plan B is also enrolled) 
2)Medical plan B- applied contingency scenario in this plan in eligibility rule
3)For waive import also its expected that when Plan A is waived, Plan B must be waived
4)But we are getting import fail issue when contingency is applied to any plan.
Please note : Error Log for all the attached companies are same
Please find attached error log and screen shot : 
ImportFailContingency.txt
Not working as expected
Hence re-opening this jira
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - Hi Snehal Katkar ,
Verified this issue on LB
Company - QA Matt for hspl, QA wheaton
Verified below contingency scenario :
1)Medical Plan A - enroll this plan (With this plan, Plan B is also enrolled)
2)Medical plan B- applied contingency scenario in this plan in eligibility rule
3)For waive import also its expected that when Plan A is waived, Plan B must be waived
4)But we are getting import fail issue when contingency is applied to any plan.
Please note : Error Log for all the attached companies are same
Please find attached error log and screen shot : ImportFailContingency.txt
Not working as expected
Hence re-opening this jira
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise Hi Jayshree,
Waive import is working as expected for contingency. I checked contingency scenarios for 'City of Durham for HSPL' and 'For QA Caiso for HSPL' companies.
Please refer to below screenshots.
Plan design ids 26,6 and 24 are considered in contingency scenario, for company 'For QA Caiso for HSPL'.
Plan design ids 60,61 and 66 are considered in contingency scenario, for company 'City of Durham for HSPL'.
UI screenshots I have attached in ticket WT-9327.
Again, which you have observed, must be company specific or data issue.
Thanks,
Snehal
Snehal Katkar (Inactive)
added a comment - Hi Jayshree,
Waive import is working as expected for contingency. I checked contingency scenarios for 'City of Durham for HSPL' and 'For QA Caiso for HSPL' companies.
Please refer to below screenshots.
Plan design ids 26,6 and 24 are considered in contingency scenario, for company 'For QA Caiso for HSPL'.
Plan design ids 60,61 and 66 are considered in contingency scenario, for company 'City of Durham for HSPL'.
UI screenshots I have attached in ticket WT-9327 .
Again, which you have observed, must be company specific or data issue.
Thanks,
Snehal
cc: Jaideep Vinchurkar Rakesh Roy Verified for contingency scenario.
Company - QA city of durham for hspl
Contingency scenario is working fine. 
But label is not updating, as discussed with Jyoti Mayne issue exists for UI also.
But from import end, its properly updating on view history.
Hence marking item state as LB QA on hold
Jayshree Nagpure (Inactive)
added a comment - Verified for contingency scenario.
Company - QA city of durham for hspl
Contingency scenario is working fine.
But label is not updating, as discussed with Jyoti Mayne issue exists for UI also.
But from import end, its properly updating on view history.
Hence marking item state as LB QA on hold
verified on stage
Company -city of bellevue for hspl
Verified for contingency scenario.
Working fine
Marking item state as Ready for Production
Jayshree Nagpure (Inactive)
added a comment - verified on stage
Company -city of bellevue for hspl
Verified for contingency scenario.
Working fine
Marking item state as Ready for Production Verified on Production
Working fine
Marking item state as Production complete
Jayshree Nagpure (Inactive)
added a comment - Verified on Production
Working fine
Marking item state as Production complete 
This issue got resolved with enhancement of
WT-9291.