Verified below mentioned scenario ,earlier it was not working
Scenario #3
customisation : OE + Qualifying Event
Company name : For QA JE Dunn For HSPL
OE start date :08/31/2017 End Date : 10/18/2017
Date of Employment : 01/01/2017
raised qualifying events (multiple times for back date )as below :

1. Add Dependent who is loosing coverage : 10/13/17

2. Add Dependent who is loosing coverage : 10/14/17

3. Add Dependent who is loosing coverage : 10/15/17

Reflected effective date : 10/13/17

Which is working as expected.

CC- Rakesh Roy Sachin Hingole Hrishikesh Deshpande

Thanks,

Rutuja

Hi Rutuja Chilwar,

Please find the below comments:

Scenario 1:
Customization: QE + QE
Date of Employment: 11/06/2017

Raised 2 qualifying events:
1. Birth or adoption: 10/10/2017
2. Admin changes: 10/20/2017

On demographics page, as per system behaviour, we have shown lesser effective date, in this case(10/10/2017)
If we change any data on demographics, then it will save with lesser effective date with proper qualifying event id in Employee_History table.
In Employee table it will save data with higher effective date(in this case 10/20/2017)

Scenario 2:
Customization: OE + QE
Date of Employment: 11/07/2017

OE Dates: 08/31/2017 to 11/06/2017
OE Effective date: 01/01/2018

If we change any data on demographics then it will save the data with lesser effective date and
enrollment id(in this case with QE)

Note: This is system behavior, we are showing the lesser effective date on the demographics page, if we change any data then data will get save with lesser effective date with enrollment ID in employee_History table, but in Employee table it will save data with higher effective date.

Thanks and Regards,
Jyotibala P.

CC: Satya, Swapnil Pandhare, Sheetal Bodhale

Hello Swapnil Pandhare
Verified below mentioned scenario ,earlier it was not working
Scenario #3
customisation : OE + Qualifying Event
Company name : For QA JE Dunn For HSPL
OE start date :08/31/2017 End Date : 10/18/2017
Date of Employment : 01/01/2017
raised qualifying events as below :

1. Marriage domestic partner registration : 09/012017
2. Losing coverage in Job loss : 09/02/2017

When we traverse QE mode for Losing coverage in Job loss : 09/02/2017 Event ,
09/01/2017 is reflecting as Effective date

Please find attached screenshots :

CC- Rakesh Roy Sachin Hingole Hrishikesh Deshpande

Thanks,
Rutuja

HI Rutuja Chilwar,

My changes related Mode id not effective date
I checked customisation : OE + Qualifying Event , system will show lesser effective date and
I also checked from back end Mode ID is correct .So Please check it once again

Thanks,
Akshay Mukkawar
-----------------------------
CC:Sheetal Bodhale,Satya

Hello Sheetal Bodhale ,

Verified above mentioned point for following scenarios :
Scenario #1
customization : OE

1. Add new Employee
OE start date : 09/01/2017 End Date : 09/302017
date of Employment : 01/012017
Effective date : 01/01/2018
Status :PASS

Scenario #2
customization : OE + New hire mode
2. Add new Employee
OE start date : 09/01/2017 End Date : 09/302017
Date of Employment : 09/26/2017
Effective date :09/26/2017
Status : Pass

Scenario #3
customization : OE + Qualifying Event
OE start date : 09/01/2017 End Date : 09/302017
Date of Employment : 01/012017
raise multiple qualifying events ,
lesser effective date is not reflecting .
Status : FAILED

Scenario #4
customization : OE + New hire mode , Set required verification Yes for new hire mode
Add new Employee
OE start date : 09/01/2017 End Date : 09/302017
Date of Employment : 09/26/2017
Effective date :09/26/2017
data going for approval for new hire mode
Status: PASS

3rd scenario is getting failed

CC - Rakesh Roy Sachin Hingole Hrishikesh Deshpande

Hi Rutuja Chilwar,

Please consider following scenarios too:

1)Get Employee with any two modes. And effective date of one mode should be lesser than other mode.
Then system will show lesser effective date on employee forms.That is correct.
But while saving data, it is saving data with wrong mode.We have fixed this.For that you need to check from back end.Please refer below tables,
select EnrollMentModeID, from Employee
select * from EnrollmentMode
*
2)Set requires verification to 'yes' for mode with greater effective date.It should not pend the data of
lesser effective date mode as for the mode verification is 'No'

Please let me know any additional details are required.

CC:Swapnil EksambekarSatyaAkshay MukkawarGaurav Sodani

Thanks,
Sheetal Bodhale

Please find following 3C's:
Concern: Employee data gets saved with wrong mode when multiple modes going on
Cause: Code was wrong when multiple modes
Correction: We have modify Sp for this.

*Impacted Areas: *
Employee login

Files Affected
1) .OES_SP_GetEmployeeEffectiveDate

Please consider following scenarios for Impact Testing:

1) Single mode for Employee login
2) Multiple modes for Employee login

Thanks,
Akshay Mukkawar
--------------------------
CC:Swapnil Pandhare,Sheetal Bodhale,Satya

Hi Akshay Mukkawar,

Please check scenario with and with out requires verification.

Thanks,
Sheetal Bodhale

CC:SatyaGaurav SodaniSwapnil Pandhare