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

Scheduled Order Import - Update to support delivery date time check

    Details

    • Sprint:
      CFAMX 2018R4 Sprint 3, CFAMX 2018R4 Sprint 4, CFAMX 2018R4 Sprint 5, CFAMX 2018R4 Hardening, CFAMX 2019R1 Sprint 1
    • SOW (Time Tracking) Project:
      44792

      Description

      As a Store Manager I want my imported Scheduled Orders to include a delivery time so that my auto create job can use that time when generating an order

      Notes

      Acceptance Criteria
      Delivery Time

      1. Confirm that the import supports a Delivery Time as an optional field
        • Format should be hh:mm
        • If the field is not supplied only the delivery date is used
        • If the Delivery Time is supplied it must be a valid time
      2. Confirm that if a delivery time is provided it is displayed on the order series that is created

      Cover Until Time

      1. Determine what the default offset is for cover until time, and review with Will Englefield
      2. The Cover Until Time, for a Suggested (Scheduled) Order is the Delivery Date time plus one day
        • For example:
        • Delivery Date: Sep 24, 2018 6:45 AM
        • Cover Until: Sep 25, 2018 6:45 AM

      Auto Submit

      1. Confirm that the import supports the Auto Submit attribute as an optional field
      2. Confirm that if the Auto Submit field is supplied as true, this is reflected in the order series that is created

      Duplicate Records

      1. Confirm that the import is enhanced to prevent the importing of duplicate records (see MX-16109
      2. There is a new configuration option in the form of an optional XML Header Attribute: “Skip Duplicates” (name is TBD)
        • This optional header attribute is to be added by the vendor (or through a custom XSLT)
      3. If the Scheduled Order Import does contain the “Skip Duplicates” (name is TBD) header attribute, and the value of that attribute is set to true, AND there are existing records with the same store, vendor, and order date combination, then:
        • Do not import records
        • A warning is reported for this import
      4. If the Scheduled Order Import does contain the “Skip Duplicates” (name is TBD) header attribute, and the value of that attribute is set to false, AND there are existing records with the same store, vendor, and order date combination, then:
        • Proceed in importing the duplicate records (current functionality)
        • Do not report a warning for this import
      5. If the Scheduled Order Import does not contain the “Skip Duplicates” (name is TBD) header attribute, AND there are existing records with the same store, vendor, and order date combination, then:
        • Proceed in importing the duplicate records (current functionality)
        • Do not report a warning for this import

      Scope Exclusions
      No changes will be made to the Scheduled Order Setup, under the Store Calendar, to prevent a user from manually entering duplicate scheduled order records.

      Note: If a record is manually created, the import will respect that record, and will not permit a duplicate, in the event that the optional header attribute is included.

        Attachments

        1. screenshot-2.png
          screenshot-2.png
          20 kB
        2. screenshot-1.png
          screenshot-1.png
          31 kB
        3. OrderSchedule20170220_21586_1.xml
          0.3 kB
        4. OrderSchedule20170216_280197_1.xml
          0.3 kB
        5. Manual0000.png
          Manual0000.png
          24 kB
        6. Imported0500.png
          Imported0500.png
          27 kB
        7. image-2018-07-12-21-03-58-677.png
          image-2018-07-12-21-03-58-677.png
          87 kB

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 56h 8m Original Estimate - 56h 8m
                  56h 8m
                  Remaining:
                  Time Spent - 177.65h Remaining Estimate - 10h
                  10h
                  Logged:
                  Time Spent - 177.65h Remaining Estimate - 10h
                  177.65h

                    PagerDuty

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