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

Warning Doesn't Appear When Editing Customer History Records

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: CFA 2022R2
    • Fix Version/s: None
    • Component/s: Customers
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Sprint:
      2022.R2 New Features Sprint 5

      Description

      Details
      Warning Doesn't Appear When Editing Customer History Records

      Testing Environment Details
      Effected Server: JAT
      Build: CFA - 22.2.0.4849
      Affected: All
      iPad Version: 14.4.1
      Store(s): Any
      Logged in User: sysadmin

      Feature: N/A
      Related Tickets (Stories or Features): CFAMX-19209
      Other Related Links (Confluence, BRDs, Etc...): N/A
      Feature Configurations: CFAMX-12484

      Steps to Reproduce:
      1. Login to JAT
      2. Change to Store 00442 - College Mall
      3. Navigate to Customers > Customer Management
      4. Click on History next to Bath and Body Works account
      5. Check the Uncollectible checkbox
      6. Navigate to another page (Ex. Input Inv. Counts > Weekly)

      Expected Result
      User should receive a warning that they will lose changes if they navigate to a different page and if they wish to proceed

      Actual Result
      MxConnect becomes unresponsive

        Attachments

        1. screenshot-1.png
          67 kB
          Gareth Leibbrandt

          Issue Links

            Activity

              People

              • Assignee:
                John.Rust John Rust
                Reporter:
                Tristan.Strong Tristan Strong
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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