Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Problem(s):
- User must navigate to inventory to place a request on newly ordered items. This requires additional permissions and breaking up the acquisitions workflow or risking that items are requested before a hold can be place for the desired user.
- Title level requests will automatically pull an item that is created by the orders app.Fiscal year rollover can not be "undone"
- Fiscal year rollover errors can be complex and difficult, if even possible to correct
Use Cases & Requirements:
Requirement | Status | Use cases | |||||||
---|---|---|---|---|---|---|---|---|---|
Automatically create a request for the on-order material so that it can't be taken by someone else. Prevent Title level request queue from picking up this item.Allow user to generate a rollover report that will tell the user what errors may occur if rolling over with current data |
|
| Allow requests to be created for a general user. Possibly system user or a specified generic user account (Requests require a user ID so we can not allow free text when generating request)
| ||||||
Allow user to run a rollover "preview" that will show a user the result of rolling over with existing settings |
|
|
Proposed workflow:
| ||||||||
Allow user to run rollover "Test" more than once if desired |
|
| ||||||
Allow user to easily obtain an export of the current years data during rollover process |
|
|
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? |
| Only one user at the same time. The 2nd user should see a warning/notification message | |||||||||||
Does one need to keep a history of all rollover preview runs? If yes, how long? |
| Async operation - once started, the preview rollover will be executed on back-end, and the result will be available in history Rollover setting is to be stored as well together with the results in order to enable/simplify further analysis 1 year is the max period for storing All the data are stored in DB, and CSV can be generated via UI (as it's currently used in Acquisition app) The question about the scope form Mikita One of the option is not to have the history on UI but just provide an ability to download the file for the most recent rollover preview How does the user user the preview is done? - E.g., by email Try 2 options and estimates them | |||||||||||
Does one need to support rollover preview not only for finances, but also for transactions and orders? |
| Unpaid invoices - it's just a prerequisite for preview In fact, it's required to test the logic of budget_encumbrances_rollover.sql | |||||||||||
Need to map all the columns in Export file example (see Miro board) with data available in mod- finance |
| All the mentioned data is required in final export file. | 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)
| ||||||||||
Report with Unpaid invoices should be generated for Ledger or include all Unpaid invoice? |
| All | |||||||||||
Dennis Bridges Can we provide in the email just link on Folio page with export downloading link? |
| Provide link to FOLIO page | |||||||||||
Dennis Bridges Do we need to show Ledger Rollover Preview progress as for Rollover? |
| Just show Status "In progress" or "Complete" |
Proposed Implementation Details:
Preview Ledger Fiscal Year Rollover#SolutionDesign
Work Breakdown Structure:
Features:
UI Stories
MOD Stories
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|