Uploaded image for project: 'mod-inventory'
  1. mod-inventory
  2. MODINV-296

Field mappings: Item - Item status handling logic

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Folijet Sprint 98, Folijet Sprint 99
    • Story Points:
      8
    • Development Team:
      Folijet
    • Release:
      Q3 2020

      Description

      Purpose: To refine the logic applied when setting the item status during item record creation or update

      As a staff person working with field mapping profiles
      I want different things to happen depending on existing and new item statuses and whether the item record is being created or updated
      So that I do not accidentally assign or re-assign inappropriate statuses

      Scenarios

      1. Scenario 1
        • Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
        • When the action is Create item
        • And the item status is in the dropdown list in the item record field mapping screen
        • Then create the item record with the mapped item status
      2. Scenario 2
        • Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
        • When the action is Update item
        • And the item record's existing item status is one of the following
          • Available
          • In process
          • In transit
          • Missing
          • On order
          • Order closed
          • Withdrawn
        • Then update the item record's status (and update the other fields in the item record according to the item field mapping profile)
      3. Scenario 3
        • Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
        • When the action is Update item
        • And the item record's existing item status is one of the following
          • Aged to lost
          • Awaiting delivery
          • Awaiting pickup
          • Checked out
          • Claimed returned
          • Declared lost
          • Paged
        • Then do not update the item record's status (but update the other fields in the item record according to the item field mapping profile)
        • And return an exception for that item record to the Data Import log: Could not change item status from [existing status] to [field mapping status]
        • Add an error message to the context and put error message to the journal

      NOTES:

      • Further handling for Available status moved to MODINV-339 to unblock this story
      • When status Recently returned (UXPROD-527) is added to the Inventory item record, it should also be disallowed being updated by the incoming status; see MODINV-337
      • When status Long missing (UXPROD-2177) is added to the Inventory item record, it should be allowed for Creates (scenario 1) and updates (scenario 2); see MODINV-338 and UIDATIMP-641

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ruslan_lavrov Ruslan Lavrov
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases