Scenarios:
Toggle : System Settings >> Allow Changes without Qualifying Event (For Demographics, Child, Spouse and Emergency)
Unit Testing required through SA/P/CA/EE Login

Today's Date - 02/15/2018 and Mode - 31 Days

Employee is Eligible with demographics criteria:

Employee is not Eligible with demographics criteria:

ETAs and Pages to make NH changes:

CC: Swapnil Pandhare Satya

Analysis:

WT-13231 Issue :
Shows server error on Change Status page because OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION return NULL value as Hire Date/Employment Date. And this issue occurred due to WT-10837 changes.

Scenario :
If Today's Date - 02/13/2018
Employment Date - 20/02/2018
Effective Date - 20/02/2018

Then OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION
return NULL DB value and Exception thrown at Business Logic cause NULL result not handled at BL.

WT-10837 Issue :
If we set future Hire Date/Employment Date then it allow employees to use New Hire mode to make changes which should not do.

Scenario:
If we'll revert WT-10837 changes from OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION
then it'll return Hire Date as Effective Date and WT-13231 will works as expected
BUT, as we reverted WT-10837, then issue of Future New Hire remain exists.

Enroll Now : If it is the case of Future New Hire it does not check either employee is eligible for Demographics Criteria or Not
Workflow : Future Effective Date returns and starts work-flow. Not checked either Employee is eligible or not.
Demographics criteria not checked in dbo.OES_SP_Get_EnrollmentModesForEmployee.StoredProcedure (if reverted WT-10837)

Temporary Solution : We can handle DB NULL value exception at BL.
We have to fix Employee's Future New Hire mode from Enroll Now screen and Workflow screen.

We'll share the ETAs after discussion in design meeting.

Thanks,
Niteen

We are analyzing the WT-10837 and WT-13231 as well to avoid contradiction to each other.
We need to either re-fix WT- 10837 or fix WT- 13231 such way that it'll not contradict other one.

SP : dbo.OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION.StoredProcedure

CC: Swapnil Pandhare

We have started Analysis on this issue, This issue is caused by WT-10837 ticket fix. So, first we'll do analysis on WT-10837 and we'll share the ETA.

CC: Swapnil Pandhare