Satya
Hi Sachin Hingole

Can you please check if this error is getting reproduced on all additional forms ?

Thanks,
Swapnil P.

Hi Rajendra Joshi,

Can you please check this JIRA.

Thanks,
Sachin Hingole

Assigning this to Kunal.

CC: Sachin HingoleRakesh RoyRajendra Joshi

Hi Swapnil Pandhare,

We have verified this error by adding a new hire on "LONG" company on Stage. The issue is reproducible for all additional forms while traversing the tour. Please refer below screenshot and error log for same.

Steps:
1] Login as a new hire.
2] Traverse the Onboarding tour.
3] Server error is displaying for every page (except Emergency Contact).

Cc: Rajendra Joshi, Sachin Hingole, Hrishikesh Deshpande, Prasad Pise

ErrorLog.txt

Hi Kunal Kedari

Please check this as discussed.

Thanks,
Swapnil P.

Hi Swapnil Pandhare,

Verified the issues for BenAdmin, error is not displaying while saving same froms. Please refer attached screenshot for same.

Cc: Sachin Hingole, Hrishikesh Deshpande, Prasad Pise

When New Hire waiting period is 30 then it is not getting proper Effective Date mode to save details. It does not save additional form data and throws server error.
When we set New Hire Waiting Period to 0 then it gets Effective Date mode directly and it works properly.
Observation:
We can set New Hire Waiting Period to 0 and apply Is New Hire criteria to Specific forms as Discussed with satya.

Cc: Swapnil Pandhare

Veronica Blanco Please refer the above comments and settings. Let us know if you still face any issue related to on boarding. Thanks!

CC: Vijay Siddha shyam sharma Swapnil Pandhare

Hi Sonali Punse

We have another solution also. We can add Employee and Set Employment Date as more than 30 days in past.
Example: If today's date : 01/16/2017
then, Employment Date should : 12/15/2017 or less.

Cc; Swapnil Pandhare
Thanks,
Niteen S.

Hi Sonali Punse,

I am aware that when the BenAdmin waiting period is 0 there is not error, however, there is still a problem with all waiting periods. Unfortunately, manipulating the data to avoid the error is not going to be acceptable solution.

Thank you,
Veronica

cc: Vijay Siddha shyam sharma Swapnil Pandhare Amannda Johnson

Swapnil Pandhare Could you please check if you can provide fixes to this error?

CC: shyam sharma Vijay Siddha

Hi Sonali Punse

As of now, this is handled through customization . If we want to change current implementation, it will be a bit big change which cannot be accommodated now due to other priority task.
We might take this to fix later .

Thanks,
Swapnil P.

Sonali PunseVeronica Blanco Please create a change request for this and after Dave's approval will take this change as per its priority.

I will update this ticket to a change request.

Duplicate with WT-8002. Hence closing this. Keeping WT-8002 open.

This is a bug that is NOT RESOLVED. There was a new feature request that was created for the same issue - which was not the right process. That request NF-221 is now marked as DUPLICATE and can be left alone. This one needs to be fixed. This need not require Dave's approval as this is NOT AN ENHANCEMENT REQUEST.

CC shyam sharma Mandar Kulkarni Chitra Rao Veronica Blanco Swapnil Pandhare Nagini Indugula Amannda Johnson

Abhay Patil : Yes I agree with you but as this is a support ticket (WT-7723), so as per defined process we can not make code changes in any support ticket. so in order to fix this issue we have created NF-221. Team will work on NF-221 to address this issue and once this get fixed then only we will close Parent ticket WT-7723 and NF-221. by that time WT-7723 will remain open.

Swapnil Pandhare : Please fix this issue in ticket NF-221 and once this get deployed on Production, please close both the tickets WT-7723 and NF-221 at the same time.

I hope this is fine

CC : Mandar Kulkarni,Chitra Rao,Bharti Satpute,Nagini Indugula
–
Regards,
Shyam

Thanks shyam sharma - this is perfect.

Swapnil Pandhare : please look into this support ticket.

Hi Abhay Patil,
Shall we close this one for now?

---------------------------------------------------------------------
CC: Vijay Siddha, Satya, Swapnil Pandhare

Mandar Kulkarni - as discussed before, once NF-221 is closed, this could be closed.

Swapnil Pandhare - I think we can close this ticket as it relates to onboarding.

This is about Onboarding - so not relevant anymore.

As we are not working on onboard anymore, closing this JIRA.