-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:Support
-
Company:El Dorado
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
-
Sprint:WT Sprint 34-Bugs
Hi Satya,
Can you please assist with why the Dental and Vision records exported on the Payroll_El Dorado_DV_2016 template and the Medical exported out on the next Medical file on 01/19/2017 for Debra Touchette. Medical template called Payroll_El Dorado_Medical_2016
According to the client Debra Touchette had a pending request during the 1/6 file timeframe but was not approved until after this time and they are saying the dental/vision elections should not have exported out on the file on 1/6. Pending requests are not coming over, correct?
On Fri, Jan 20, 2017 at 1:46 PM, Sandra Kesler <sandra.kesler@edcgov.us> wrote:
Touchette came over on the Dental/Vision file but not the Medical file posted on 1/6
Also:
Angela Weide had no changes for any fields associated with the Medical file and did not export as expected but did come on the Dental/Vision file on 01/19/2017. Need to know why the elections for Angela Weide exported on the Dental/Vision export file.
Thanks!
Cindy
Verified this issue on Stage Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision
Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.
Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected
found one scenario specific issue created jira :WT-10501 with this known issue changing status as ready for production
Verified this issue on Production Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision
Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.
Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected
Hi,
This is deployed and verified on Production.
While testing found one existing issue Jira:WT-10501 which is under development.
Kindly, Check and Update this jira accordingly.
Thanks,
Rashmita
I have not had any additional issues reported. Closing ticket
Verified this issue on Lb Environment consider below scenario
Customization
Dental and vision plan force contingent on Medical plan with Exact tier match up.
1]: Done 1st enrollment through Admin change event with effective date 08/01/2016 with EE+SP tier in Medical Plan with Dental and vision which are contingent Plan so it was also enrolled with same effective date.
2]Done 2nd enrollment through BIRTH-ADOPTION event with effective date 04/01/2017 with EE+SP+CH tier in Medical going for Admin Approval pending with contingent plan Dental Vision
Scenario 1: Pending Queue when we accept Medical plan then Enrollment done both with medical and all contingent plan.
Scenario 2:Pending Queue when we Reject Medical plan then contingent plan also rejected.
working fine as expected
found one scenario specific issue created jira :WT-10501 with this known issue changing status as ready for stage