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

Implement API for sending patron notices

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.2.0
    • Labels:
      None
    • Template:
    • Sprint:
      EPAM-Veg Sprint 9, EPAM-Veg Sprint 10
    • Story Points:
      5
    • Development Team:
      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

              Activity

                People

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

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases