Files Affected

/*
New Data ( Online & Master)
Get & Save SP ( Online & Master) dbo.OES_Export_SaveEDIToolAction.sql & dbo.OES_SP_Export_GetTemplateListForEDITool.sql
MVC JS
EDITool.cshtml
_PVEDITool.cshtml
EDITool.vb (BL)

*/

Localication

AddRunDateSpecificNote There should not be any Run Date/Time which is greater than below given Run Date/Time on template. Please delete if such Run Date/Time is present.
ChangeFileFullFileChange If template is being updated as Full File then change in election track will be removed from template if mapped. And if template is being updated as Changes Only then change in election track will be added to applicable templates.
CurrentElectionFrom Current Election From
CurrentElectionTo Current Election Upto
UpdatetoFullFile Update to Full File
UpdatetoChangesOnly Update to Changes Only
Doyouwanttoupdate Do you want to update
FullFile Full File
ChangesOnly Changes Only

Started testing on LB on windstream company . Verified UI level Flag flipping for Company Level Template

Testing is in Progress

Verified this Enhancements on LB with attached scenarios and additionally verified below scenarios

1) Columnwise Changes Only to Full File and vice versa
2) Rowise Changes Only to Full File and Vice versa
3) Cross Companies Group Template Full files To Changes only and Vice Versa

Manually Exported for all above scenarios. Working as expected on LB. Ready for stage

Below are Observations and Suggestions

Observation #1 : When Change in Election track is mapped on the changes only through EDI utility and we manually change to Full File . Then Change in Election Track is not removed (Discussed this with Dev Team and confirmed that flags changed to Changes File through EDIUtility should be changed to Full File using EDI utility only)

Suggestion#1 : We are able to unmap Change in Election Track indicator mapped through EDI Utility. When such action is done and file is again changed to Changes Only through Utility. It adds new filed for Change in Election Track . Previous remains Blank as it is . This can affect the structure of the exporting file. So can we please restrict this at field mapping level or at sub template level for such scenario ?

Verified this enhancement on Production as per attached scenarios on both Company level as well as group level.

Working Fine