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

Auto Create - Update Job to be hourly not daily

    Details

    • Sprint:
      CFAMX 2020R1 - SA Sprint 6
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      3
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a Product Owner I want the job that Auto Creates Scheduled Orders to be updated to look at the next hour rather than the next day, so that Orders can be created through out the day

      Notes

      • The job is currently designed to be run once per day, when it is run, orders are created for all schedules for the day that do not already have an order associated to them.
      • From SM:
        • Service Method: Mx.Services.ScheduledOrderCreationService,Mx.Services:CreateSalesOrdersFromSchedule
      • The purpose of this change is to allow messages to be queued, and have orders be created at the appropriate time, rather than at some arbitrary time

      Acceptance Criteria

      • When the job runs:
        • Determine which schedules have a order date & time that is due to be placed/created within the next hour (CFAMX-7332 - Order Day & Order Time)
        • For each of those schedules:
          • If an order already exists, do nothing
          • If an order has not already been associated to the schedule, put a message on the queue (Store/Schedule/Date/Time)
            • The message should fire at the relevant Date/Time:
            • If at the time the message fires there is no order associated to the schedule, and the schedule still exists, create the order (The forecast period for the order should be between the Order Day & Time and the Cover Until Day & Time)
            • If at the time the message fires there is an order associated with the schedule (someone created it manually, between when the task ran and the message is processed), the message should complete successfully. It should not report as a failure, if we keep the messages, maybe include a comments to say that Order 12345 already exists for the schedule
            • If at the time the message fires, the schedule no longer exists the message should complete successfully. It should not report as a failure.
      • Any messages being placed on the queue should take into account the difference between Server Time and Store Local Time, message should be fired at Store Local Time. Meaning that an order Time of 10am at Castle Rock, should be placed at 10am MST, not 10am EST.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 18h Original Estimate - 18h
                  18h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 35h 16m
                  35h 16m

                    PagerDuty

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