Aggregate values incorrect after date change

[exalate-issue-sync]

This ticket encompassed two issues that arise when hanging the date of an existing transaction that is included in the aggregates of another to a date after that future transaction.

1. (Trigger bug) it will result in incorrect aggregates for both the transaction that was once but no longer after it because we do not trigger a recalculation of past transactions.

2)(onscreen aggregate preview bug)The previous transaction that is sent to the front end for figuring out the aggregate preview will include the transaction itself in the aggregate (transaction b’s aggregate includes a’s value still)

After fixing this we will be able to move transaction A after transaction B and both aggregates will be correct.

Additionally the preview for A’s aggregate in the form where we change it’s date will be correct (it will not include itself in B’s aggregate)

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-2087

[exalate-issue-sync]

Elaine Krauss commented: There is a fix ready for the aggregate preview in the transaction form ready [here|https://github.com/fecgov/fecfile-web-api/pull/1380], but it will wait until the rest of this ticket is satisfied.