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

2020R1(S6): Create Order Schedule Page missing some localization

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2020R1
    • Fix Version/s: None
    • Component/s: Ordering
    • Labels:

      Description

      Looks like a couple of the fields on this page have not been localized:

      I ran the Pseudo Locale script a handful of times, but I get the same results. Please have a look.

      Steps:
      1. Log into MxConnect with credentials user: Pseudo_locale and password: 123456
      2. Navigate to the Scheduled order page for any store
      Results: the following fields do no appear to be localized:
      Distributor, Order Day and Delivery Day
      Expected: All fields to be localized on new page.

        Attachments

        1. CFAMX-7451localization.jpg
          134 kB
          Soma Dixon
        2. Localisation_mxc_2019R4.sql
          947 kB
          Caner Saritac
        3. Localisation_mxc_trunk.sql
          2 kB
          Caner Saritac
        4. Localization Missing.png
          49 kB
          Soma Dixon

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

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

                    PagerDuty

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