Verified on Production
Company - Barrow for hspl

Verified all scenario of updated test-cases
Working fine,

Marking item state as Production complete.

Thanks,
Jayshree

Verified on Stage
Company - ASML or hspl

Verified all scenario of updated test-cases
Working fine,

Marking item state as Ready for Production

Thanks,
Jayshree

hello Amanulla Mulla,

Verified on LB
Company - QA CAISO

Verified scenarios are attached in Latest updated Test-cases
PFA FinalUpdatedTestcases.xls

All scenarios are working fine

Marking item state as Ready for Stage

Thanks,
Jayshree

cc - Rakesh Roy Hrishikesh Deshpande Prasad Pise Ganesh Sadawarte

Below are 3C's

1.Concern: File wents to bad”Invalid numeric format” For -> To check supervisor ID with alpha numeric
Cause : The data format for supervisor ID in system is numeric and for EMP ID is alpha numeric Thats why it wents to bad file
Correction : We have handled this scenario by changing the data format for Supervisor EmpID at run time through the coding.

2. Concern : successfully imported records not shown in org chart
Cause : even though file went bad the update query was getting generated and replacing the successfully imported records.
Correction : We have done currections so it will not generate the query for bad records and successfully imported records will show in org chart.

Hi Jayshree Nagpure,

Please find below details,

1) Employment information supervisor field mapping is currently not used in import, This field should be removed:
Comments: As of we are not removing this will consider this in import refactoring.

2) File should kicked out to bad”Reuired field should not be blank or ~”:
Comments: This is working as expected for other fields. Please refer below steps how IsRequired filed work.

• If employee adding to system then required marked field must provide value.
• If employee updating and required marked field has value in system but value not provide in file then it import successfully.
• If employee updating and required marked field not has value in system and value not provide in file then it will to go bad file.

3) To check supervisor SSN/ID uniquee
Comments: Suraj Sokasane has already provided details on this. adding same in JIRA.
Dependent Import has Composite key concept for unique fields. A composite key of all unique fields is created and used to check if dependent exist or not.
Import does not support this functionality for Employee. Employee Import only supports uniqueness for either SSN or EmpID. If any other field is marked as unique, Import won't work.

CC-Suraj Sokasane

Thanks,
Ganesh

Hi Amanulla Mulla,

Employment information supervisor field mapping is currently not used in import, This field should be removed

Hello Amanulla Mulla,

Verified this on Lb
Company - QA CAISO

Verified scenario's are attached in test cases
Some scenario's are not working are highlighted in testcases
PFA - UpdatedTestcases.xls

Re-opening this jira

Thanks,
Jayshree

cc - Rakesh Roy Prasad Pise Sachin Hingole Hrishikesh Deshpande Jaideep Vinchurkar Suraj Sokasane Suraj Sokasane Ganesh Sadawarte

Hi Jennifer Reed,

As per our email communication, will go with approach 1 to implement this change.

CC-Suraj Sokasane,Vinayak Kulkarni

Thanks,
Ganesh

Hi Jennifer Reed,

Please find attached Analysis_document.doc analysis document. We have come up with two approaches and we need to decide one of them. Let us know your preferred approach, if you want discuss this we can have call.

CC-Vinayak Kulkarni,Satya,Samir,Gaurav Sodani

Thanks,
Ganesh

Hi Amanulla Mulla,

Attached are the testcase according to analysis doc provided by Suraj Sokasane.
Let me know if any thing needed from my side.
Also while testing if found some scenario's will update accordingly in test cases
Testcases.xls
cc - Hrishikesh Deshpande Prasad Pise Rakesh Roy Sachin Hingole Suraj Sokasane Jaideep Vinchurkar