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

Workflow - Change position of Closing Change Fund

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      CFAMX 2020R3 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      As an operator I want the Collected Sales task to be moved to be after Cashier Settlement so that I can complete my Cashier Settlement before Closing out my Change Fund for the day

      Notes

      • Move Closing Change Fund to be after Cashier Settlement - This can be done in both MMS and MxC
      • Update any tasks that are dependent on completing the Closing Change Fund to account for the new position of the Closing Change Fund
      • Update the Confirmation Queries on any tasks that are before the new location of the Closing Change Fund task, that reference the Closing Change Fund

      Task details

      Looking at the page that Michael DeBinder created, https://fourthlimited.atlassian.net/l/c/U5Jp6THm, the current Confirmation Queries are:

      Task Confirmation Query
      Closing Change Fund qryMMSWorkFlowCheck_ClosingChangeFundStatus
      TBC/Outside Sales qryMMSWorkFlowCheck_ClosingChangeFundStatus, qryMMSWorkFlowCheck_CustomerSalesStatus
      Collected Sales qryMMSWorkFlowCheck_ClosingChangeFundStatus, qryMMSWorkFlowCheck_CustomerSalesStatus
      Paid In/Out qryMMSWorkFlowCheck_PettyCashStatus
      Cashier Settlement qryMMSWorkFlowCheck_OpenCashiersStatus, qryMMSWorkFlowCheck_CashierSettlementStatus, qryMMSWorkFlowCheck_PettyCashStatus, qryMMSWorkFlowCheck_ClosingChangeFundStatus

      The following tasks will need the Confirmation Queries adjusting to match the new location of the Closing Change Fund

      • TBC/Outside Sales - Remove qryMMSWorkFlowCheck_ClosingChangeFundStatus
      • Collected Sales - Remove qryMMSWorkFlowCheck_ClosingChangeFundStatus
      • Cashier Settlement - Remove qryMMSWorkFlowCheck_ClosingChangeFundStatus

      Update the Closing Change Fund task, in its new location, after Cashier Settlement to be Dependent on the Cashier Settlement

      The workflow order will be updated manually post deploy

      Acceptance Crietria

      1. Confirm that the Closing Change Fund task is moved to be between the Cashier Settlement and Deposits tasks in both MMX and MxC
      2. Confirm that the Closing Change Fund is now dependent on the Cashier Settlement Task being completed
      3. Confirm that the Closing Change Fund task cannot be completed if a Closing Change Fund for a previous business day is not completed (Current functionality)
      4. Confirm that TBC/Outside Sales, Collected Sales, Paid In/Out and Cashier Settlement tasks can be completed successfully before the Closing Change Fund task is completed
      5. Confirm that TBC/Outside Sales, Collected Sales, Paid In/Out and Cashier Settlement tasks must be completed successfully before the Closing Change Fund task is completed
      6. Confirm that TBC/Outside Sales, Collected Sales, Paid In/Out and Cashier Settlement tasks can be completed successfully before the Closing Change Fund task is completed when completing the Workflow in MMS
      7. Confirm that TBC/Outside Sales, Collected Sales, Paid In/Out and Cashier Settlement tasks must be completed successfully before the Closing Change Fund task is completed when completing the Workflow in MMS
      8. Confirm that documentation is updated to reflect this new configuration

        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 - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 22h Time Not Required
                  22h

                    PagerDuty

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