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

Workflow - Migrate Opening Change Fund to MxC W/F

    Details

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

      Description

      As an operator I want to be able to complete the Opening Change Fund in MxC so that I no longer have to use MMS

      Notes

      • Need to come up with a way to mark optional tasks as complete, my preference would be to do it on the page, rather than within the workflow

      Acceptance Criteria

      1. Confirm that the Opening Change Fund page is representative of the date of the workflow being completed
      2. Confirm that the Opening Change Fund is an optional task
      3. Confirm that there is a way to mark an optional task as Complete without having to perform it

      Dev Notes - Updates made:

      1) Added gear icon on each task for ones where a Complete, Override or Rollback option are available. Override and Rollback actions are tied to permissions. Complete is only available on tasks marked as such. Complete and Override are also hidden if already on that status. Rollback is only available when Status is not 0 or 1. It actually resets the Status to 1 for some reason I am not sure of.

      2) Added gear icon beside "Daily Workflow" title. This contains actions for Refresh, Rollback, Go To Current, and Go To Today. 

        a) Refresh just reloads the workflow in case statuses have changed
        b) Rollback is tied to the permission for Rollback Entire Workflow and will not show if date is past the current workflow
        c) Go To Current is only available when not on the date of the current workflow and jumps to that date if selected
        d) Go To Today is only available when not on current date and jumps to today

      3) When clicking a task still on StatusID 0, status will be updated to 2. This is not really visible in the Mobile UI right now, but we may in the future.

      4) The User's Workflow Pin\Unpin selection should now be stored in Mobile Settings and default appropriately on each login.

      5) Changing the date to a date past the current workflow date should leave the list of tasks the same as the current workflow, but turn all the buttons white and be used only for navigation, not for updating workflow. There should also be a message letting the user know the workflow is not a valid instance.

      6) On the Opening Change Fund page, if the Mobile Workflow is on, the Date Picker should not appear on the page but instead you should see a read-only date and also see a calendar icon to re-open the workflow frame. The date-picker should always show when in the embedded frame in MMS.

      7) When the Mobile Workflow is on, the workflow should always default to the most recent Workflow Instance date. Otherwise (and in embedded mode) it should default to the previous functionality of defaulting to the most recent Workflow Count date or as far back as 14 days (based on config).

       

       

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            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 - 21h Original Estimate - 21h
                  21h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 30h 35m
                  30h 35m

                    PagerDuty

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