WR-67 : WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved

Hi Prasad Pise,

Please find below 3C's:

Concern: WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved
Cause: Code was not present to store Employer Match Up,Employee Cost fields for transit.
Correction: We have fixed code for this.

Impact Testing:
Test FSA and Transit enroll now screens

Cc: Jyoti Mayne, Alankar Chavan

This is tested on WT Stage - Working Well

All the mentioned fields are getting saved

Actual and assumed expected behavior for these fields are -

Employer Match Up = 50 %
Show Employer Coverage = Yes

say employee puts amount on enroll now screen as 130
EE cost = 130 / 26 (pay cycle) = 5
ER Coverage = 65 (130/2)
ER Cost = 65 / 26 (pay cycle) = 2.5

This is ready for Stage

Jyoti Mayne - can you please review mentioned behavior of the system and confirm the same ? Please let us know, if you find any discrepancy in above mentioned scenario

CC - Sachin Hingole Hrishikesh Deshpande Rakesh Roy Prasad Pise

Environment: Stage
Company: Asml for Hspl
Login: Partner and Employee
Plan: Transit

Issue: Employer Match Up and Employee Cost fields not getting saved.

The issue of Employer Match Up and Employee Cost fields not getting saved is verified and is able t save the fields as added

Impact:
Added values in fields as:
Employer Match Up: 70
Employee Cost fields: 20

Employee Login > Enroll Now > Transit Plan

EE Cost: 70/Employee remaining paycycle = 70/12 = 5.83

As above calculation worked as expected and able to Save the fields, moving jira on Prodution.

Environment: LB
Company: Asml for Hspl
Login: Partner and Employee
Plan: Transit

Issue: Employer Match Up and Employee Cost fields not getting saved.

The issue of Employer Match Up and Employee Cost fields not getting saved is verified on LB and is able to save the fields as added.

Impact:
checked Employee login with its cost.

So, moving jira on Stage.

Environment: Stage
Company: Asml for hspl
Login: Partner and Employee
Plan Type: Transit

The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting properly saved. also, able to verify corresponding changes with Employee login after enrolling the plan.

So, moving jira on production.

Environment: Production
Company: Asml for hspl
Login: Partner and Employee
Plan Type: Transit

The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting saved is resolved on Production. Verified the same on mentioned company. So, closing jira on production.