-
Type:
Bug
-
Status: Rejected
-
Priority:
Medium
-
Resolution: System Behaviour
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:Client
-
Company:TIBCO
-
Item State:Development - In Analysis
Hi,
Per the client:
We had some below issues where the state was removed from the spouse record in 2.0. This caused errors on the MetLife file. I was looking into what happened, and it looks like the employee at time of OE, somehow removed the state.
From what I can tell in the View History – the employee updated the information in the beneficiary information – updated the country, and removed the state. Either that they removed the state in the dependent information, and it updated the beneficiary information. The change happened at the exact same time.
Is there a connection between the beneficiary screens and the dependent demographic info?
(please visit View History of EE: Pei Fazhan)
Thank you,
Kira Hamilton
Debbie Kulling
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Satya [ ID10004 ] | Jaideep Vinchurkar [ jaideep.vinchurkar ] |
| Component/s | BenAdmin [ 10000 ] | |
| Developer | Prasanna Karlekar [ prasanna ] | Jaideep Vinchurkar [ jaideep.vinchurkar ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | |
| Module | Parent values: BenAdmin(10100) | Parent values: BenAdmin(10100)Level 1 values: Enrollment(10107) |
| Root Cause | Intended Functionality [ 18446 ] | |
| Remaining Estimate | 2h [ 7200 ] | |
| Original Estimate | 2h [ 7200 ] |
| Status | Open [ 1 ] | In Development [ 10007 ] |
| Assignee | Jaideep Vinchurkar [ jaideep.vinchurkar ] | Kira Hamilton [ kira.hamilton ] |
| Resolution | System Behaviour [ 10100 ] | |
| Status | In Development [ 10007 ] | Rejected [ 10004 ] |
| Remaining Estimate | 2h [ 7200 ] | 1h [ 3600 ] |
| Time Spent | 1h [ 3600 ] | |
| Worklog Id | 93735 [ 93735 ] |
Hi,
Per the client:
I do require some clarification. I completely understand if an employee changes the dependent data in the dependent screen that it would automatically update the beneficiary information. However, if the employee makes a change to beneficiary information, in my opinion, that should NOT automatically update the dependent demographic information. The reason I state this is because there are rules in the system that govern the Dependent Demographic page as to what is required, hidden, editable and what is view only. This functionality does NOT exist at the beneficiary level. Therefore, our inquiry was: was the update made at the BENEFICARY level – which then auto updated the dependent demographic, which should NOT happen, or was it made at the Dependent Demographic level – which then correctly updated the beneficiary information.
Thank you,
Kira Hamilton
Debbie Kulling
| Resolution | System Behaviour [ 10100 ] | Unresolved [ 10200 ] |
| Status | Rejected [ 10004 ] | Reopen [ 4 ] |
Hi Kira Hamilton,
The changes were made on dependent demographic page and then it reflects on Beneficiary information.
PS: If you select dependent (spouse / child) as beneficiary, you are not allowed to make any changes in demographic data from beneficiary screen. You can only select / remove dependent from given options in drop down list.
| Remaining Estimate | 1h [ 3600 ] | 0.5h [ 1800 ] |
| Time Spent | 1h [ 3600 ] | 1.5h [ 5400 ] |
| Worklog Id | 94137 [ 94137 ] |
| Status | Reopen [ 4 ] | In Development [ 10007 ] |
| Resolution | Unresolved [ 10200 ] | System Behaviour [ 10100 ] |
| Status | In Development [ 10007 ] | Rejected [ 10004 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
5h 11m | 1 |
|
18h 15m | 1 |
|
40d 22h 18m | 1 |
|
24s | 2 |
Hi Kira Hamilton,
There is connection between dependent demographic screen and beneficiary screen. If the beneficiary is one of the dependent, when we change dependent data, the changes gets reflect to beneficiary as well.
Since, the employee himself removed state, it can not be a bug, hence rejecting this as of now. Please reopen if you feel any action is needed.