Hi Jaideep/Amit,

I have verified this issue and below is my observation.

1] There is Additional Eligibility Criteria on Tobacco Surcharge form.

2] To eligible this form employee need to satisfied additional eligibility criteria.

3] Tried first on UI by raising QE and saved Are you or anyone covered under Wheaton Franciscan Healthcare Medical Plan tobacco users? as YES

4] On Enroll now Screen it showing Tobacco Surcharge plan and it is enrolled automatically no need to enrolled force fully.

5]But, When i tried this through Import Fields value Are you or anyone covered under Wheaton Franciscan Healthcare Medical Plan tobacco users? as YES is imported successfully for employee but employee not enrolled in Tobacco Surcharge plan.

6] When i saved Tobacco Surcharge form again though UI on Enroll now Screen it is showing Tobacco Surcharge plan is enrolled automatically.

7] Also crossed verified though import for Are you or anyone covered under Wheaton Franciscan Healthcare Medical Plan tobacco users? with value NO

It is working fine and plan is not eligible for employee and not showing on enroll now screen.

Forced enrollment routine not working properly through import.

Please check this.

Thanks & Regards,

Rashmita

hi Amit Thorve,

I have started working on this. Unfortunately, I have not come to any conclusion yet. I will update you on this on Monday

Jaideep Vinchurkar, Samir, Rakesh Roy, Sachin Khandge,

I cannot wait to load the data till Monday, I at least want to know why the elections for Smoker Surcharge are not getting loaded through import.

CC - David Rhodes

Hi Amit,

We are looking into it, we will update you ASAP.

Hi Amit,

Here are the details.

1] Loading answers did not force plan

yes, it did not, Per analysis we found the forced plan get allocated through import only when we are making change in original plan.
So here loading answer is not changing anything in Medical plan that is why it is not forcing Tobacco surcharge plan.
Jaideep will let you know more detail on this.

2] Tobacco surcharge enrollments not loading even if tried explicitly
No, they are loading. we have tried to import enrollment of tobacco surcharge and it went properly. please try again and let us know if you face problem here.

Vinayak Kulkarni, Jaideep Vinchurkar, Samir, Sachin Khandge

I just tried to import the Smoker Surcharge file again and getting the same bad records file. All records are going in bad file with reason "Employee does not satisfy contingent eligibility plan design rule."

Hi Amit Thorve,

Please check the details:

Concern: File getting kicked out with error "Employee does not satisfy contingent eligibility plan design rule."

Cause:
There is in issue with date format you have selected (YYYY-MM-DD). The date is changed from any format to 'MM/DD/YYY' during import and same format is used while checking the eligibility.
The format you have used is missing conversion at a point and hence making it not satisfy the condition and throwing records to bad.

Correction: This will need a code fix. For now, you can use 'MM/DD/YYYY' format on Template and File. I've changed the format on template.
Vinayak Kulkarni used the second format and so his file was successful.

We'll update you with ETA for code fix soon.

Thanks Suraj Sokasane for the updates.

Vinayak Kulkarni didnt specify in his comments that he changed the format.

Verified on LB Environment,
Verified date format for below scenarios:
1]MM/DD/YY -Import Successfully and cross verified for bad file
2]YYYYMMDD-Import Successfully and cross verified for bad file
3]YYYY/MM/DD-Import Successfully and cross verified for bad file
4]MM-DD-YYYY-Import Successfully and cross verified for bad file

5]For force contingency
6]For General contingency.
7]Verified on UI

Working Fine as expected

Verified on Stage Environment,
Verified date format for below scenarios:
1]MM/DD/YY -Import Successfully and cross verified for bad file
3]YYYY/MM/DD-Import Successfully and cross verified for bad file
4]MM-DD-YYYY-Import Successfully and cross verified for bad file
Working Fine for above scenarios
but not working for
1]YYYYMMDD-Import Failed
2]DDMMYYYY- Import Failed

refer below error log:

ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ProcessImportDataFile->ImportValidation.ValidateAndInsertData->ImportValidation.ProcessAllOtherTableExceptEmployee->ImportValidation.ProcessAffidavitAndFormData->FormBuilder.CheckEmployeeEligibilityForPage->FormBuilder.GetAdditionalCreiteriaPageInfo
ErrorMessage: Conversion from string "20160101" to type 'Date' is not valid.

Not able to test for contingency.
getting Run time error follow below steps.
1]Select employee
2]Go to enroll now screen
3]Import Into the contingent plan file went to bad because of reason "Employee Does not satisfied plan design eligibility.
4]Again got to same employee enroll now screen
5]Show run time error tried on more than 2 company.

please check

Satya and Rashmita Dudhe What is the status of this issue?

This issue is fixed and deployed on stage. Rashmita is not able to test it because of some another issue.
Rashmita Dudhe: You the issue you have mentioned above is fixed but since LB is freezed for pre-stage build we can not deploy it. For time being, you can try different logins for import and for enroll now screens

Verified on Stage Environment,
Verified date format for below scenarios:
1]MM/DD/YY -Import Successfully and cross verified for bad file
2]YYYYMMDD-Import Successfully and cross verified for bad file
3]YYYY/MM/DD-Import Successfully and cross verified for bad file
4]MM-DD-YYYY-Import Successfully and cross verified for bad file

5]For force contingency on plan
6]For General contingency on plan
7]Verified on UI

Working Fine for above so moving it to production.

Verified on Production Environment,
Verified date format for below scenarios for election import as well as demographic import
1]MM/DD/YY -Import Successfully and cross verified for bad file
2]YYYYMMDD-Import Successfully and cross verified for bad file
3]YYYY/MM/DD-Import Successfully and cross verified for bad file
4]MM-DD-YYYY-Import Successfully and cross verified for bad file

5]For force contingency on plan
6]For General contingency on plan
7]Verified on UI

Working Fine for above so moving it to production.

Amit Thorve
Hi Amit,

This is deployed and verified on Production date format issue is solved now for Election Import.
Kindly, Update jira accordingly

Thanks & Regards,
Rashmita