Check after todays LB build.

Hi all - do we have any ETAs on this?

Rakesh RoyHrishikesh Deshpande

Hi Aniruddha,

Please update its testing status & by when it can be moved to Stage environment?

Thanks & Regards,
Satya Prakash.

Jennifer Leugers

Hi Jennifer,

We are setting up local environment for COBRA scenarios Testing on Local which we'll complete by tomorrow .
We'll deploy this fix on stage on Wednesday 5/11/2016.

We'll keep updating you on its progress.

Thanks & Regards,
Aniruddha Dev

CC:Hrishikesh DeshpandeVinayak KulkarniRakesh Roy

Hi Vinayak,

Verified on LB on FDU COBRA Templates (COBRA PAR, COBRA COV Med and COBRA COV Den, COBRA DEP) for below scenarios

1) Divorce
2) Deceased
3) Retirement
4) OAD
5) LOA

Only Termination , Divorce and OAD scenarios are working No records are getting exported for other scenarios.

Also observed one doubtful scenario while trying Termination scenario came across one employee ( BEHSON SCOTT) which had enrollment in UHC POS Medical and Delta Dental PPO with EE+CH. But spouse (Name-Griffin Amy) is also exported on COBRA DEP file along with Child even though the spouse is currently not enrolled in the Plan. (NOTE: Previously spouse was enrolled in this plan and it was terminated on 11/02/2015.)
Please let us know whether 'COBRA Notice Indicator ' mapped on template has something to do with this ? and the record exporting on the file is proper or not ?

*Testing is in Progress *

CC: Rohan J KhandaveHrishikesh Deshpande

Hi Vinayak Kulkarni

Verified all above scenarios (Except OAD - Created this scenario will update about it tomorrow after execution) on MATT company of LB on Wageworks_Ceredian_MATT_QE Template . Scenarios working properly and as expected

Also verified Termination after OAD scenario mentioned in the description on FDU COBRA templates and below is the observation .

1) Par file: EE termination exported (Passed)
2) Dep file: OAD also exported along with the dependents (Failed)
3) COV file: the coverage for the EE and remaining dependents (Passed)

Please look into the 2nd issue and the issue mentioned above for Deceased , Retirement and LOA scenarios

Today Verified below things.

1) Verified OAD scenario on MATT for Wageworks_Ceredian_MATT_QE template . It is working as expected.

2) verified termination after OAD scenario on FDU again and confirmed that 2nd issue listed in the above comment exists. and also observed that no records getting exported on either of the COV templates on Termination after OAD scenario.

3) Verified Termination, Retirement, Divorce, Death , FMLA and OAD scenario on JAMBA JUICE company on LB on _DiscoveryBenefits_COBRA_QB_PLAN 2015 Template and Observed that only Termination and Death Scenarios are working properly

4) Also verified WT-1850 along with this . which is working as expected

Note: for COV File scenario in the above comment . I've added a test child before terminating the employee. Here in #2 there were already two children enrolled in the plan out which one got ineligible

Hi Aniruddha,

We revisited implementation and below is findings

For Cobra notice indicator below scenarios are implemented

1] Termination
2] Divorce
3] OAD

For Discovery Benefits cobra

1] Termination
2] Retiree
3] Deceased
4] Divorce
5] OAD

As per our discussion in the call Today. i've verified below

1) Verified 'Termination after Divorce' scenario on FDU company on LB and observed below

a] Par file: EE termination not exported on file (Failed)
b] Dep file: Ex-Sposue also exported along with the dependents (Failed)
c] COV file: No records exported on COV files (Failed)

2) Verified Retirement, OAD scenario on JAMBA JUICE - Working as expected

Hi Aniruddha,

Exspouse status was selected on plan eligibility, so spouse wasn't removing from coverage even if you made status as Ex-spouse.
I have update eligibility to test.

The FDU cobra fixes are also checked into LB, please verify them after LB build. If they works proper then regress entire tests. Thanks.

Hi Vinayak,

LB patch deployed yesterday (05/12/2016) evening so couldn't check this yesterday but created OAD scenarios for today.Verified these scenarios along below scenarios on FDU , Jamba Juice and MATT companies on LB

1) Termination
2) Retirement(Not on FDU)
3) Death (Not on FDU)
4) Divoce
5) OAD
6) FMLA (Not on FDU and Jamba Juice)
7) Employee Termination after OAD (On all above comapnies)
8) Employee Termination after Divorce (On all above companies)

Below are the observations/issues for FDU

After Termination of the employees who had - OAD and Divorce initially

PAR File : Participants for Termination ,OAD, Divorce Scenarios exported successfully

DEP File: Dependents for the employee(KRISTIN GRANADE) did not export on file. (This employee had divorce scenario before).For OAD employee this is working fine

COV File: Value for Enrollment members covered is getting exported as EE only in case of all OAD, Termination and Divorce scenarios. Actual members covered were EE+FAM. Please confirm this ?

Observations/Issue for Jamba Juice _DiscoveryBenefits_COBRA_QB_PLAN 2015 Template

No records exported for 'Employee Termination after OAD and Divorce Scenario'.

Scenarios on 'Matt' Wageworks_Ceredian_MATT_QE Template are working fine.

Note: Please confirm the working of COBRA coverage Tier Label and enrollment members covered .
1) For COBRA coverage tier label value is getting exported as per the covered members in the plan . (Check MATT Template)
2) Only EE is getting exported for Enrollment members covered (Check UHC COBRA COV MED/ DEN on FDU)

Jennifer Leugers
Hi Jennifer,
Internally we have found some issues in our Local testing. We will update you once they're fixed/resolved.

Regards,
Aniruddha Dev

Ok thanks - I have a call with UHC tomorrow so any updates would be appreciated.

Hi Jennifer,

We have almost done but we have some issues with cobra coverage template, once this is done, we will release this on stage followed by production.

Hi Anirudhha,

Member covered is coming EE every time is because its field length is 2. Considering this customization on main FDU production will not have any impact of any cobra event.
see below

Also note below

1] Members covered is not recommended to be use on cobra templates. as its tied with termed enrollment regardless of event,

For example, event OAD terminated an enrollment of EE+SP+2CH and continued EE+SP+CH then on file only child is coming up but member covered for termed enrollments are EE+SP+2CH, so it will populate on file.

Whereas cobra coverage tier is calculated upon actual members on file, consider same example given above, so only child is coming up in file then cobra coverage will be single.

Hi Vinayak,

Verified after the fix deployed on Monday evening . With all above scenarios for FDU, MATT and Jamba Juice companies on LB and observed below

1) for FDU
PAR File : Working as expected
DEP File : Working as Expected
COV File : Working as Expected*

Note*: Enrollment members covered are as expected and explained above by you

2) For MATT

All Scenarios are working fine .

Note: for divorce scenario - cobra coverage tier label exported is for SPOUSE, as spouse only is the one exported on the COBRA file. But in case of OAD scenario COBRA coverage tier label is FAMILY. please have a look at the record for employee 'Alonzo Villasenor' and update me regarding this.
Also verified for WT-1850 . Please check the comment on that JIRA

3) for JambaJuice

No records exported for 'Employee Termination after OAD/Divorce Scenario'. The scenario is explained below

Plan termination date 05/31/2016 and Employee Terminated before 05/31/2016 then records are not getting exported on the file . Where records are exported on the file for the Employee Termination after 05/31/2016.
Test Employee which have Termination after divorce s: 1) Shannon Patrick 2) Wilson Renee

Regards,
Aniruddha Dev

HI Aniruddha ,

We have checked on MATT but could not find any issues with Cobra coverage tier label, Below scenarios we have checked

1] Divorce
2] Term after divorce
3] OAD
4] Term after OAD
And it worked well for me, can you re-verify this on MATT.

We will update on JAMBA Juice later. Thanks.

Hello Vinayak,

I could not check my scenarios as the services did not run as per schedule on companies. Ashwin is looking for fixing it on LB. I looked at your files from view exported and those are okay .
Just a question here, when i deleted previous 2 run dates (OAD and Employee Termination after OAD scenarios were there) and exported the file then the OAD record shows 'fam2'.

Can you please confirm is it okay to have like this ?

Regards,
Aniruddha

Hi Aniruddha,

Yes, that is correct, if we deleted two run-dates so we are moving back by two events which took place.
now when you export file then it will consider termination event and OAD will appear as dependent and this is fine.

Our objective is to pass a member only once on file, if child becomes OAD and went on file then we should not pass it on termination event if happened in same month. and if employee is terminated after OAD event but OAD is yet to pass on file then its okay to pass it as dependent as far as member is getting cobra coverage for that benefit.

For Discovery Benefits cobra we have done changes and check it after LB build. Thanks.

File changed for Discovery benefits cobra fix : dbo.OES_UDF_Export_DiscoveryBenefitsCobraNotice.UserDefinedFunction

Vinayak Kulkarni

Hi Vinayak,

Verified the fix on Jamba Juice template for Divorce/Divorce followed by Termination scenario along with Term, Retirement, Death and OAD scenario (Employee Termed on 5/31/2016 in all employee termination scenarios) .
Also verified OAD, Divorce followed by termination scenario on FDU and Matt company on LB .
All scenarios are working as expected.

Note: Please change the status & Item State of this JIRA (Along with WT-1850), so that we can mark it as Ready for Stage .

Hi Aniruddha, changed status of this & WT-1850. Could not find item state for this JIRA.

Marking this JIRA as

Ready for Stage

Vinayak Kulkarni This is missed from Dev or QA team. And how we can catch scenario from next time?

Hi Rakesh,

This was historical bug in our system. So when we solved it for first time then it got re-opened on FDU.
later we found we have large variety of cobra file types on production and they have different implementation in system.
So we had targeted only one of them.

Then we listed down mostly used cobra files from production, solved this for each of them, attached those companies on LB
and tested on them.

So we need to make sure we keep these companies on LB updated to test any thing related to cobra on all of these companies.

Hi Vinayak,

Verified below scenarios on stage companies

1] Termination (FDU Payroll for HSPL and Jamba Juice for HSPL)
2] Divorce (FDU Payroll for HSPL and Jamba Juice for HSPL)
3] OAD (FDU Payroll for HSPL and Jamba Juice for HSPL)
4] Retirement (Jamba Juice for HSPL)
5) Death (Jamba Juice for HSPL)
6) OAD followed by Termination
7) Divorce followed by Termination

and results are
FDU Payroll For HSPL
1) Par file: Working as expected (Passed)
2) Dep file: Working as expected (Passed)
3) COV file:Working as expected (Passed)

Jamba Juice for HSPL
1) In case of Divorce followed by Termination scenario , Enrollment COBRA qualifying event name is blank on the exported file (Failed) Test Employee : 1) Allison,Lindsly 2) Carol,Greenwell

Could not check on MATT for HSPL because getting server error while changing employee status . Conveyed this to EDS team. Will update on this after their reply

Hi Anirudhha,

For Jamba Juice event blank issue, one database store procedure was missed in check-in,

I have updated it on HSPL copy for testing purpose, will check with Rohan J Khandave whether it can be given in patch today.

Vinayak Kulkarni This is only on Stage or production also.
Also I think we should check this script for all companies , what you say?

Rakesh Roy This is deployed stage , so it is updated on LB but not on stage and testing is going on stage.

Hello Vinayak Kulkarni , Aniruddha Dev , Rakesh Roy

I have checked in missed SP into stage branch.

Hi Vinayak,
Verified above listed scenarios on Matt for HSPL and observed one issue .

1) No Records exported for OAD followed by termination and Divorce followed termination .

Below are the test employees

1) Ronald,Molnar JR. (OAD Scenario)
2) Christopher,Richins (Divorce Scenario)

Please look into this . All above issues were working fine on LB.

Hi Aniruddha,

This is due to the missing SP i mentioned in earlier comments and i have already told you that if you are testing then get scripts updated on companies from Rohan. Anyways I will check-in those missing scripts in next stage patch , after patch deployment please use restored companies or get scripts updated on HSPL copy as well from Ashwin.

Verified above after stage patch and Script execution by exporting this template on MATT for HSPL again.
Issue listed above still exist.

Aniruddha Dev Status and comment shows its Re-open but assigned to you, is this correct?

Rakesh Roy

Verified above scenario on stage after stage patch deployment and after script execution is completed. It didn't work.
Today, creating new scenarios again for WT 1850 and Matt for HSPL and will update accordingly after checking this.

hi,

Verified for MATT for HSPL by recreating scenarios after Scripts has been explicitly updated on Matt for HSPL.
Divorce and OAD followed by termination working as expected on Stage. WT-1850 issue still exist.
Will mark the status once WT-1850 is fixed

Hi all - any updates on this?

Hi Jennifer,

This is done but we are working on WT-1850 which is dependent on this in development perspective.
That is why this is on hold. But you can ask UHC to test this on stage.

Otherwise, We are working on WT-1850 from today and we will resolve this ASAP.

As per discussion with Rakesh and Vinayak updated this jira.

Created below scenarios on FDU copy company on Production
1) Termination
2) Divorce
3) Divorce followed by termination

and verified these scenarios on below templates
UHC COBRA PAR
UHC COBRA DEP
UHC COBRA COV_Medical
UHC COBRA COV_Dental
All above scenarios are working as expected on FDU production

Note: Created OAD scenario as well. Testing is in progress with this. Will update tomorrow after 12:00 AM PST.

Verified OAD followed by termination scenario on Production and it is working as expected on Prod.
Also Verified all above mentioned scenarios on Matt for HSPL and Jamba Juice for HSPL COBRA templates

Working as expected on Production

Hi Jennifer ,

We have deployed this on Production.
Can you please verify this at your end and close this JIRA ?

Thanks & Regards,
Aniruddha Dev

Hi all - how did you verify the OAD scenario? UHC is stating it still is not working. Please see below -

I’ve tested this in FDU Prod and it looks like it is working under the Divorce scenario, however, the OAD scenario is still incorrect.

The Par files and the COV files are pulling in the correct info, but the Dep file is still pulling in the terminated (already previously sent) overaged dependent on the second set of dependent termination files.

I tested this in FDU Prod with Jenna Test (OAD) and Travis Test (Divorce).

These are what we are expecting on these connections:

First set of test files run after the dependent is terminated:

Par file: Dep (OAD/Ex-Spouse) termination

Dep file: blank

COV file: the coverage for the family

Second Set of Test files after the EE has terminated status:

Par file: EE termination

Dep file: the remaining dependents (if any) excluding the OAD or Exspouse (Currently Ex-Spouse is correctly being withheld, OAD’s are still being passed)

COV file: the coverage for the EE and remaining dependents

These are the file templates I used:

Test_RA clone COBRA PAR Del after testing

Test_RA Clone COBRA dep del aft testing

Test RA Clone COBCOV med Del aft test

For Jenna Test, She had a child (Baby Test) who turned 26 on 7/21/16. The OAD service ran and removed her coverage. The first set of COBRA files picked up the Baby correctly. Jenna then termed status on 8/2. On the second set of COBRA files, the Par and COV files pulled the correct information, however, the child was still passed on the Dep file.

Hi Aniruddha Dev, could you please reply on Jennifer Leugers questions?

CC: Vijay Siddha, Rakesh Roy

Hi Jennifer Leugers,

We have analyzed above mentioned issue. It occurs only when OAD and OAD followed by EE Termination scenarios take place in different months (as in case of Jenna Test). Implementation works fine when OAD and Employee Termination happen in same month. We'll try to fix it ASAP and update you on its progress. Also we'll add such rare scenarios in our test cases.

Vinayak Kulkarni Can you please look into this at the earliest ?

Regards,
Aniruddha Dev

Hi All,

Code fix is in progress on development environment, We will update once it is done and ready to move further.

Hi all - any ETA on this?

Hi Jennifer,

Separate bug ticket WT-3838 is created under this ticket. ETA is updated over there. Thanks.