-
Type:
Bug
-
Status: Closed
-
Priority:
Low
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:QA
-
Bug Type:Functional
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
Replication steps:
1)Login with Partner
2)Search and select company
3)Go to import/Export -> Template management
4)Create template for dependent
5)Selected Dependent effective date as unique -> Import fail
Please refer attached screen shot and error log :
Hi Ankur Deshpande,
Verified on Lb
company - City of Durham
Verified Effective date validation message scenario for following import :
1)Employee import - Pass (Shows validation for unique effective date)
2)Spouse import - Pass (Shows validation for unique effective date)
3)Child import - Pass (Shows validation for unique effective date)
4)Salary - Pass (Shows validation for unique effective date)
5)Election import - Pass(Effective date is by default unique)
6)Paycheck import - (Effective date is by default unique)
7)Emergency contact import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)
8)Beneficiary import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)
As 7th and 8th scenario is not working fine, Re-opening this jira
Thanks,
Jayshree
Jayshree Nagpure (Inactive)
added a comment - Hi Ankur Deshpande ,
Verified on Lb
company - City of Durham
Verified Effective date validation message scenario for following import :
1)Employee import - Pass (Shows validation for unique effective date)
2)Spouse import - Pass (Shows validation for unique effective date)
3)Child import - Pass (Shows validation for unique effective date)
4)Salary - Pass (Shows validation for unique effective date)
5)Election import - Pass(Effective date is by default unique)
6)Paycheck import - (Effective date is by default unique)
7)Emergency contact import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)
8)Beneficiary import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)
As 7th and 8th scenario is not working fine, Re-opening this jira
Thanks,
Jayshree
CC : Rakesh Roy Prasad Pise Jaideep Vinchurkar
Verified on LB
company - City of Durham
Verified below effective date uniqueness validation scenario :
1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. The field cannot be mapped as it is marked as unique error message is show.
2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the user defined field as unique. The field cannot be marked as unique validation message is shown .
Verified Effective date validation message scenario for following import - Working Fine
1)Employee import - Pass (Shows validation for unique effective date)
2)Spouse import - Pass (Shows validation for unique effective date)
3)Child import - Pass (Shows validation for unique effective date)
4)Salary - Pass (Shows validation for unique effective date)
5)Election import - Pass(Effective date is by default unique)
6)Paycheck import - (Effective date is by default unique)
7)Emergency contact import - Pass (Shows validation for unique effective date)
8)Beneficiary import - Pass (Shows validation for unique effective date)
Marking item state as Ready for stage.
Thanks,
Jayshree
CC : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - Verified on LB
company - City of Durham
Verified below effective date uniqueness validation scenario :
1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. The field cannot be mapped as it is marked as unique error message is show.
2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the user defined field as unique. The field cannot be marked as unique validation message is shown .
Verified Effective date validation message scenario for following import - Working Fine
1)Employee import - Pass (Shows validation for unique effective date)
2)Spouse import - Pass (Shows validation for unique effective date)
3)Child import - Pass (Shows validation for unique effective date)
4)Salary - Pass (Shows validation for unique effective date)
5)Election import - Pass(Effective date is by default unique)
6)Paycheck import - (Effective date is by default unique)
7)Emergency contact import - Pass (Shows validation for unique effective date)
8)Beneficiary import - Pass (Shows validation for unique effective date)
Marking item state as Ready for stage.
Thanks,
Jayshree
CC : Rakesh Roy Prasad Pise Verified on stage all above scenario
Company - Caiso for hspl
Working fine
Marking item state as Ready for production
Thanks,
Jayshree
Jayshree Nagpure (Inactive)
added a comment - Verified on stage all above scenario
Company - Caiso for hspl
Working fine
Marking item state as Ready for production
Thanks,
Jayshree verified on production
working fine
Jayshree Nagpure (Inactive)
added a comment - verified on production
working fine 
Hi Ankur Deshpande,
Verified this issue on LB.
Company - City of Durham
Verified for scenario
1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. the field is mapped and save
Verified spouse import - import Fail
Error log :
ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ListOutDuplicates
ErrorMessage: No column name was specified for column 2 of 'Temp'.
For another scenario :
2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the spouse effective date field as unique.system shows proper validation message "Spouse effective date cannot be unique"
As first scenario is not working hence re-opening this jira
Thanks,
Jayshree
CC : Rakesh Roy Prasad Pise Suraj Sokasane