-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:CFAMX 2020R2 Sprint 4, CFAMX 2020R2 Sprint 5
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:8
-
Work Type Classification:Sustaining
As a user, I would like for the Mobile Workflow panel to instantiate a new workflow instance when appropriate. This includes:
1) If there are no workflow instances at all for a store, but the store is attached to a Workflow Template, an instance should be created for the current date. QUESTION: Would it be better to do for the first, open MxDay?
2) If the current workflow instance that loads is complete (based on the top parent task), then create the instance for the next open date.
3) When all of the tasks are marked complete, the parent task should be marked complete and then reloaded to trigger the same new instance as in #2
Additional considerations:
a) Need to support the "Workflow - Can View" permission which should override the Mobile Workflow Config
b) Respect the Entity Manager "Workflow Participation" attribute as well
c) Respect the "Workflow - Can Create" Permission for whether new instances should get created
d) Respect the Config setting for WorkFlow_AutoForwardToNextWorkFlowDateOnWorkFlowComplete (if off then user would have to browse to the next day and get the instance created then?)
e) Create a SQL Script that can delete a Workflow Instance so we can easily retest on certain Stores \ Days
--------------------------------------------
Will Englefield to provide some details
Sundays
Holidays
Closed Days
Grand Opening script assigns templates and adds an completed instance of the workflow
Attribute for Workflow Participation
Disconnect dates for certain tasks
- implements
-
CFAMX-6855 MxC - Cash Management Workflow
- Closed
- is related to
-
CFAMX-8559 2020.R2(S4): When MxDay not present for a store, change appearance of Workflow
- Done
1.
|
Review Test Scripts | Done | Gareth Leibbrandt (Inactive) |
|
|||||||||
2.
|
Deploy | Done | Soma Dixon (Inactive) |
|
|||||||||
3.
|
Functional Review with QA | Done | Michael DeBinder (Inactive) |
|
|||||||||
4.
|
DIT | Done | Michael DeBinder (Inactive) |
|
|||||||||
5.
|
Build SP to Initialize a WF from a template | Done | Michael DeBinder (Inactive) |
|
|||||||||
6.
|
SQL Script to delete a WF Instance properly | Done | Michael DeBinder (Inactive) |
|
|||||||||
7.
|
Trigger WF Instance Creation on new store | Done | Michael DeBinder (Inactive) |
|
|||||||||
8.
|
Start new Instance when current one completes | Done | Michael DeBinder (Inactive) |
|
|||||||||
9.
|
Create Test Cases/Research | Done | Soma Dixon (Inactive) |
|
|||||||||
10.
|
Execute Test Cases | Done | Soma Dixon (Inactive) |
|