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

Ability to update item record with Barcode

    XMLWordPrintable

Details

    • Very Small (VS) < 1day
    • Small < 3 days
    • Low
    • Small < 3 days
    • will depend on Inventories ability to accommodate our requests.
    • Thunderjet
    • R2
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      Purpose: When receiving a physical item the system will prompt you to imput the Barcode and attach that to its corresponding item record in inventory.

      High-Level Requirements:
      GET barcode data from inventory record
      display barcode field in receiving screen for each item record
      POST update to barcode data from value input in receiving screen

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-170 Receiving: Access the Piece Details Wizard and update receiving workflow

            • 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. UIOR-171 Piece Details Wizard: Final review in modal and click receive

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

            New Feature - New feature requests UXPROD-187 Receive Item and update details regarding availability

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

            Umbrella - FOLIO-1273 Define and describe the architecture for seamless push and pull of data between apps (interaction)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Open

            Umbrella - FOLIO-1331 Define and describe the architecture for how to keep data in sync across multiple apps

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Open

            Umbrella - FOLIO-1756 Define and describe the architecture for how to keep data in sync across multiple apps for partial record updates

            • 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. MODORDERS-160 Receiving history: item barcode, location and status

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

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases