Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3434

Implement new finance transaction model to protect against parallel processing

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • Nolana (R3 2022)
    • Out of scope
    • Thunderjet
    • 0
    • R2
    • R2

    Description

      Current situation or problem: When 2 users or separate mods run operations in parallel, they can send both summaries before sending the operations. mod-finance-storage is not saving previous summaries with the same id (which in practice is the order id for encumbrances), so one of the summaries sent will have no effect, resulting in an error for the second one:

      "All expected transactions already processed"

      In scope

      Redesign transaction summaries to allow parallel usage. Using unique ids (as opposed to for instance order ids)  could be part of the solution, but we don't want to accumulate too many records in the summary tables, so they would have to be deleted when no longer in use.

       When redesigning, care should be taken to avoid requiring a check for 404 errors, as was done in mod-orders' TransactionSummariesService.java for MODORDERS-545 (normal operations should not report errors in the logs).

      Out of scope

      Use case(s)

      Proposed solution/stories
      Wiki : https://wiki.folio.org/display/DD/Support+for+transaction+processing+by+two+or+more+users+in+parallel

      Links to additional info

      Questions

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3666 Improve support for parallel processing

            • TBD - To be determined
            • In Refinement
            is cloned by

            New Feature - New feature requests UXPROD-3636 Define new transaction model to protect against parallel processing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFIN-214 Option to provide a summary id parameter in the transaction API

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODFISTO-259 Releasing 2 transactions at the same time can fail to update budgets

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-260 Transaction summaries are not designed to be used in parallel

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-266 Create a new model "TempTransaction"

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-267 Update table "order_transaction_summaries"

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-268 Option to provide a summary id parameter in the transaction API

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-314 POC: fix the transaction API

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVOICE-307 Update transaction summary API calls

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-581 Update transaction summary API calls

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases