Hi Rashmita Dudhe,

We need to test:

1. Demographic Import
2. Salary Import
3. Election Import

for both types: Syn and Async.
Also cross verify the email flags at various levels: Company level, Email Message format, Import screen.

CC- Ankur Deshpande, Jaideep Vinchurkar

attached Testcases

Hi Ankur Deshpande,

CC:Jaideep Vinchurkar,Suraj Sokasane,Hrishikesh Deshpande,Rakesh Roy

Verified this enhancement on LB Environment.
Eligibility Routine Is getting Failed Refer below error Log:
ErrorID : 0
ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->ExecuteImportDTS.GetImportExportTemplateInformationBackEndRoutine
ErrorMessage: Object reference not set to an instance of an object.

Thanks,
Rashmita

Hi,

Verified this enhancement on LB Environment.
But Mails are not getting triggered.

Thanks,
Jayshree

CC: Jaideep Vinchurkar Suraj Sokasane Prasad Pise Rakesh Roy Rashmita Dudhe

Hi,

As discussed with Suraj and Prasad, Emails configurations are not available on LB environment.
Thus we will verify it on stage environment.
Hence updating the item state as ready for stage.

Thanks,
Jayshree

CC: Rashmita Dudhe Prasad Pise Rakesh Roy Jaideep Vinchurkar

Hi,

While Testing on stage Emails are getting configured with mention mail id, But they are not getting triggered in back end Routine.

Thanks,
Jayshree

CC; Jaideep Vinchurkar Suraj Sokasane Prasad Pise Rakesh Roy

Hi Ankur Deshpande

As Per Discussed with Suraj Sokasane Back End Routine mails are not getting trigerred.
So Re-Opening On Stage.

Thanks,
Jayshree

CC: Suraj Sokasane Jaideep Vinchurkar Rashmita Dudhe Prasad Pise Rakesh Roy

Hi,

As discussed with Ankur Deshpande Emails configurations are not available on LB environment.
Thus we will verify it on stage environment.
Hence updating the item state as ready for stage.

Thanks,
Jayshree

CC; Jaideep Vinchurkar Suraj Sokasane Prasad Pise Rakesh Roy

Hi Ankur Deshpande

As Discussed with Suraj Sokasane Back End Routine mails are not getting trigerred.
So Re-Opening On Stage.

Thanks,
Jayshree

CC: Suraj Sokasane Prasad Pise Rakesh Roy

HI Jayshree Nagpure
The issue was with the code. I have checked in the code. I tested it on stage with the file that you gave me, mails are getting fired. Please verify.

CC: Suraj Sokasane, Jaideep Vinchurkar Prasad Pise

Regards,
Ankur

Hi,

Verified this Enhancement on Stage.
Mails are getting trigerred as expected.
We have tested for:
Demographic Import
Salary Import
Election Import
for both types: Syn and Async.
Also cross verified the email flags at various levels: Company level, Email Message format, Import screen.
Issue is fixed.
Thus Updating it as Ready for Production.

Thanks,
Jayshree

CC: Ankur Deshpande Suraj Sokasane Rashmita Dudhe Jaideep Vinchurkar

Hi Ankur Deshpande and Jayshree Nagpure,

I have tried a salary import template on Austin for HSPL on production. I receive below email from manual import screen as well as view bad file screen.

This email is not enough descriptive. we do not know exact status of back end routines execution. Whether the routines are succeeded or failed.
This functionality should be tested from automated import as well.

Please work on sending actual result of routine execution status.

Hi Jayshree Nagpure

I have made the change. Also, I have tested for employee demographics import for Sync and Async. Please verify the changes on LB.

Regards,
Ankur

Hi Ankur Deshpande,

Verified this Enhancement on LB on Wheaton Fransican Healthcare company
Mails are getting trigerred as expected and are enough descriptive.
We have tested for:
Demographic Import
Salary Import
Election Import
for both types: Syn and Async.
Also cross verified the email flags at various levels: Company level, Email Message format, Import screen.
Issue is fixed.
Thus Updating it as Ready for Stage.

Thanks,
Jayshree

CC: Jaideep Vinchurkar Prasad Pise Rakesh Roy

Someone has stopped SMTP on stage. I have activated it. Its working fine. Please test.
You have to try automated import on stage. use austin for HSPL for automated import

Hi Ankur Deshpande,

Verified this Enhancement on Stage for Austin for HSPL.
Verified below scenarios:
1)Demographics import
2)Election import
3)Salary import
for sync and async
For Manual import mails are getting trigerred.
Also tried for Automated import on stage for Austin for Hspl for salary import, But mails are not getting trigerred as expected.
Hence as discussed with Jaideep Vinchurkar, Re-opening this on Stage.

Thanks,
Jayshree

CC: Jaideep Vinchurkar Suraj Sokasane Rakesh Roy Prasad Pise

Hi Ankur Deshpande,

we have verified on stage for automated import for Austin for Hspl.
Mails of automated import are getting trigerred as expected.
As discussed with prasad, I have verified for below scenario:
Emp import
Salary import

Thanks,
Jayshree

CC: Jaideep Vinchurkar Rakesh Roy Prasad Pise Suraj Sokasane

We will deploy this on production in next week.

Hi Ankur Deshpande,

I have verified on Production for Austin for HSPL.
Mails are getting trigerred for Manual import and Automated import.
Verified for Demographics import, Election import, Salary import.
But the back end routine email is not enough descriptive. we do not know exact status of back end routines execution. Whether the routines are succeeded or failed.
Hence As discussed with Jaideep Vinchurkar and Prasad Pise Re-opening on Production.

Thanks,
Jayshree

CC: Prasad Pise Jaideep Vinchurkar Rakesh Roy Suraj Sokasane

Missing script is deployed on production. Please test

Hi Ankur Deshpande,

Verified enhancement on Production for Austin for hspl
Verified for Demographics import,Election import,Salary import.
For sync and async.
Mails are getting trigerred for manual import as well as automated import.
And the back end routine mails are enough descriptive.
Working as Expected.
Thus updating item state as Production complete.

Thanks,
Jayshree

CC: Jaideep Vinchurkar Prasad Pise Rakesh Roy Suraj Sokasane