Uploaded image for project: 'mod-circulation'
  1. mod-circulation
  2. CIRC-719

Improve notice errors due to incorrect reference to or not to multiples on template

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Open (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Template:
    • Development Team:
      Vega

      Description

      Check in notices - expects multiple loans {{#loans}} {{/loans}} on template because these are always intended to be sent bundled with all loans by patron by session on a single notice. If a template does NOT include the multiple loans token, this will cause an error.

      • What happens now? One to a few notices are sent and token values are empty. The number of notices sent does not seem to be related to the number of items checked in. Note: there's a separate issue related to duplicate notices that it might be related to the number of notices sent - UICHKIN-176.
      • Proposed solutions:
        • When policy is being configured and check in is selected as the trigger, is it possible to scan the template, and then alert user if template does not contain multiples reference?
        • Is it possible to send an individual notice for each item checked in but with loan/item token values?

      Check out notices - expects multiple loans {{#loans}} {{/loans}} on template because these are always sent bundled with all loans by patron by session on a single notice. If a template does NOT include the multiple loans token, this will cause an error.

      • What happens now? One notice is sent and token values are empty. I tested this several times and I always seemed to receive one check out notice (upon session end) but it's curious why this is always one and check in seems to be always be more than one. If more than one notice is ever received, then it might be related to UICHKOUT-607.
      • Proposed solutions:
        • When policy is being configured and check out is selected as the trigger, is it possible to scan the template, and then alert user if template does not contain multiples reference?
        • Is it possible to send an individual notice for each item checked out but with loan/item token values?

      Notices triggered by due date/time (before, upon/at or after) is trickier. Templates without and with multiple loans are both acceptable; however, multiples only works with those notices not sent in "real time" (misleading term, but there's another story to fix this).

      • If a template includes the multiple loans token and real time is checked, this will cause an error.
        • What happens now? Notices are still sent (appears to be one for each item?); however, anything contained within the multiples loop are empty/blank (both labels and token values).
        • Proposed solutions:
          • Scenario 4 on UICIRC-454 should help to eliminate some misaligned configurations b/n templates and policies.
          • If there is still a misaligned configuration, is it possible to send a notice for each item in "real time" with token values. So basically, it only loops once.
      • If a template does NOT include the multiple loans token and real time is UNchecked, this will also cause an error.
        • What happens now? Notices are still sent - a single notice; however, the token values contained within the are all empty/blank. Labels are still displayed.
        • Proposed solutions:
          • Scenario 4 on UICIRC-454 should help to eliminate some misaligned configurations b/n templates and policies.
          • If there is still a misaligned configuration, is it possible to send a notice for each item overnight (during non-peak hours as not real time indicates) with token values.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                dbranchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases