Hi Swapnil Pandhare,

Please refer below findings:

Employee : Bobby Hunter.
Plan Name : Retiree Health Plan.

On Demographic Page : if we set Retiree Subsidy to 0. In Database value is getting save as 'NULL'.
Because of this Employee is not satisfy the Eligibility of sub rate.
But for other values of Retiree Subsidy are saved properly in DB.

Rate Details :

To solve this issue, Retiree Subsidy is must be save as 0 in database then employee will get Rate: '2017 Retiree Health 0' . accordingly cost gets display on Confirmation page.

Let me know if you need more details on this.

Thanks & Regards,
Vinanti

CC : Jyoti Mayne, Amruta Lohiya, Jaideep Vinchurkar, Satya, Yashau MacShate

Hi Vinanti Yadav,

We have executed the scripts on the Main(Town of Cary) company as well as on the HSPL company.

Please find the below 3C's,

Concern : Town of Cary- Rate issue (PROD)

Cause : Condition was not handled in the code

Correction : Handled the condition in the code

Impacted Areas: System forms

Affected files: dbo.CheckIfAdditionalListBoxOptionsContainsZero.sql
dbo.OES_SP_UpdateEmployeeAttribute.StoredProcedure.sql

Please check at your end and update the JIRA accordingly.

Thanks and Regards,
Jyotibala P.

CC: Satya, Swapnil Pandhare, Sheetal Bodhale, Amruta Lohiya

Hi Yashau MacShate,

We have corrected mentioned employee : Bobbye Hunter.
Now Employee gets correct rate.

also scan all employee to check same issue for them but we did not found any employee.
Please check at your end.

Thanks,
Vinanti

CC : Jyoti Mayne, Amruta Lohiya, Jyotibala Pardeshi, Jaideep Vinchurkar, Swapnil Pandhare, Satya

Dev - will we need to make any changes to the form or should this be fixed going forward?

Jenni

Hi Jennifer Johnson,

No need to make any changes to the form. We already corrected reported employee and fixed the issue.

We will move this fix on Stage on 10/09 and on Production on 10/11.

Thanks,
Hrishikesh.

Environment: LB
Company: For QA Asml for Hspl
Login: Partner and Employee

The issue is checked for:
1. Adding Zero in drop down
2. If added through backend, the value stored is not NULL (verified through backend)

For effect of 0 on Rate and cost will verify on Stage, as LB we don't have company. As this customization cannot be performed as this component is not available.

Screen capture for the same is attached with jira. As mentioned scenario worked as expected, moving jira on Stage.

Hrishikesh Deshpande Jyotibala PardeshiRakesh Roy

Hi Jennifer Johnson,

We will move this JIRA on Stage tomorrow 10/10 on Stage.

Thanks,
Hrishikesh.

Environment: Stage
Company: Town of Cary for Hspl
Login: partner

Unable to get the correct Employee cost for below scenario.

• Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0
• Demographic page > change Retiree Subsidy > 55(or any value in drop down) > Save
• Enroll Now Page > Cost is displayed as expected.

Means for the default value zero cost is not changing, later after demographics change it is displayed as expected.

So, re-opening the jira on Stage.

As mentioned, this scenario was not tested on LB, because in newer component 0 value couldn't be saved.

Hrishikesh Deshpande

Hi Priya Dhamande,

Please find below comments,

• Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0 (System behavior)
• If we set default value as 0 in form builder > page field configuration, then > Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = Rate value

If you set a default value as 0 then employee will get rates, but if you didn't set any default value, then it won't calculate the rate, this is System Behavior (as default constraint is not set)

Kindly check with default value condition once and update JIRA accordingly.

Thanks and Regards,
Jyotibala P.

CC: Satya, Swapnil Pandhare, Sheetal Bodhale

By mistaken changed status

Environment: Stage
Company: Town of Cary for Hspl
Login: Partner

Now, 0 value is not saving as null in DB and hence cost is displayed as expected.

But as mentioned in above comment, the issue of default value as 0 didn't display correct cost still exists. This issue is also existing on other companies and client has reported the same.

As null issue is resolved so moving jira on production and separate jira is created for the issue with ID: WT-11872.

Jyotibala Pardeshi Hrishikesh Deshpande Rashmita Dudhe Rakesh Roy

Yashau MacShate This is deployed on production, please verify and confirm.