-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: System Behaviour
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Stage
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:Harbinger
-
Item State:Development - In Analysis
-
Sprint:WT Sprint 30 -Bugs
Scenario:-
1] Imported an election with effective date as 07/01/2016 without termination date. This plan election has a rate mapped effective from 07/01/2016 to 12/31/2017.
2] Now import the same election with termination date as 09/30/2016 and observe the ratechanges_log table.
Actual Result:-
Ratechanges_log table is making the entries dead and then inserting the entries with correct terminationdate.
Expected Result:-
Ratechanges_log table should alter the existing entries with correct terminationdate and not make any entries dead.
NOTE:- This works fine if we terminate the election through UI.
Prasanna Karlekar,Jaideep Vinchurkar,Sachin Hingole,Suraj Sokasane,Jyoti Mayne
Please let me know if you need any more information on this.
- relates to
-
WT-7614 Test data for Invoice and Billing Testing company
-
- Resolved
-
This issues is because the way election import designed. Election import can set the termination date to enrollment as it is, but for setting termination date call is given to rate recalculation. Previously we used to delete entries from rate changes log in such cases. However, export team needs all such details for changes in rates, that's why instead of deleting the rate, we are making it dead.
Another issues we found that while terminating enrollment through election import, enrollment also get dead and new enrollment with termination date gets inserted. This is because of
WT-6041.we will consider this issue while working on
WT-9056.