High We (Tibco) have an employee that went into the system to update the commuter benefit effective 3/1/17. The event appears to be correct, but when Patrick ran the billing invoice it appears the Vision plan reverted back to the plan that was in effect for 2016 and termed it out. This plan is no longer available for 2017. I have attached a print screen of the “view history” and the commuter event (see attached)
What could possibly have caused this?
I (Tibco) had to create an event for 1/1/2017 in order to add the 2017 vision base plan in his record.
We will give a try to reproduce this at our end. This is in progress
Any update?
Hi Debbie Kulling,
We tried to reproduce mentioned issue but is not reproduced at our end.
We tried same scenario as of 'Anton Fomin' as below:
-We added back same contingencies(Which was removed) on 'VSP Vision plan 2016'
-Raised 'BCC admin changed' QE event and enrolled in "VSP Vision plan 2016" from 09/01/2016 -set termination date as 12/31/2016
-Raised 'Commuter-Transit Benefit Updates' QE and enrolled in "VSP Base Vision Plan" plan with date 01/01/2017 and set termination date as 08/31/2016
-As per QE effective date rule, he got QE mode with 03/01/2017 effective date
-Employee went through his QE enrollment modes - made few elections - made some EDS change.
-After finishing QE mode, his status changed from 'Incomplete' to 'Complete' in system (shown in employee's history)
-The 2016 election in VSP Vision plan 2016 remained active till 12/31/2016 - while his 2017 election in VSP Base Vision Plan remained ON from 01/01/2017
Through all the actions performed above - we never observed the termination date set as NULL with employee's 2016 plan election.
We will try to keep an eye on such scenarios in our daily testing - if we encounter with such scenario, we will notify the same with steps to reproduce the same
Please do let us know in case of you need any further help on this.
Thanks,
Jayshree
CC; Prasad Pise Rakesh Roy Alankar Chavan Jyoti Mayne Umesh Kadam Vinanti Yadav Sumeet.Kolge Satya
Jayshree Nagpure (Inactive)
added a comment - Hi Debbie Kulling ,
We tried to reproduce mentioned issue but is not reproduced at our end.
We tried same scenario as of 'Anton Fomin' as below:
-We added back same contingencies(Which was removed) on 'VSP Vision plan 2016'
-Raised 'BCC admin changed' QE event and enrolled in "VSP Vision plan 2016" from 09/01/2016 -set termination date as 12/31/2016
-Raised 'Commuter-Transit Benefit Updates' QE and enrolled in "VSP Base Vision Plan" plan with date 01/01/2017 and set termination date as 08/31/2016
-As per QE effective date rule, he got QE mode with 03/01/2017 effective date
-Employee went through his QE enrollment modes - made few elections - made some EDS change.
-After finishing QE mode, his status changed from 'Incomplete' to 'Complete' in system (shown in employee's history)
-The 2016 election in VSP Vision plan 2016 remained active till 12/31/2016 - while his 2017 election in VSP Base Vision Plan remained ON from 01/01/2017
Through all the actions performed above - we never observed the termination date set as NULL with employee's 2016 plan election.
We will try to keep an eye on such scenarios in our daily testing - if we encounter with such scenario, we will notify the same with steps to reproduce the same
Please do let us know in case of you need any further help on this.
Thanks,
Jayshree
CC; Prasad Pise Rakesh Roy Alankar Chavan Jyoti Mayne Umesh Kadam Vinanti Yadav Sumeet.Kolge Satya
Hi Prasad Pise,
This issue is not reproducing from dev and QA side. Please find QA update above and update JIRA status.
Cc: Satya
HI Alankar,
Could you please try to reproduce this issue and share your findings.