-
Type:
Enhancement
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - EDS
-
Reported by:White Label
-
Company:Utah Valley University
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
-
Sprint:WT Sprint 18
We need to consider one special character for Dependent SSN. It can be either ^ or ~.
Let UHC know which character will be feasible. This requirement is for ACA files as well. They need to import dependents with special characters as SSN and after proper SSN is submitted all of these would be updated in system.
Note: - 1. Employee SSN (Add Employee, Demographics or through Import )would not be considering this special character.
2. Special character has to be considered on Spouse & child page.
3. It should also be allowed on Beneficiary page.
We need to make sure that all modules in the system works correct with this special character. It would need to implement in Import (demographics and ACA import) as well.
Swapnil Pandhare: Can we please share feasible character with UHC at first.
Nandkumar Prabhakar Karlekar Jaideep Vinchurkar Rakesh Roy Vijay Siddha Samir
Environment: LB
Company: Caiso and MBF
Login: Partner, Company Admin and Employee
The enhancement is verified on LB and it is working as expected. Scenarios covered are updated in above comments. These are checked by changing the rights for Employee and CA login.
For Impact we have checked on: Confirmation Statement PDF, Confirmation statement
Under header Dependents Information, Export and Reports [Dependent Census].
As mentioned scenarios worked well so moving jira on Stage.
Environment: Stage
Company: Wheaton Franciscan Healthcare OE 2017 For HSPL
Login: Partner, Company Admin and Employee
Scenarios Covered:
1. Partner:
- Added Spouse [Spouse, ExSpouse, DP]
- Added Child [Natural, Step, Disabled Child]
- Verified on Confirmation statement Under header Dependents Information - Three dash appeared
- Verified on Confirmation statement PDF - Three dash appeared
- Export - Blank appears in place of *
2. Company Admin:
- Added Spouse [Spouse, ExSpouse, DP]
- Added Child [Natural, Step, Disabled Child]
- Verified on Confirmation statement Under header Dependents Information - Three dash appeared
- Verified on Confirmation statement PDF - Three dash appeared
- Export - Blank appears in place of *
3. Employee [verified by OE and New Hire Mode]
- Spouse [Spouse, ExSpouse, DP]
- Child [Natural, Step, Disabled Child]
- Confirmation statement Under header Dependents Information - Three dash appeared
- Confirmation statement PDF - Three dash appeared
We have checked Export, Report and Confirmation Statement for its Impact. As mentioned scenarios worked as expected moving jira on Production.
Environment: Production
Company: Utah Valley University For HSPL
Login: Partner, Company Admin and Employee
Scenarios Covered:
1. Partner:
Added Spouse [Spouse, ExSpouse, DP]
Added Child [Natural, Step, Disabled Child]
Verified on Confirmation statement Under header Dependents Information - Three dash appeared
Verified on Confirmation statement PDF - Three dash appeared
Export - Blank appears in place of *
2. Company Admin:
Added Spouse [Spouse, ExSpouse, DP]
Added Child [Natural, Step, Disabled Child]
Verified on Confirmation statement Under header Dependents Information - Three dash appeared
Verified on Confirmation statement PDF - Three dash appeared
Export - Blank appears in place of *
3. Employee [verified by OE and New Hire Mode]
Spouse [Spouse, ExSpouse, DP]
Child [Natural, Step, Disabled Child]
Confirmation statement Under header Dependents Information - Three dash appeared
Confirmation statement PDF - Three dash appeared
We have checked Export, Report and Confirmation Statement for its Impact.
Pending:
As WT-6897 patch, Import dependent SSN didn't went to production cannot verify the Import dependent through Ui. So, will able to complete jira once the mentioned jira goes to production and is verified.
verified the import Spouse and Child SSN through UI. Blank appears even if the SSN is inserted as '*' so closing jira on Production.
Jennifer Leugers: Can you pleas confirm from your end and close the jira.
Environment: LB
Company: Caiso and MBF
Login: Partner, Company Admin and Employee
Testing in-progress.
Scenarios Covered Today:
1. Partner:
2. Company Admin:
3. Employee
Pending Scenarios: need to check on Reports for all above scenarios. Willbe completing the reaming scenarios tomorrow and will move jira for Stage.