Is there anyway to get it in for tomorrow?

Thank you,
Sam

Has this been tested fully?

Thank you,
Sam

Damion M Velasquez
Hi Sam,

This ticket is linked to WT-1763 & we are waiting for 1 query from Damion. After getting inputs on this, we will be in a position to proceed further with development.

This is affecting its timelines.
Damion M Velasquez: Can you please update us with option of (generic change or company specific).

Thanks & Regards,
Satya Prakash

Rohan, I dont know if this is my call to make, without seeing the code. Is this just a table being added to the back-end? if so we would anticipate company level. I believe all of the other updates for this QE Code process has been a system wide change.

Please use company level.

Can we move forward?

We answered the questions in the other ticket.. Please move forward now.

Hello Damion M Velasquez,

Thanks for your reply , we have start working on this issue.

We are developing new field(Election Change Reason Of Review Pending) which will will work accordingly "Election Change Reason" along with changes suggested by UND for New Hire.

So please find changed estimation.

Affected Files

1. App/BusinessLogic/CollectionManager/CollectionManager.vb
2. App/BusinessLogic/Employee/ImportExportSettings.vb
3. App/BusinessLogic/ImportExportDTS/CommonExportRoutines.vb
4. App/BusinessLogic/ImportExportDTS/ExportConstants.vb
5. App/BusinessLogic/ImportExportDTS/ExportProcess.vb
6. App/BusinessLogic/ImportExportDTS/ExportProcessRowwise.vb
7. App/BusinessLogic/ImportExportDTS/ExportProcessXML.vb
8. DatabaseObjects/MasterCompanyDB/04_StoredProcedures/
   OES_SP_Export_GetChangeReasonAndDateTimeForElection.sql
9. DatabaseObjects/MasterCompanyDB/07_Data/
   19_WT2490_WTB_Export_NewData_Fields.sql
10. Database Objects/OnlineEnrollment/07_Data/15_WT2490_WTB_Export_NewData_Fields.sql

Code Review: Rohan K

Verified on LB on ASML Temp Company on Rowise Template .

Testing is in progress with Column wise and ANSI 834 Template.

Hi,

Verified the scenarios attached in WT-2490 Scenario.xls for Rowise and Column wise Templates and observed below

1) for Qualifying Event _ Divorce. Where the value getting exported for 'Enrollment Election Change Reason Of Review Pending'
'Employee Data Change' and for 'Enrollment Qualifying Event Date of Review Pending ' is enrollment effective date. Please confirm that is it as per implementation ?

2) Could not check on ANSI 834 as getting server error when both these fields are mapped on ANSI 834 template.
So reopening the JIRA

sam lindberg

Hi Sam,

We've found internal issues in our local testing . We will fix these and deploy it on stage on Friday, 03/06/2016. We'll update you once its deployed .

Regards,
Aniruddha Dev

Hi
All this needs to be done much sooner. Can this fix be deployed to prod by Friday?

My client has been waiting patiently for this code and the deadline has passed.

Thank you,
Sam

sam lindberg
Hi Sam,

Fix got delayed because we've found an internal issue and the fix has been deployed on LB.
We will deploy this fix on stage tomorrow and on Production by Friday 06/03/2016.
We will let you know once deployed on Production.

Regards,
Aniruddha Dev

H Aniruddha Dev,

Please find my comments.

1) for Qualifying Event _ Divorce. Where the value getting exported for 'Enrollment Election Change Reason Of Review Pending'
'Employee Data Change' and for 'Enrollment Qualifying Event Date of Review Pending ' is enrollment effective date. Please confirm that is it as per implementation ?
Yes this is as per impemenation

2) Could not check on ANSI 834 as getting server error when both these fields are mapped on ANSI 834 template.
So reopening the JIRA
- We have fixed this and also deployed on LB

Verified the fix after LB patch for ANSI 834 Template on ASML Temp company.
Working as expected on LB.
Ready for Stage

Verified on Stage on UND for HSPL company with below scenarios

1) New- hire , (Review Changes Approval )
2) Re-hire, (Review Changes Approval)
3) Open Enrollment (Review Changes Approval),
4) QE- Admin Change,
5) Employee Data Change

Working as expected

Ready for Production

Hi Sam,

We have deployed this patch on Production . Can you please verify this at your end and close this JIRA item ?

Please let us know in case of any queries.

Thanks & Regards,
Aniruddha Dev

Aniruddha Dev Was this deployed into the correct Client Site? There are two for this cleint. THe deployment should have occured on 'UND For Banner Payroll Testing'

sam lindberg

Hi Aniruddha Dev, could you please confirm on Damion M Velasquez's query above?

Satya

Hi Damion,

This is a generic change. It has deployed on Production and accessible on all companies including 'UND for Banner Payroll Testing'.

Please check this at your end and Let us know in case of any queries.

Thanks & Regards,
Aniruddha Dev

Hi damion:

Please rerun the payroll and submit any defects.

Also if you need me to create any scenarios please tell me.

Thank you,
Sam

sam lindberg

hello,
in re-running this export we are not seeing the codes for the new hire. (Rosie Test) entered by Steven Cohen. Can you look into this and tell us what needs to be done differently @ the UI Level in order to get a new hire code to pass of '01'? Review change approval shows without the QE verbiage. Was the New HIRE WE not used?

Thank you