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

Bundle overdue fines into a single notice (“Multiples”) when charging: At check-in

    XMLWordPrintable

Details

    • Poppy (R2 2023)
    • Out of scope
    • 100%
    • Large < 10 days
    • 80%
    • Vega
    • 0
    • R4
    • TBD

    Description

      Current situation or problem:

      • Overdue fines are generated according to the settings in the overdue fine policy (i.e. patron is billed/charged a calculated amount, at the timepoint when the overdue item is checked in).
      • The patron notice policy contains two triggers ("Overdue fine, returned" and "Overdue fine, renewed") to send a notice when the patron is charged overdue fines.
      • Currently, a SINGLE notice is sent out for every SINGLE overdue fine.
      • The aim of this feature = Send MULTIPLE overdue fines in a SINGLE notice.
      • The bundling happens at the check-in END SESSION (whether by clicking on the button, or by the session running out) ; using the same logic as for the check-out/-in multiples.

      In scope

      • BE: Bundle mutliple overdue fines into one single notice: CIRC-1726
      • BE: Closed overdue fines are not included in bundled notices: CIRC-1736

      Out of scope:

      • New notice tokens
      • Changes to the notice template 
      • Changes to the notice policy

       

      Questions

      TestRail: Results

        Attachments

          Issue Links

            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-904 FE: Add new multiples token: "Multiple fee/fine charges" for the Fee/Fine Charge section

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1726 BE: Bundle mutliple overdue fines into one single notice

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1736 BE: Closed overdue fines are not included in bundled notices

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-421 Add sessionId to patron action session and scheduled notice

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-385 Add sessionId field to check-in request body JSON

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            split from

            New Feature - New feature requests UXPROD-2252 Multiple fee/fine charges or actions (pay, waive, transfer, error or refund) on a single notice for a patron

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

            Page Loading...

            Activity

              People

                JulieBickle_LMU Julie Bickle
                JulieBickle_LMU Julie Bickle
                Dmitriy Litvinenko Dmitriy Litvinenko
                Alexander Kurash Alexander Kurash
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases