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

CFA API - Transfer that is partially declined is not correctly updated in tbTransactionTransferDetail

    Details

    • Type: Testing Defect
    • Status: Done (View Workflow)
    • Priority: Critical
    • Resolution: Completed
    • Affects Version/s: CFA 2023R3
    • Fix Version/s: CFA 2023R3
    • Component/s: API
    • Labels:
      None
    • SCRUM Team:
      Globogym Purple Cobras
    • Sprint:
      2023.R3 New Features Sprint 4

      Description

      Scenario - when the api/transfer/updatetransfer is called from Signal UI, we are not updating the Received transferqty1, transferqty2 or transferQty3 correctly.

      Steps to reproduce - in JAT

      1.Create a Transfer in JAT from sending store  01023 to receiving store 00663. (signaltransferid = 18833)

      2.The transfer is received by a signal user and all qty's for the item are partially received. 

       CFA API api/transfer/updatetransfer is called and the items TransferQty1- 3 are all partially received by exactly 1/2.

      3. *  Declined tbTransactionTransfer & tbTransactionTransferDetail are created as expected 

       

      Defect : The tbTransactionTransferDetail associated with the Received tbTransactionTransfer record (554804) should be updated in the TransferQty1, TransferQty2 and TransferQty3 values.  

       

      In this case - I declined 20, 15 and 10 respectively so the values in TransferQty 1- 3 should be reduced these values respectively.   

      WRONG JAT DB with our API

      Correct in TESTING DB when using 2 non signal stores

        Attachments

        1. image-2023-04-25-11-46-31-494.png
          49 kB
          Charles Wheeler
        2. image-2023-04-25-11-48-20-220.png
          53 kB
          Charles Wheeler

          Issue Links

            Activity

              People

              • Assignee:
                Tristan.Strong Tristan Strong
                Reporter:
                charles.wheeler Charles Wheeler
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h
                  4h

                    PagerDuty

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