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

INF-12307: CM - Finalize Day/Insert Closing Changefund script for future doomsday scenarios

    Details

    • Type: Feature Request
    • Status: Ready for Functional Review (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: CFA 2022R1
    • Component/s: None
    • Labels:
      None

      Description

      Request

      When Covid-19 first hit the US, CFA experienced chain-wide closures more than ever before. A similar problem occurred when ice storms hit many mid-US states in February 2021. There was confusion on what to do in order to finalize subsequent Work Flows over long periods of time.

      CFA would like a Helpdesk script that allows a system admin to complete a Work Flow/string of consecutive Work Flows for a location(s) that has been closed for 1 or more dates.

      This script should be able to be used for mass-chainwide closures as well as standard remodel use cases. This script should be able to be run for 1 or many locations over a date range.

      Question to discuss: Would it be better to have a script that identifies and then finalizes any outstanding business dates, or a script that uses date parameters provided by the user running it?

      InFORM Notes (7/7/21)

      Requirement 1: Search and select multiple locations for update.

      Requirement 2: Select a date or consecutive date range.

      Requirement 3: Complete any unfinalized workflow within the date range provided.

      What does this actually look like? What happens to balances from previous workflows? How does the next valid workflow look once the store is back up and running?

      Notes from meeting on 08/31 - Lots of folks involved

      Hi team,
      These are my notes from our meeting, to provide some more AC for this feature:

      1. The scenario that we are trying to solve for, is when a store is closed, but the POS is still on line
        • In this case, EOD/SOD records are received from the POS, along with Opening Shift records for specific system users (Mobile Order Taker, Online Order Taker, etc)
      2. In this instance, the record in Mx will be a 1
        • After discussing this, our goal state is to set the MxDay record to be 2, which is an ephemeral day
        • Note: When updating the MxDay record, is it possible to change the times in DayOpen and DayClose, to be some value that draws attention to them, and is different from Sundays, which are also marked as 2. Maybe 03:03:03 & 04:04:04
          • Something to help us differentiate between Sundays and HD Script closed days
        • Note 2: If a Sunday, or a day marked as Closed in Entity Manaager is included in the range that is being closed, do not update the MxDay record, leave it as it is
      3. The script should only automatically mark days as closed when there are zero sales and zero paid in/out records
        • If there are sales (+ve or -ve), or if there is a paid in or paid out, the user should be prompted to complete the workflow for that day
      4. Performance - Test against sandbox to ensure that the script is optimized, and provide benchmarks
      5. Stacy supplied two scripts, to reference, which are used in the Training Environments to move days.
      6. Workflow instances - Colin is going to look at the best way to solve for an Open workflow instance on the first day that is being closed (Delete it or move it)
      7. Opening Change Fund - The Opening Change Fund comes from the Closing Change Fund of the previous day, Stacy Privalova is pretty sure that it's the previous calendar day, not the previous workflow day, although we somehow handle Sundays

      Attendees: Stacy PrivalovaMarwa AbdelwahedCharles WheelerTristan StrongColin Wyatt-GoodallSharon Madihlaba

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jason.powell Jason Powell
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  PagerDuty

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