As per Dave/Amit email this task is dropped from sprint 10 as team needs to work on followings in the current sprint 10
• (ST-193) Prime Split - Alvarado Hospital Medical Center
• (ST-195) Prime Split - Harlingen Medical Center
• (ST-196) Prime Split - Monroe Hospital
• (ST-197) Prime Split - Pampa Regional Medical Center
• (ST-198) Prime Split - Hospitality
Now We will pick up WT-3095 in sprint 11

Due to below task changing dev due date

1) WT-4500: Wheaton - Deduction File
2) Production build

Affected Files:

1)Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_Export_SaveEDIToolAction.sql
2)DatabaseObjects/MasterCompanyDB/04_StoredProcedures/
dbo.OES_SP_Export_GetTemplateListForEDITool.sql
3)Database Objects/MasterCompanyDB/07_Data/108_WT-3095_WTB_Export_NewData_ExportEDIToolActions.sql
4)Database Objects/OnlineEnrollment/04_Stored Procedures/dbo.OES_Export_SaveEDIToolAction.sql
5)Database Objects/OnlineEnrollment/04_StoredProcedures/dbo.OES_SP_Export_GetTemplateListForEDITool.sql
6)Database Objects/OnlineEnrollment/07_Data/68_WT-3095_WTB_Export_NewData_ExportEDIToolActions.sql
7)Database Objects/OnlineEnrollment/07_Data/70_WT-3095_WTB_Export_NewData_PageLevelAccess.sql

8)Shared Library/SharedFunction/SharedFunction/WORKTERRASharedFunction.cs
9)Shared Library/WORKTERRALocalization/WORKTERRALocalization

10)App/BusinessLogic/ImportExportDTS/EDITool.vb
11)App/ControllerAppTier/ControllerAppTier/WORKTERRAControllerAppTier.cs

12)Web/Web Projects/WORKTERRA/Areas/Customization/Controllers/EDI/EDIToolController.cs
13)Web/Web Projects/WORKTERRA/Areas/Customization/Models/EDI/PVEDIToolModel.cs

15)Web/Web Projects/WORKTERRA/Areas/Customization/Views/Customization/EDI/_PVEDITool.cshtml
16)Web/Web Projects/WORKTERRA/Areas/Customization/Views/Customization/EDI/EDITool.cshtml

17)Web/Web Projects/WORKTERRA/Scripts/ImportExportTemplateManagement_MVC.js
18)Web/Web Projects/WORKTERRA/Scripts/WORKTERRAShared.js

Ganesh Sadawarte : please sync the status of this ticket I mean Item state : LB QA - LB Deployed and Main status
Rohan J Khandave

Hi shyam sharma,

LB Deployed was update by deployment engineer and main status of local testing will we update by QA.
We are just assigning JIRA to the respective QA after patch deployment.

Rohan J Khandave,Satya

Thanks,
Ganesh

Getting server error on EDI utility -> select Company -> Select new Plan selection .

error log :
ErrorID : 0
ErrorSource : ControllerAppTier.GetData->WORKTERRAControllerAppTier.GetData
ErrorMessage: Object reference not set to an instance of an object.

Hi Hrishikesh Deshpande,

LB patch deployment was going on when you are verifying this change due to this its error occurred. Please check now it working properly.

Thanks,
Ganesh

The Test Cases and Scenario document is attached with the jira. Please find the attachment for the same.

The enhancement is tested for basic scenarios and Test cases. The tested scenarios and Test cases worked as expected. Testing is in progress for further scenarios.

The enhancement of EDI Utility - New Plan Selection is tested on JambaJuice on LB. The scenarios covered during testing are:

1. All Template having same Benefit Type mapped should appear in list
2. Template having new Plan already selected should not appear
3. All templates checked marked should have new plan selected.
4. Class Status Eligibility of Plan should be in sync with Template
5. The Template listed should have same benfit provider as selected on template else Template should not be listed.

As all the scenarios worked as expected, moving the jira on Stage.

The enhancement of EDI Utility - New Plan Selection is tested on LHP for HSPL.
Scenarios covered during testing are:

1. Checked for Benefit Type
2. Checked if Plan already selected
3. Checked for Class Status Eligibility of Plan in sync with Template
4. Checked for same Benefit Type and different Benefit Provider and Vice versa

As all the scenarios worked as expected, moving the jira on Production.

The enhancement of EDI Utility - New Plan Selection is tested on Wheaton Franciscan Healthcareon company on Production.

Scenarios covered during testing are:
1. All Template having same Benefit Type mapped should appear in list
2. Template having new Plan already selected should not appear
3. All templates checked marked should have new plan selected.
4. Class Status Eligibility of Plan should be in sync with Template
5. The Template listed should have same benfit provider as selected on template else Template should not be listed.

As all the scenarios worked as expected, so closing the jira on Production.