Uploaded image for project: 'mod-notify'
  1. mod-notify
  2. MODNOTIFY-50

Implement API for sending patron notices

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 2.2.0
    • None
    • EPAM-Veg Sprint 9, EPAM-Veg Sprint 10
    • 5
    • Vega

    Description

      Problem

      The notifications sending mechanism used for sending Password Management Events is not convenient for sending Patron Notices as it obtains templateId from predefined event entities for password management events. To reuse current mechanism event entity should be created for every patron notice and while notice sending mod-circulation must somehow know the name of the created entity. This way brings a lot of external complexity, in turn Patron Notice contains templateId itself, so call to mod-event config is redundant.

      Solution

      Implement new endpoint without call to mod-event-config.

      Http method: POST
      URL path: /notify/patron-notice
      Required permission: patron-notice.post
      Response codes: 200, 422, 500
      Request body properties: recipientId, deliveryChannel, templateId, outputFormat, lang(optional, default - en), context(optional)

      TestRail: Results

        Attachments

          Issue Links

            has to be finished together with

            Task - A task that needs to be done. FOLIO-1848 Include mod-notify dependencies in core hosted environments and VMs

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-154 End to End Testing: Send loan-related notices (check-out and check-in)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            requires

            New Feature - New feature requests UXPROD-1386 Send patron notices via email for user initiated loan events, such as check in/out (i.e., check in or out receipt)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1585 Send patron notices for user initiated request events, such as recall request, page request, hold request, cancel, etc (via email)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1586 Send patron notices for time based loan events, such as due date/time (i.e., courtesy notices and overdue notices) via email

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1587 Send patron notices for time based request events, such as hold expiration or request expiration via email

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

            New Feature - New feature requests UXPROD-1588 Send patron notices for user initiated fee/fine events, such as a new manual charge or payment (i.e., fee/fine receipt or new charge notice) via email

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

            New Feature - New feature requests UXPROD-1589 Send patron notices for item status changes (request related), such as available - awaiting pickup (i.e., available notice for recalled item) via email

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Activity

              People

                opoch Oleh Pochernin
                opoch Oleh Pochernin
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases