Details

      Description

      As a third party system I want to be able to get active available Waste Reason Codes from InFORM so that when I send a Waste transaction I can include an appropriate code

      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.
      • Response should include details that we will require when sending a waste transaction to InFORM
      • For example:
      • Id (Is Id really required, is this something that we would ask CFA to pass back to us?)
      • WasteReasonId
      • Description
      • Filter - NOT Required
        • New ticket, CFAMX-11087,entered to back out the work done around filters

      The Reason Codes displayed on the Record Waste page are viewed/maintained through the List Maintenance page:

      • Admin > Admin > List Maintenance
      • List = Adjustment - Waste

      Acceptance Criteria

      1. Confirm that a generic call can be made to get reason codes
        • Reason codes are used across all stores, and are NOT store specific
      2. Confirm that the response is as streamlined as possible, and only returns 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
      3. Confirm that the response includes details that will allow CFA to POST back a Waste transaction
        • Id / Waste Reason Id
        • There is no reason for CFA to pass back the description
      4. Confirm that there is support for US vs CA stores, although this is not something that we support today
        • From a security perspective we should require a store number on each call
      5. Confirm that the developer has documented the call in Confluence

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 11.5h Original Estimate - 11.5h
                  11.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11.75h
                  11.75h

                    PagerDuty

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