Uploaded image for project: 'ui-checkin'
  1. ui-checkin
  2. UICHKIN-109

Route for delivery check in modal + delivery slip

    XMLWordPrintable

Details

    • eHoldings Sprint 75, eHoldings Sprint 76, eHoldings Sprint 77
    • 5
    • Spitfire

    Description

      Purpose: To create a check in modal to display when an item is checked in and needs to be routed for delivery (see UIREQ-302) and to print the delivery slip that has been configured

      User stories:

      • As a circ desk worker who is checking in an item that needs to be routed for delivery to requester's delivery address
      • I want a check in modal to display in FOLIO
      • So I know I need to do something special with this item (e.g. put in a special bin or shelf)
      • As a circ desk worker who is checking in an item that needs to be routed for delivery to requester's delivery address
      • I want a delivery slip to be printed when I check in an item for delivery
      • So I can slip it in the item to ensure people know where and to whom it must be delivered
      • As a circ desk worker who is checking in an item that needs to be routed for delivery to requester's delivery address
      • I want to be directed to immediately check out the item
      • So I can check it out to the requester (assuming there are no blocks or other issues preventing checkout)

      Scenarios:

      1. Scenario
        • Given the Route for delivery check in modal is generated (see UIREQ-302 for business logic)
        • When displayed
        • Then:
          • Generic "Route for delivery" modal should display with
            • Title of modal: Route for delivery request
            • Body of modal: There is a delivery request for <title of item> (<material type of item>) (Barcode: <barcode of item>). Please check the item out and route for delivery
            • Controls:
              • Print slip - Checkbox (default controlled by Print by default on the service point (Settings > Tenant > Service points > Print by default > Request delivery)
              • Close - Button
              • Close and check out - Button
              • X on window for closing (same as Close)
      2. Scenario
        • Given the print slip checkbox is checked
        • When route for delivery modal is closed via the "Close" button
        • Then the Request delivery print slip should be generated, populating with the text and tokens as specified in Settings > Circulation > Staff slips > Request delivery CB: Please test all tokens (especially the new ones defined in UICIRC-319) are populating properly NOTE: The requester.country token is not populating but I will create a separate bug for that because I think that's backend work: CIRC-566
      3. Scenario
        • Given the print slip checkbox is checked
        • When route for delivery modal is closed via the X in the upper left of the modal
        • Then the Request delivery print slip should NOT be generated
      4. Scenario CB: Moved to UICHKIN-142 since there were remaining issues and sprint was near end (per request from MaksymDryha)
        • Given the modal is displaying
        • When closed using the Close and check out button
        • Then the Check out app will be opened and auto populated with the requester as patron and the item CB: Item is only populated the first time you do this. If checkout is blocked for some reason and you try again, the item data doesn't populated the second time. Screencast attached. If this is really difficult to fix, let's file a separate bug for it.
          • All relevant popups and messaging should display such as:
            • Check out notes
            • Patron borrowing blocks
            • Check out disallowed due to loan policy with Loanable = N
            • Checkout disallowed due to patron expired

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                MaksymDryha Maksym Dryha
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases