Suraj Sokasane Is this deployed and i f yes then put your comment what fixed and what files are modified?

It is an Enhancement. I have attached the analysis document with all details.

Modified files:
https://delta.harbinger.in/svn/WT/trunk/WORKTERRAweb/App/BusinessLogic/ImportExportDTS/ImportEmployeeEnrollment.vb

Suraj SokasanePlease update status.

Tested on Local environment.
Verified below scenario:
1]Checked their should be the Employer Coverage Amount field in Import.
2] Import Employer Coverage Amount with different coverage amount for different employee imported successfully.
3]Verified on Enroll now screen and view enrollment summary imported cost is showing properly.

But for age banged rule it is not working so created another Jira and assign it to Suraj

Rakesh Roy Is it correct now?

Rashmita Dudhe If any jira ticket is open against any enhancement, parent enahnacment can not be marked as Ready for stage or ready for production.

Rashmita Dudhe Also Test case is mandatory for enhancement

Hi all - the last communication I received on this item was that it will be deployed on Stage yesterday. Please verify that occurred and let me know when it will be deployed on Production. Thanks.

Yesterday it was tested and verified on our local testing environment and will deploy on Monday (2/15 IST )on stage.

Refer https://workterra.atlassian.net/browse/WT-568

Jennifer Leugers]Will deploy this tomorrow morning(2/17 IST) on stage and if everything goes fine will deploy the same on production.

Tested on Stage:
Verified below scenario:
1]Checked their should be the Employer Coverage Amount field in Import.
2] Import Employer Coverage Amount with different coverage amount for different employee imported successfully.
3]Verified on Enroll now screen and view enrollment summary imported cost is showing properly.

We are moving this patch with known issues related Age Band approve coverage amount.

Hi all - was this deployed on Production?

Jennifer LeugersYes, its deployed on production today.

Jennifer Leugers
Hi jennifer,

This is deployed on Production and we have verified it.
[Note: Scope area which is affecting Enhancement i.e Age Band Criteria we are not start working on this related jira WT-618]

Thanks & Regards,
Rashmita

Hi Rashmita - I'm confused by the comments above. Could you please provide more information on what was done in Production and what is included in the enhancement ticket 618? Thanks.

Jennifer Leugers
Hi Jennifer,

Kindly, Go through the attached Document HSA_Age_Wise_Coverage_Amount
For Enhancement Jira ticket 618.
Let us know if you need more information.

Thanks & Regards,
Rashmita

I will look through the enhancement 618 but I'm still confused on what was deployed to Stage. Per the comments I received from Rakesh, it was tested and verified on our local environment and was supposed to deploy on Monday January 15. So what was deployed?
Rakesh Roy

Hi Jennifer Leugers,

In WT- 568 we have allowed to add / update ER coverage using election import. There is no validation on coverage amount as per the age bands. Because of time constraint, we pushed it as it is and created new ticket 618 to provide validations on age bands.
You can use the functionality to add update ER coverage but you have to give exact amount of coverage like we give in other cases.

Hi all - here are UHC comments on the attached document

Sorry for the delay on this! I was able to review the attached and am unsure what we should be commenting on. It looks like from the screen shots the system would continue to operate as it does today with exception that once new functionality is released we will be able to load both EE & ER contributions.

Is the question pertaining to the import allowing greater values than identified in customization chart for EE and/or ER contributions to be successfully imported? If that is the case – then yes our preference would be to have any records error that exceed the threshold identified in the customization chart.

Hi Jennifer Leugers,

Currently, there's no validation on ER Coverage, It'll get in even if you give value greater than the max as per customization.
When the another ticket: WT-618 will be completed, Yes the records with ER exceeding the limit in customization will be kicked out.