Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-9632

EOM - Sending data to the unpaid-expenses endpoint

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: CFA 2020R3
    • Component/s: None
    • Labels:
    • Sprint:
      CFAMX 2020R3 Sprint 3, CFAMX 2020R3 Sprint 4
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      2
    • Work Type Classification:
      Sustaining

      Description

      As a system I want to send all relevant data to the unpaid-expenses endpoint whenever a POST call is made so that the CFA system has all of the data

      Notes

      • The CFA EOM endpoints are built in such a way that every time data is sent, all previously received data is removed, and replaced with the new data set
      • The v1/survey/unpaid-expenses endpoint is used by two sections in the EOM, these are:
        • Unpaid Invoices/Expense
        • Utility Payments (When the action = Add Accrual)
      • The issue to be resolved is that when the POST call is triggered from either of the EOM sections, only the data that pertains to that section is sent. The change is that when either of these sections trigger the POST call, the data from BOTH sections is sent
      • Also, in the Utility Payments section the payments can have one of two actions, Add Accrual or No Payment Required, depending on the action selected, the data should be sent to one of two endpoints.
        • Add Accrual - POST to v1/survey/unpaid-expenses
        • No Payment Required - POST to v1/survey/no-payment-accrual-reason

      Acceptance Criteria

      Summary

      • Unpaid Invoices/Expense - POST to v1/survey/unpaid-expenses
      • Utility Payments (Action = Add Accrual) - POST to v1/survey/unpaid-expenses
      • Utility Payments (Action = No Payment Required) - POST to v1/survey/no-payment-accrual-reason
      1. Confirm when the POST is made to the v1/survey/unpaid-expenses endpoint and there is data in the Unpaid Invoices/Expense section, that data is sent to the endpoint
      2. Confirm when the POST is made to the v1/survey/unpaid-expenses endpoint and there is data in the Utility Payments section (where the Action = Add Accrual), that data is sent to the endpoint
      3. Confirm when the POST is made to the v1/survey/unpaid-expenses endpoint and there is data in either the Unpaid Invoices/Expense or the Utility Payments section (where the Action = Add Accrual), that ALL data (from either one or both of the sections) is sent to the endpoint
      4. Confirm when the POST is made to the v1/survey/unpaid-expenses endpoint and there is data in both the Unpaid Invoices/Expense AND the Utility Payments section (where the Action = Add Accrual), that ALL data (from both sections) is sent to the endpoint
      5. Confirm when the POST is made to the v1/survey/unpaid-expenses endpoint and there is data in the Utility Payments section (where the Action = No Payment Required), that data is NOT sent to the unpaid-expenses endpoint
      6. Confirm when the POST is made to the v1/survey/no-payment-accrual-reason endpoint and there is data in the Utility Payments section (where the Action = No Payment Required), that data is sent to the no-payment-accrual-reason endpoint
      7. Confirm when the POST is made to the v1/survey/no-payment-accrual-reason endpoint and there is data in the Utility Payments section (where the Action = Add Accrual), that data is NOT sent to the no-payment-accrual-reason endpoint

        Attachments

        1. image-2020-05-08-19-18-01-497.png
          64 kB
          Charles Wheeler
        2. image-2020-05-13-15-27-27-373.png
          25 kB
          Charles Wheeler

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 9h Original Estimate - 9h
                  9h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 29.5h
                  29.5h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.