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

SO export - Trigger Export when order is canceled

    Details

    • Sprint:
      CFAMX 2019R3 Sprint 1
    • SCRUM Team:
      Globogym Purple Cobras
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a third party system I want to receive the Suggested Order Export when an Order is Canceled so that I am aware that the Order has not been fulfilled

      Notes

      • The SO Export is Event based, currently there are two events that trigger the export, they are:
        • SupplyOrderCreated
        • SupplyOrderReceivedChangeApplyDateCorrectReceive
        • We will need a new event to trigger the export when the order is canceled:
          • SupplyOrderCanceled

      Acceptance Criteria

      1. Confirm when an Order is Canceled, and the SupplyOrderCanceled event is raised the Suggested Order Export is triggered and contains data for the order
        • Note: Can all data be included at this point (Cancel), or only header data?
      2. Confirm that the Order Status (CFAMX-3383) reflects the correct status of a Canceled order

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 19h 40m
                  19h 40m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 19h 40m
                  19h 40m

                    PagerDuty

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