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

Help Desk Script - Migrate TLD/LiteSum Comparison

    Details

    • Sprint:
      CFAMX 2020R2 Sprint 3, CFAMX 2020R2 Sprint 4
    • SCRUM Team:
      Brotherhood of Mutants
    • Work Type Classification:
      Sustaining

      Description

      As a Support Tech I want to be able to execute the TLD/LiteSum Comparison script within MxC so that I don't have to use MS

      Notes

      • Based on feedback from CFA, we will only be migrating a few HD Scripts

      Acceptance Criteria

      1. Confirm that the TLD/LiteSum Comparison script is available in MxC
      2. Confirm that the expected results of the scripts can be reviewed before executing them
      3. Confirm that the scripts can be successfully executed
      History of this ticket

      As a support tech, I want to be able to run Help Desk Scripts in MxC so that I no longer have to use MMS

      Notes

      • This story is to migrate a number of the Help Desk scripts from MMS to MxC, starting with those that only require the selection of:
        • Store
        • Date
        • Script
      • For Example:
        • Unfinalize Day
        • Forecast Component Actuals
        • Transfer Status
        • EOM Counts Status
        • Finalizes Previous Calendar Days
        • Get Last Finalized Calendar Day
        • Insert Closing Change Fund
        • Checks/Sets LL transaction sending settings
        • Uncheck MxConnect Sales Item Forecast Visibility
        • Insert Previous WorkFlow

      Feedback from Charles Holmes at CFA is that the only scripts that are used by CFA help desk are:

      1. TLD/LiteSum Comparison
      2. Shift Validation Status Check
      3. Shift Validation Status Update
      4. DLPS Diagnostics CFA are replacing DLPS at some point in the future, so we will not port this one
      5. Orphan Cashier Shifts
        Therefore, these should be our priority

      Acceptance Criteria

      1. Confirm that the simple help desk scripts are available in MxC
      2. Confirm that the expected results of the scripts can be reviewed before executing them
      3. Confirm that the scripts can be successfully executed

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 39h
                  39h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 25.75h Time Not Required
                  25.75h

                    PagerDuty

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