Medium Cottingham & Butler used their SISCO call center to enroll the Lily employees into their Unum benefits (Accident/CI). C&B paid for an administrative seat for each of those SISCO call center reps so we could track which call center rep elected which employee. The call center usernames in WORKTERRA are the same as their username in Unum. Jason (C&B) would like to see a report of which call center reps enrolled which employees. This is critical for their benefit set up. David Rhodes and Steve Allison have asked me to create a JIRA and attach the files which need to be populated.
Waverly from Unum shared exactly what she is looking to receive:
“What we need on the file is the username of the benefit counselor (SISCO call center employee) that enrolled each individual, not their name. We had asked when we set this up to have the usernames for WorkTerra match the usernames for our proprietary enrollment system, as this allows us to check licensure without having to re-request social security numbers for each individual when we get the file.”
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Evan Tuckey [ etuckey ] | Satya [ ID10004 ] |
| Account Executive | Steve Allison [ sallison ] | Evan Tuckey [ etuckey ] |
| Account Executive | Evan Tuckey [ etuckey ] | Kevin Walker [ kwalker ] |
| Link | This issue causes EDI-60 [ EDI-60 ] |
Hi Evan,
I have shared this ticket with development. Looking at the description it seems that currently this is not implemented in Export. It will require enhancement.
Development will share analysis & queries (if any) on this.
Thanks & Regards,
Satya Prakash
| Assignee | Satya [ ID10004 ] | Rohan Khandave [ rohan.khandave ] |
Hi Evan,
As per our understanding , template has below two new fields , which required to expose new fields as there no such fields available on export to achieve this.
1. ENRLR_LOGON_NAME : This field needs to pull user name of user who make new elections / changes into existing elections on behalf of employee (SISCO call center).
Development Query : If employee make elections / changes into existing elections by self then this field will be blank for those elections. Is it fine , or you want employee's user name also? If election change by some services like over age dependent then on file respective service name will export Or you want this field only for some specific users only like Partner,Broker,Company Admin?
2. ENROL_LOGON_TYPE : This fields tell user type who change/add elections, currently it has fixed value as "Call Center – Other".
Development Query : Currently we set fix value as "Call Center – Other". So it will appear for elections which made by employee himself/herself and even for service like overage dependent. Are you fine with this? If not ,and you required this value only when there value into "ENRLR_LOGON_NAME" field and vice versa Or you want this field only for some specific users only? Then to achieve this we need to develop rule engine.
Common Query : You want "User Name" on file which is used for login or actual users first name & last name ?
Kindly please confirm above change will satisfy your requirement or not and please clear our queries ? After your reply we will shared details analysis and ETA.
CC – Satya Kevin Walker
| Assignee | Rohan Khandave [ rohan.khandave ] | Evan Tuckey [ etuckey ] |
| Issue Type | Support Activity [ 10301 ] | Enhancement [ 4 ] |
| Status | Open [ 1 ] | New Request [ 10029 ] |
| Support Task Type | Query Resolution [ 11205 ] | |
| Workflow | WT_Support [ 14517 ] | WT_Features [ 14542 ] |
| Item State | Parent values: Development(10200)Level 1 values: Development Backlog(10205) |
| Dev Estimates | 64 |
| Module | Parent values: BenAdmin(10100)Level 1 values: Report(10109) | Parent values: BenAdmin(10100)Level 1 values: Export(10110) |
| Attachment | Lily_WT1488.zip [ 14524 ] |
Please find updated file with Users Names.
We have randomly verified some records in file and observed that proper users names are proper.
Satya Please share password of attached file with Evan,
While reviewing the spreadsheets, I saw "kmejia" a number of times which was concerning. Kari is a WORKTERRA Implementation Manager and I'm not sure her name should be included. Can the team look into the records that have her name on them? I don't believe those are correct.
| Assignee | Evan Tuckey [ etuckey ] | Hrishikesh Deshpande [ hrishikesh.deshpande ] |
Hi Evan,
There are many enrollments done by Kari's Partner ID and those are valid enrollments.
I am not sure whether Kari got request from client to do those enrollments or not .
As of now enrollments are proper but I can not tell whether client really need those enrollments or not.
Let me know if you need any information from my end.
Thanks
Hrishikesh
| Assignee | Hrishikesh Deshpande [ hrishikesh.deshpande ] | Evan Tuckey [ etuckey ] |
Hi Hrishikesh,
I believe we are good now. The team is looking into the one-off names and we believe it's resolved. Thank you for your help, you can close this ticket at this time.
Best,
Evan
Hi Evan,
Development has provided file with username from backend. Please let us know if this will be further required?
If it is required through export on regular basis, we will need to do enhancement in Export functionality. Request you to please go through development queries (added in this ticket itself on 24th march ) and provide help us with your replies on this.
Thanks & Regards,
Satya Prakash
| Fix Version/s | 1.0 [ 10000 ] |
| Component/s | BenAdmin [ 10000 ] |
| QA Estimates | 16 |
| Sprint | WT Sprint 1 [ 6 ] |
| Rank | Ranked higher |
| Status | New Request [ 10029 ] | Pending for Approval [ 10002 ] |
| Status | Pending for Approval [ 10002 ] | Approved for Development [ 10003 ] |
| Item State | Parent values: Development(10200)Level 1 values: Development Backlog(10205) | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
| Assignee | Evan Tuckey [ etuckey ] | Rajendra Pawar [ rajendra.pawar ] |
| Developer | Rajendra Pawar [ rajendra.pawar ] |
| Status | Approved for Development [ 10003 ] | In Development [ 10007 ] |
| Dev Due Date | 21/Apr/2016 |
This ticket should now be closed, I believe it's been completed for a number of weeks now.
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Attachment | WT-1488- Expose Enroller Details Implementation.doc [ 15592 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: On Hold(10207) |
| Item State | Parent values: Development(10200)Level 1 values: On Hold(10207) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
Changing Dev Due Date to 26/Apr/16. Because priority was changed for enhancement(WT-1871).
| Dev Due Date | 21/Apr/2016 | 26/Apr/2016 |
| Rank | Ranked lower |
| Sprint | WT Sprint 1 [ 6 ] | WT Sprint 2 [ 7 ] |
| Rank | Ranked higher |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: Ready for Review(10208) |
| Attachment | WT-1488.ods [ 16159 ] |
| Attachment |
|
| Attachment | WT-1488.ods [ 16162 ] |
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
Online DB changes
4_WT1488_WTB_Export_NewData_Fields
MasterDB DB changes
UDF – OES_UDF_Export_EnrollerDetails
SP – OES_SP_Export_GetEnrollerDetails
6_WT1488_WTB_Export_NewData_Fields
36_WT1488_WTB_Export_NewTable_Export_TempEnrollerDetails
| Item State | Parent values: Development(10200)Level 1 values: Ready for Review(10208) | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) |
| Item State | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) | Parent values: LB QA(10201) |
| Item State | Parent values: LB QA(10201) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Assignee | Rajendra Pawar [ rajendra.pawar ] | Aniruddha Dev [ aniruddha.dev ] |
This Enhancement is working as expected on LB.
Field Name : "Enroller user Name"
Verified that Export will pull user Name of Enroller and export on file on mapping of This filed.
Verified for Payroll Template, Employee Template, Row wise and Column wise feeds.
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
| Production Due Date | 28/Apr/2016 | |
| QA | Hrishikesh Deshpande [ hrishikesh.deshpande ] | |
| QA Due Date | 26/Apr/2016 | |
| Stage Due Date | 27/Apr/16 [ 2016-04-27 ] |
| Status | Local Testing [ 10200 ] | Pending for Stage Approval [ 10300 ] |
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Hrishikesh Deshpande [ hrishikesh.deshpande ] |
| Status | Pending for Stage Approval [ 10300 ] | Approved for Stage [ 10030 ] |
| 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) |
| Status | Approved for Stage [ 10030 ] | Stage Testing [ 10201 ] |
This is working well on Stage. Ready for Production.
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
| Status | Stage Testing [ 10201 ] | Pending for Production Approval [ 10301 ] |
| Status | Pending for Production Approval [ 10301 ] | Approved for production [ 10034 ] |
| Status | Approved for production [ 10034 ] | Production Testing [ 10202 ] |
| 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) |
Hi Kevin/Evan,
This Enhancement is Deployed and working as expected on Production.
We have exposed 4 new fields, Please see below :
1) "Enrollment Enroller User Name" - This filed will pull User ID of enroller.
2)* "Enrollment Enroller User Role" *- This filed will pull User Role like Admin, Partner of enroller.
3) "Enrollment Enroller User First Name" - This filed will pull First Name of enroller.
4) "Enrollment Enroller User Last Name" - This filed will pull Last Name of enroller.
Note : Lily Feeds has requirement only for Enroller User Name. We have exposed other fields for future use.
We have mapped Enroller User Name field on below Lily feeds.
Lily_Payroll_CriticalIllness
Lily_Payroll_Accident.
Please let us know in case of any questions on this.
Thanks,
Hrishikesh.
| Assignee | Hrishikesh Deshpande [ hrishikesh.deshpande ] | Kevin Walker [ kwalker ] |
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
| Link | This issue relates to DEV-9156 [ DEV-9156 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
16h 23m | 1 |
|
18d 20h 22m | 1 |
|
3s | 1 |
|
9m 35s | 1 |
|
14d 18m | 1 |
|
1h 58m | 1 |
|
8d 22h 40m | 1 |
|
21s | 1 |
|
1h 45m | 1 |
|
21h 50m | 1 |
|
2s | 1 |
|
1h | 1 |
Dave asked me to assign it to you. Thanks Satya.