Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-211

Make Request Policy Effective At Request Creation

    XMLWordPrintable

Details

    • Core: F - Sprint 59
    • 8
    • Prokopovych

    Description

      Purpose: We have implemented a very simple request policy (UIREQ-181) and we have tied it into circ rules (UICIRC-164). The purpose of this story is to use these elements to determine which types of requests can be made for different requester/item combinations.

      User story:

      • As a user who is trying to create a request for a patron/item combination
      • I want FOLIO to prevent request types that are not allowed according to the applicable request policy
      • Because some types of requests are only allowed for certain patron groups, item types etc.

      Scenarios:

      1. Scenario
        • Given:
          • Request policy A with Recall = Yes AND
          • Circ rule with Patron group = Undergrad, Material type = Any, Loan type = Any
        • When:
          • A recall request is created for John Doe with Patron group = Undergrad AND
          • Recalls are not prevented based on the Whitelist (see UIREQ-209) AND
          • Save is attempted
        • Then request is successfully created
      2. Scenario
        • Given:
          • Request policy A with Recall = No/Unchecked AND
          • Circ rule with Patron group = Undergrad, Material type = Any, Loan type = Any
        • When:
          • A recall request is created for John Doe with Patron group = Undergrad AND
          • Save is attempted
        • Then:
          • Request creation is prevented
          • Modal should display:
            • Header: Request not allowed
            • Body: Recall requests are not allowed for this patron and item combination.
            • Buttons:
              • Close (closes modal and returns user to unsaved request form)
              • X (same behavior as close button)
      3. Scenario
        • Given:
          • Request policy A with Hold = Yes AND
          • Circ rule with Patron group = Any, Material type = Book, Loan type = Any
        • When:
          • A recall request is created for Item X with Material type = Book AND
          • Holds are not prevented based on the Whitelist (see UIREQ-209) AND
          • Save is attempted
        • Then: request is successfully created
      4. Scenario
        • Given:
          • Request policy A with Hold = No/Unchecked AND
          • Circ rule with Patron group = Any, Material type = Book, Loan type = Any
        • When:
          • A recall request is created for Item X with Material type = Book
          • Save is attempted
        • Then:
          • Request creation is prevented
          • Modal should display:
            • Header: Request not allowed
            • Body: Hold requests are not allowed for this patron and item combination.
            • Buttons:
              • Close (closes modal and returns user to unsaved request form)
              • X (same behavior as close button)
      5. Scenario
        • Given:
          • Request policy A with Page = Yes AND
          • Circ rule with Patron group = Any, Material type = Any, Loan type = Non-Circulating
        • When:
          • A recall request is created for Item X with Loan type = Non-Circulating AND
          • Pages are not prevented based on the Whitelist (see UIREQ-209) AND
          • Save is attempted
        • Then: request is successfully created
      6. Scenario
        • Given:
          • Request policy A with Page = No/Unchecked AND
          • Circ rule with Patron group = Any, Material type = Any, Loan type = Non-Circulating
        • When:
          • A recall request is created for Item X with Loan type = Non-Circulating
          • Save is attempted
        • Then:
          • Request creation is prevented
          • Modal should display:
            • Header: Request not allowed
            • Body: Page requests are not allowed for this patron and item combination.
            • Buttons:
              • Close (closes modal and returns user to unsaved request form)
              • X (same behavior as close button)
      7. Scenario
        • Given the Request not allowed modal
        • When closed
        • Then the user should return to the unsaved request form where they can change all aspects of the requests that are normally editable when creating a new request

      NOTE: The above scenarios only cover the very most basic circ rules setups. It would be great if testers could exercise more scenarios to ensure circ rules are working as one might expect.

      Mockups: https://drive.google.com/drive/folders/1qMLWk7RThsy9xUDYQpTHMrw95E-qydYz

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                adityamatukumalli Aditya matukumalli
                cboerema Cate Boerema
                Cate Boerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases