Versions Compared

Version Old Version 10 New Version 11
Changes made by

Raman Auramau

Andrei Makaranka

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2899

Problem(s):

  1. Fiscal year rollover can not be "undone"
  2. Fiscal year rollover errors can be complex and difficult, if even possible to correct

Use Cases & Requirements:

RequirementStatusUse cases

Allow user to generate a rollover report that will tell the user what errors may occur if rolling over with current data

Status
colourGreen
titleVERIFIED

  • In preparation for rollover the library will run a report to catch any errors that may occur so they can be dealt with before the rollover is officially executed.
Allow user to run a rollover "preview" that will show a user the result of rolling over with existing settings

Status
colourGreen
titleVERIFIED

  • In preparation for rollover the library will run a report to catch any errors that may occur on account of the rollover settings that are being used, so they can be adjusted before the current fiscal year ends.
Allow user to run rollover "Test" more than once if desired

Status
colourGreen
titleVerified

  • Library will always test rollover to make sure there are no surprises. Rollover may be tested more than once.
Allow user to easily obtain an export of the current years data during rollover process

Status
colourGreen
titleVerified

  • When rolling over the system should provide a copy of the closing years budgets (Current state at end of year). This is used  as a reference to help verify the results of the rollover


Proposed workflow:



Functionality Potentially Impacted by Changes:

Functional area

Records

Potential impact

Suggested Regression Testing




Questions:

Question

Status

Conclusion

Comments

Can 2 or more users run rollover preview at the same time? What behavior is expected?

Status
colourBlue
titleopen



Does one need to keep a history of all rollover preview runs? If yes, how long?

Status
colourBlue
titleopen



Does one need to support rollover preview not only for finances, but also for transactions and orders?

Status
colourBlue
titleopen



Need to map all the columns in Export file example (see Miro board) with data available in mod- finance

Status
colourBlue
titleopen


I have done some mapping of the columns with fields of Budget record (see https://github.com/folio-org/acq-models/blob/13072225f182e5d88a8811aabcfd55bb497e78aa/mod-finance/schemas/budget.json)

  1. Mapped fields are marked with (plus)
  2. Some of the fields, though mapped, are readonly in the schema; this means that the data in the fields is calculated in real time; they are marked with (warning)
  3. Some of the fields remained unmapped




Proposed Implementation Details:

  • 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
  • mod-finance-storage-master\src\main\resources\templates\db_scripts\budget_encumbrances_rollover.sql - make this script parameterizable; pass a real/preview flag as the input parameter; use different tables depending on the flag value. This will allow not to duplicate the SQL script, but to use the same script for both the real rollover and the preview, and thereby get the correct results for the preview.
    • Add another table to store preview data, including Export budget and errors that have occurred; data from this table can then be exported to any convenient format or displayed on the UI

    Preview Ledger Fiscal Year Rollover#SolutionDesign

    Work Breakdown Structure:

    Features:


    UI Stories


    MOD Stories

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET))
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc