-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Module:BenAdmin - Export
-
Reported by:Support
-
Item State:Production QA - In Testing
-
Sprint:Bugs - In Progress
Concern: Election Change Reason field not exporting reason at time enrollment when its pending for approval
Cause: Election Change Reason is export reason according current enrollment mode and qualifying event.
Correction: We have implemented new below macro to achive this.
1) Enrollment Election Change Reason Of Review Pending:
This field will export reason when enrollment done if its pending for approval, other wise it will work like
(Election Change Reason) exporting reason according to current enrollment.
2) Enrollment Qualifying Event Date of Review Pending:
1) If enrollment is new hire then it will export Employment Date.
2) if enrollment is Re-hire Enrollment and employee status is also rehire, then it will export Rehire Date
3) if enrollment is done using Qualifying Event then event date will export
4) if enrollment done with review change approval mode then it will export date of history according to above scenario
- relates to
-
-
- Closed
-
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Satya [ ID10004 ] | Rakesh Shahane [ rakesh.shahane ] |
| Summary | Change Reason And Date Time For Election MOved to stored Proc | Change Reason And Date Time For Election Moved to stored Proc |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Issue Type | Enhancement [ 4 ] | Bug [ 1 ] |
| Status | New Request [ 10029 ] | Open [ 1 ] |
| Workflow | WT_Features [ 16600 ] | WT_Defects [ 16705 ] |
| Dev Due Date | 23/May/2016 |
| Priority | Medium [ 3 ] | High [ 2 ] |
| Production Due Date | 26/May/2016 | |
| QA Due Date | 24/May/2016 | |
| Stage Due Date | 25/May/16 [ 2016-05-25 ] |
| Status | Open [ 1 ] | In Development [ 10007 ] |
| Assignee | Rakesh Shahane [ rakesh.shahane ] | Rohan Khandave [ rohan.khandave ] |
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
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: On Hold(10207) |
| Assignee | Rohan Khandave [ rohan.khandave ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
| Developer | Ganesh Sadawarte [ ganesh.sadawarte ] | |
| Item State | Parent values: Development(10200)Level 1 values: On Hold(10207) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| QA | Aniruddha Dev [ aniruddha.dev ] |
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.
| Priority | High [ 2 ] | Highest [ 1 ] |
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.
| Dev Due Date | 23/May/2016 | 27/May/2016 |
| QA Due Date | 24/May/2016 | 01/Jun/2016 |
| QA Due Date | 01/Jun/2016 | 31/May/2016 |
| Stage Due Date | 25/May/16 [ 2016-05-25 ] | 1/Jun/16 [ 2016-06-01 ] |
| Production Due Date | 26/May/2016 | 02/Jun/2016 |
| Sprint | Bugs - In Progress [ 17 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: Ready for Review(10208) |
Affected Files
- App/BusinessLogic/CollectionManager/CollectionManager.vb
- App/BusinessLogic/Employee/ImportExportSettings.vb
- App/BusinessLogic/ImportExportDTS/CommonExportRoutines.vb
- App/BusinessLogic/ImportExportDTS/ExportConstants.vb
- App/BusinessLogic/ImportExportDTS/ExportProcess.vb
- App/BusinessLogic/ImportExportDTS/ExportProcessRowwise.vb
- App/BusinessLogic/ImportExportDTS/ExportProcessXML.vb
- DatabaseObjects/MasterCompanyDB/04_StoredProcedures/
OES_SP_Export_GetChangeReasonAndDateTimeForElection.sql - DatabaseObjects/MasterCompanyDB/07_Data/
19_WT2490_WTB_Export_NewData_Fields.sql - Database Objects/OnlineEnrollment/07_Data/15_WT2490_WTB_Export_NewData_Fields.sql
Code Review: Rohan K
| Description |
*Concern*: Election Change Reason field not exporting reason at time enrollment when its pending for approval *Cause*: Election Change Reason is export reason according current enrollment mode and qualifying event. *Correction*: We have implemented new below macro to achive this. 1) Enrollment Election Change Reason Of Review Pending: This field will export reason when enrollment done if its pending for approval, other wise it will work like (Election Change Reason) exporting reason according to current enrollment. 2) Enrollment Qualifying Event Date of Review Pending: 1) If enrollment is new hire then it will export Employment Date. 2) if enrollment is Re-hire Enrollment and employee status is also rehire, then it will export Rehire Date 3) if enrollment is done using Qualifying Event then event data will export 4) if enrollment done with review change approval mode then it will export date of history according to above scenario |
| Code Reviewed By | Rohan Khandave [ 11903 ] | |
| Environment | Production [ 10005 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Item State | Parent values: Development(10200)Level 1 values: Ready for Review(10208) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Aniruddha Dev [ aniruddha.dev ] |
Verified on LB on ASML Temp Company on Rowise Template .
Testing is in progress with Column wise and ANSI 834 Template.
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
| Description |
*Concern*: Election Change Reason field not exporting reason at time enrollment when its pending for approval *Cause*: Election Change Reason is export reason according current enrollment mode and qualifying event. *Correction*: We have implemented new below macro to achive this. 1) Enrollment Election Change Reason Of Review Pending: This field will export reason when enrollment done if its pending for approval, other wise it will work like (Election Change Reason) exporting reason according to current enrollment. 2) Enrollment Qualifying Event Date of Review Pending: 1) If enrollment is new hire then it will export Employment Date. 2) if enrollment is Re-hire Enrollment and employee status is also rehire, then it will export Rehire Date 3) if enrollment is done using Qualifying Event then event data will export 4) if enrollment done with review change approval mode then it will export date of history according to above scenario |
*Concern*: Election Change Reason field not exporting reason at time enrollment when its pending for approval *Cause*: Election Change Reason is export reason according current enrollment mode and qualifying event. *Correction*: We have implemented new below macro to achive this. 1) Enrollment Election Change Reason Of Review Pending: This field will export reason when enrollment done if its pending for approval, other wise it will work like (Election Change Reason) exporting reason according to current enrollment. 2) Enrollment Qualifying Event Date of Review Pending: 1) If enrollment is new hire then it will export Employment Date. 2) if enrollment is Re-hire Enrollment and employee status is also rehire, then it will export Rehire Date 3) if enrollment is done using Qualifying Event then event date will export 4) if enrollment done with review change approval mode then it will export date of history according to above scenario |
| Comment |
[ Hi, Verified the scenarios attached in for Rowise and Column wise Templates and observed a doubtful scenario for #9 as below 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. ] |
| Attachment | WT-2490 Scenario.xls [ 18833 ] |
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
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
| Status | Local Testing [ 10200 ] | Reopen in Local [ 10018 ] |
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Re-open(10212) |
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
| Status | Reopen in Local [ 10018 ] | In Development [ 10007 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Aniruddha Dev [ 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
| Item State | Parent values: LB QA(10201)Level 1 values: Re-open(10212) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
| Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
| Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
| Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
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
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
| Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
| Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production QA(10203)Level 1 values: In Testing(10218) |
Verified on Production on UND for HSPL company on 'OE Illusions Banner Payroll' file by mapping below fields.
1) Enrollment Election Change Reason of Review Pending
2) Enrollment Qualifying Event Date of Review Pending
Working fine on Production.
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
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
| Assignee | Aniruddha Dev [ aniruddha.dev ] | sam lindberg [ sam.lindberg@ebsbenefits.com ] |
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'
Hi Aniruddha Dev, could you please confirm on Damion M Velasquez's query above?
| Assignee | sam lindberg [ sam.lindberg@ebsbenefits.com ] | Aniruddha Dev [ aniruddha.dev ] |
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
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Damion Velasquez [ damion.velasquez ] |
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
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
| Assignee | Damion Velasquez [ damion.velasquez ] | Aniruddha Dev [ aniruddha.dev ] |
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Damion Velasquez [ damion.velasquez ] |
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
| Environment_New | Production [ 18442 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
2d 3h 46m | 1 |
|
1d 1h 25m | 1 |
|
3d 23h 40m | 1 |
|
1d 1h 28m | 1 |
|
6d 22h 38m | 2 |
|
19h 5m | 1 |
|
22h 13m | 1 |
|
5h 30m | 1 |
|
4d 5h 48m | 1 |
Is there anyway to get it in for tomorrow?
Thank you,
Sam