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

2019.R4(S3) TBC Page: Updating No Customer does not adjust balance correctly for the New Customer

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Critical
    • Resolution: Completed
    • Affects Version/s: CFA 2019R4
    • Fix Version/s: CFA 2019R4
    • Component/s: customerSales
    • Labels:
      None

      Description

      Environment: JAT
      Build: CFA - 19.4.0.2422
      Store: 00198 - Northwest Arkansas Mall
      User: Store Manager
      Day: Tue, Jul 23, 2019
      Page: https://m.inform.jatesting.cfahome.com/#/Financial/CustomerSales

       

      Steps

      I Inactivated Mary Hotard from INform

      Created a $12.17 TBC for her from the POS

      Observe: Correctly Showed up as an inactive customer on the TBC page

      But when I assigned the TBC to a new customer, the back end data did not adjust correctly to create the right balance for the new customer. 

       

       

        Attachments

          Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFAMX-4499 TBC - Display message when an TBC is processed for an inactive account

          • Closed

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                soma.dixon Soma Dixon (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  0h
                  Logged:
                  Time Not Required
                  Not Specified

                    PagerDuty

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