-
Type:
Change Request
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Import
-
Reported by:Support
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 37 - Enhancement
-
Severity:Simple
Following is the scenario as of now.
- New hire is added, say with new hire date as 3/14.
- An health enrollment is uploaded on 3/14.
- The new hire rule specifies that new hire becomes eligible on 1st of next month,
- System figures that based on the new hire rule, effective date for this benefit needs to be 4/1. But on file it is 3/14. System successfully imports the file and sets the effective date of the enrollment as 4/1.
The requirement is that the enrollment should be rejected and should show up in the bad file with the reason that the effective date doesn't follow the system rules.
Cindy Wibbing - please edit the description if necessary.
CC Samir Amit Thorve
- is blocked by
-
WT-11154 Import/Export template management -> Server Error on Stage
-
- Production Complete
-
Concern: Import is successful even if enrollment effective date do not follow new hire rules.
Cause: There are two dates, enrollment effective date(given in file) and new hire effective date. System was considering greater date amongst these two dates. So, if date given in file is less than new hire effective date, system was considering new hire effective date as enrollment effective date and hence import was getting successful. Records were getting added into Enrollment_Intermidiate table.
Correction: Added a check for date given in file. If it doesn't follow new hire rules then that record will get showed up in bad file. There won't be any changes in database for such enrollments.
Snehal Katkar (Inactive)
added a comment - Concern: Import is successful even if enrollment effective date do not follow new hire rules.
Cause: There are two dates, enrollment effective date(given in file) and new hire effective date. System was considering greater date amongst these two dates. So, if date given in file is less than new hire effective date, system was considering new hire effective date as enrollment effective date and hence import was getting successful. Records were getting added into Enrollment_Intermidiate table.
Correction: Added a check for date given in file. If it doesn't follow new hire rules then that record will get showed up in bad file. There won't be any changes in database for such enrollments. Files Having Changes:
1)https://delta.harbinger.in/svn/WT/trunk/WORKTERRAweb/App/BusinessLogic/ImportExportDTS/ImportEmployeeEnrollment.vb
Impacted Areas:
1) Election Import
Scenarios to Check:
1) Consider any date as Enrollment effective date, less than new hire effective date for election import. Bad file should get generate saying, effective date doesn't follow new hire rules.
2) Enter enrollment effective date as per the new hire effective rule. Import should be successful.
Snehal Katkar (Inactive)
added a comment - Files Having Changes:
1) https://delta.harbinger.in/svn/WT/trunk/WORKTERRAweb/App/BusinessLogic/ImportExportDTS/ImportEmployeeEnrollment.vb
Impacted Areas:
1) Election Import
Scenarios to Check:
1) Consider any date as Enrollment effective date, less than new hire effective date for election import. Bad file should get generate saying, effective date doesn't follow new hire rules.
2) Enter enrollment effective date as per the new hire effective rule. Import should be successful. Hi Snehal Katkar,
Verified on LB
Company - Qa City of durham for hspl.
Verified scenario's are below :
1) Consider any date as Enrollment effective date, less than new hire effective date for election import- File kicked out to bad with message "Enrollment effective date cannot set prior to new hire effective date"
2) Enter enrollment effective date as per the new hire effective rule- Import done successfully
Other additional scenario's with all New hire rule's are attached in checklist : UpdatedTestcases.xls
Working fine
Marking item state as Ready for Stage
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - - edited Hi Snehal Katkar ,
Verified on LB
Company - Qa City of durham for hspl.
Verified scenario's are below :
1) Consider any date as Enrollment effective date, less than new hire effective date for election import- File kicked out to bad with message "Enrollment effective date cannot set prior to new hire effective date"
2) Enter enrollment effective date as per the new hire effective rule- Import done successfully
Other additional scenario's with all New hire rule's are attached in checklist : UpdatedTestcases.xls
Working fine
Marking item state as Ready for Stage
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise Verified on Stage
Company - City of bellevue for hspl
Verified all scenario attached in Test cases
Working fine.
Marking item state as Ready for Production
Jayshree Nagpure (Inactive)
added a comment - Verified on Stage
Company - City of bellevue for hspl
Verified all scenario attached in Test cases
Working fine.
Marking item state as Ready for Production Verified on Production
Company - ASML for hspl
Verified all scenario attached in Test cases
Working fine.
Hence marking item state as Production complete
Jayshree Nagpure (Inactive)
added a comment - Verified on Production
Company - ASML for hspl
Verified all scenario attached in Test cases
Working fine.
Hence marking item state as Production complete 
Good to LB Checkin