Uploaded image for project: 'Document Management System'
  1. Document Management System
  2. DMS-377

Notification History in Communications Module

    Details

    • Type: Research
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Email communication
    • Labels:
      None

      Description

      Maintaining notification history, event on notifications. Data models related to maintaining notification history.

      Two APIs are exposed to get email history:

      api/email/history and api/email/detail

      See swagger API specification for field details.

        Attachments

        1. Capture.PNG
          Capture.PNG
          28 kB
        2. DMS-377_1.jpg
          DMS-377_1.jpg
          157 kB
        3. DMS-377_2.jpg
          DMS-377_2.jpg
          131 kB
        4. DMS-377.jpg
          DMS-377.jpg
          284 kB
        5. Screenshot (851).png
          Screenshot (851).png
          119 kB
        6. Screenshot (852).png
          Screenshot (852).png
          115 kB
        7. Screenshot (881).png
          Screenshot (881).png
          121 kB
        8. Screenshot (882).png
          Screenshot (882).png
          135 kB

          Issue Links

            Activity

            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: API testing

            Getting attached error with testing API. Can you please check the same.

            Swapnil Pandhare Samir

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: API testing Getting attached error with testing API. Can you please check the same. Swapnil Pandhare Samir
            Hide
            harshveer.singh Harshveer Singh (Inactive) added a comment -

            That error seems to be coming because you have specified query string parameters in Headers section, you should provide those as part of URL itself like: /history?page=1&count=10

            I have tried it now, it seems to be working fine.

            Show
            harshveer.singh Harshveer Singh (Inactive) added a comment - That error seems to be coming because you have specified query string parameters in Headers section, you should provide those as part of URL itself like: /history?page=1&count=10 I have tried it now, it seems to be working fine.
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Hi Harshveer Singh,

            Getting error for the APi without adding text in header as well. 

            Refer screen capture 

             

            Swapnil Pandhare

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Hi Harshveer Singh , Getting error for the APi without adding text in header as well.  Refer screen capture    Swapnil Pandhare
            Hide
            harshveer.singh Harshveer Singh (Inactive) added a comment -

            It seems you have provided some whitespace or new lines in Header section because of which this error might be coming, see screenshot below for which API is working fine:

             

            Show
            harshveer.singh Harshveer Singh (Inactive) added a comment - It seems you have provided some whitespace or new lines in Header section because of which this error might be coming, see screenshot below for which API is working fine:  
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: OneIM

            Both API api/email/history and api/email/detail are verified for its working. Results are as expected. So, closing jira.

            Harshveer Singh Swapnil Pandhare Samir

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: OneIM Both API api/email/history and api/email/detail are verified for its working. Results are as expected. So, closing jira. Harshveer Singh Swapnil Pandhare Samir

              People

              Assignee:
              harshveer.singh Harshveer Singh (Inactive)
              Reporter:
              harshveer.singh Harshveer Singh (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4h Original Estimate - 4h
                  4h
                  Remaining:
                  Time Spent - 17.75h Remaining Estimate - 5h
                  5h
                  Logged:
                  Time Spent - 17.75h Remaining Estimate - 5h
                  17.75h