Details

    • Sprint:
      CFAMX 2020R4 Sprint 5
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      As a third party system I want to be able to POST a Waste Transaction to InFORM so that I can leverage the inventory management that InFORM offers

      Notes

      • Note: We do not have any details about the solutions that CFA are planning to implement, other than they would like to use APIs to inject waste, this story is a part of the effort to provide robust, external facing API calls that can be used to GET and POST data.
      • Create a streamlined POST that will allow CFA to inject Waste Transactions, containing minimum data required to create a waste transaction
      • For example:
        • Store Number (not entity id)
        • Item Code (not Item Id)
        • Unit of measure, depending on unit being wasted:
          • Outer - Unit Of Measure
          • Inner - Unit Of Measure
          • Unit - Unit Of Measure
          • Metric Unit - Unit Of Measure
        • Quantity of unit being wasted
        • Reason Code - By item
        • Date & Time of the transaction

      Acceptance Criteria

      1. Confirm that the Request is as streamlined as possible, and only uses data that truly needs to be passed back to InFORM to inject a Waste transaction via the new API calls being developed under this feature
      2. Confirm that the Store Number must be included in the call
      3. Confirm that the Store must be Open in order to process the response
        • Not Closed or Temporarily Closed
      4. Confirm that the item being wasted must be InUse/Active in order for the request to complete successfully
      5. Confirm that the Unit Of Measure passed back is valid for the item being wasted
      6. Confirm that the quantity being wasted must be a positive value
      7. Confirm that the quantity being wasted cannot exceed two decimal places
      8. Confirm that the quantity being wasted cannot exceed 999
      9. Confirm that a Reason Code is required for each item to be wasted
      10. Confirm that the Reason Code is Valid in InFORM
      11. Confirm that the date included cannot be a Sunday
      12. Confirm that the date included cannot be in the future
      13. Confirm that the date included cannot be in a closed business period
      14. Confirm that the developer has documented the call in Confluence

        Attachments

          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 - 48h
                  48h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 44h Time Not Required
                  44h

                    PagerDuty

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