Page Comparison

rolloverType

enum ["Preview", "Commit", "Rollback"]

Y

• Current scheme for rollover records - add a column/flag to mark every rollover if it is a real or a preview one - this will also keep the history of completed previews

1. Define Storage API : Preview Ledger Rollover → Storage API : Ledger Rollover Budgets
2. Implement API → Should be without any logic.

1. Define and Implement Budgets API → Budgets Ledger Rollover Business API
2. Define and Implement Logs API → Logs view should be built accordingly with ledger_fiscal_year_rollover_log Ledger Rollover Logs Business API

1. Spike : Implement POC with storing preview result in the temporary tables and after that upload results in the preview rollover table

mod-finance-storage

All all open technical questions should be resolved

1. Update ledger rollover SQL script with preview rollover logic and store results in the preview rollover table

Implement Preview rollover flow and update budgets with all calculated amounts

1. Steps should be run in scope of one DB transaction :

1.1 Rollover script run (field LedgerFiscalYearRollover."action" = "Preview")
1.2 Retrieve result of preview from table "ledger_fiscal_year_rollover_budget", where budgets amounts will be partially filled (MODFISTO-323)
1.3. Go through all budgets and calculate remaining amounts → org.folio.utils.CalculationUtils#calculateBudgetSummaryFields
1.4. Storing updated budgets in the rollover preview table → ledger_fiscal_year_rollover_budget

  2. Update delete rollover logic : org.folio.service.rollover.LedgerRolloverService#deleteRollover. Rollover record  deletion should happened together with rollover budgets in scope of one DB transaction

Replace unique index in the table "ledger_fiscal_year_rollover" with uniqueness logic in the code

1. Remove index "ledgerId_fromFiscalYearId" from table "ledger_fiscal_year_rollover"
2. Implement validation logic in the separate validation service:

2.1 If incoming rollover is real with action "Commit", then rollover record should be unique for pair "ledgerId, fromFiscalYearId" (the same as in the index)

2.2 If incoming rollover is real with action "Preview", then rollover record should not be unique for pair "ledgerId, fromFiscalYearId"  and it possible to have many previews for one ledger and same fiscal year.

1. Spike : To gain knowledge about mod-email and implement example with usage email sending

1. Implement sending email and include it in the preview ledger rollover flow