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

Pre-Check Request Policy When Requests are Created and/or Moved

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
      UXPROD features
    • Potential Workaround:
      Cate Boerema: Requests is functional as-is. This is a nice-to-have enhancement that would save a step.
    • Epic Link:
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      Assumes the introduction of a new API for providing which request types are allowed using the whitelist and the circulation rules / request policy, based upon the user and item.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      62
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • PO Rank:
      21
    • PO Ranking Note:
      Hide
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
      2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
      Show
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now. 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R2
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: FLO (MVP Sum 2020):
      R2
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R2
    • Rank: hbz (TBD):
      R2
    • Rank: Hungary (MVP End 2020):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      When creating a request, FOLIO looks at the status of the item being requested and offers only the request types allowed per the whitelist. When the user clicks "create request", however, they may find that their request is still not allowed because of a request policy that has been applied. In this case, the user will see a popup letting them know that, for example, "A hold request is not allowed for this requester and item combination".

      The purpose of this feature is to change the design so that the user doesn't need to click "New request" in order to find out that the request is not allowed. Instead, FOLIO will look at the selected item and requester, run them through the white list and the loan rules and then present only those request types that are allowed for that combination.

      Per discussion with Marc Johnson, the same work needed to enable the above described functionality would also enable us to check the request policies and only show items to which a request can be moved in the move-request workflow (see UXPROD-1653). Without this functionality, when moving a request, you will be presented with all other copies/items in the instance and you will only find the move is not allowed after you select one.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                brookstravis Brooks Travis
                Reporter:
                cboerema Cate Boerema
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases