Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-569

Implement logic for updating Item fields when Piece was changed

    XMLWordPrintable

Details

    • Thunderjet/Firebird Back-end Story Template
    • ACQ Sprint 132, ACQ Sprint 133
    • 3
    • Thunderjet
    • Lotus R1 2022

    Description

      Purpose/Overview:
      Item fields need to be updated (displayOnHolding, enumeration, chronology, discoverySuppress) when Piece was changed.

      Requirements/Scope:

      1. Updated fields (displayOnHolding, enumeration, chronology, discoverySuppress) from Piece should be reflected in the Item

      Approach:
      1. Update Item by calling inventory using REST call : org.folio.service.pieces.PieceService#updatePieceRecord

      1.1. Create new class org.folio.service.pieces.PieceUpdateFlowManager (contains all business logic for updating piece), if it not created before.
      1.2. Create holder for storing intermediate data, which will be used in the async future flow), if it not created before. Example org.folio.models.pieces.PieceCreationHolder
      1.3. Add logic to update fields (displayOnHolding, enumeration, chronology, discoverySuppress) from Piece should be reflected in the Item

      Acceptance criteria:

      • Update Piece logic implemented
      • Unit tests
      • API tests

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3342 Implement data consistency approach for Piece<>Item interaction

            • P2 - normal priority level, must be included in the current development cycle
            • In Refinement
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREC-148 Data consistency - Update Item when piece Enumeration and Chronology are updated

            • 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. UIREC-225 Data consistency - Update Piece when Item Enumeration and Chronology are updated

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-304 Implement logic for updating Piece fields when Item was changed

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

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-649 Some fields of the piece are not populated when receiving/unreceiving

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

            Bug - A problem which impairs or prevents the functions of the product. UIREC-220 Some fields of the piece are not populated when receiving/unreceiving

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

            Page Loading...

            Activity

              People

                artsem_churakou Artsem Churakou
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases