-
Type:
Bug
-
Status: Rejected
-
Priority:
Medium
-
Resolution: System Behaviour
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:White Label
-
Company:CSE
Employee: Conard Cline
Admin went in an posted the admin event to enroll the child in child life/ad&d. When she enrolled the child Cason in the life plan the AD&D did not auto enroll the AD&D with the exact coverage and if you go to the AD&D plan to elect the coverage amount shows 0.00
I had this issue happen about a week ago and I was able to correct it by waiving life, which termed the AD&D. When I re-enrolled the coverage the system enrolled the AD&D correctly both children correctly. I did not fix this record so you could see it.
I think the bug is that system cannot enroll the additional child if there is already an enrollment
Hi Debbie Kulling,
Please find below our analysis details :
| Concern | When admin enrolled the child Cason in the "Child Voluntary Life" plan, the "Child Voluntary AD&D" plan did not got auto enrolled with the exact coverage. Also if we go to the "Child Voluntary AD&D" plan to elect, the coverage amount shows $0.00 |
| Cause | On "Plan Design" page and "Cost and Coverage" tab, under "Determine Dependent Max Coverage Amount By Employee Election?" section coverage sharing is set for "Child % on Employee" instead "Child % on Child". Please find attached screenshot for the same.  As only child can enroll in "Child Voluntary Life" plan, employee will not have any coverage. So "Child % on Employee" will not return any coverage for "Child Voluntary AD&D" plan |
| Correction | Please set "Child % on Child", system will return same coverage as "Child Voluntary Life" plan. We have tested the same in HSPL copy and it is working fine. Please check and confirm. |
Thanks and Regards,
:: Umesh Kadam
CC : Satya, Gaurav Sodani, Rohan J Khandave, Jyoti Mayne, Vinanti Yadav, Rohit Shete, Prasad Patil
Thank you that fixed my issue
Satya Gaurav Sodani Hey guys, this ticket was submitted Friday, and it doesn't appear anyone has looked at it yet. I understand that we may not have a root cause yet, but I can't tell if anyone has even begun analysis.