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

Future Fees/Fines: Refactor manual patron blocks

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Development Team:
      None
    • Calculated Total Rank:
      5
    • PO Rank:
      0
    • Rank: MO State (MVP June 2020):
      R2

      Description

      While working on MODPATBLK-60 (now UIU-1942) the Vega team discovered that much of the manual patron block business logic taking place in the front-end should be in the back-end (as was discovered with the fee/fine 'actions' earlier).

      Here is the comment left by the dev on MODPATBLK-60 (now UIU-1942)...
      Expired manual blocks are being cleared by frontend (not backend!). And it only happens when you input blocked patron's barcode on checkout screen or request creation screen. They are not cleared during renewal. Until you do that, the expired block will live and be visible as banner and icon on user details page as described in MODPATBLK-58. We can follow the same approach and let frontend clear (or just hide) expired blocks the moment User Details page is being opened, but ideally this logic should be moved to backend. And as you already know by our recent mod-feesfines refactoring, this process is not quick and easy.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                hollyolepm Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases