-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R2
-
Component/s: Core
-
Labels:
-
Sprint:CFAMX 2020R2 Sprint 2
-
SCRUM Team:Brotherhood of Mutants
-
Work Type Classification:Sustaining
As an above store user I want a help desk script that allows me to set the store level suggested item flag so that I can pilot an item as being suggested
Business Use case
- Some processes are complicated to perform through the UI, or or performed infrequently, in these cases, Help Desk Scripts have been used to assist.
- In this particular instance, the goal is to allow Chick-fil-A to pilot items as being Suggested Items at some stores, and if this is successful, roll out the item, as a Suggested Item to the whole chain.
- For an item to be suggested there are two flags that get set, one is the HO Suggested Item flag, and the other is the Store Suggested Item flag. When the HO flag is set at the item level, the Store level flag is set for all stores. The goal of this requirement is to do the following.
- Set an item as being a suggested item, this will be done via the I4 import
- At this time, HO = true, and ALL Store = True
- Execute the Help Desk script to set ALL Store = False
- Manually, or through a HD script, set the pilot stores, Store flag = true
- Note: this will not stop those stores that are not involved in the pilot from making the item suggested, that is their choice if they choose to do so. But, if the pilot is not successful, Chick-fil-A will be able to switch the item back to being Not Suggested (using the I4), or roll it out, using the HD Script to set ALL store = true
Notes
- This help desk script will be used to toggle the Store Level Is Suggested Item flag on/off
- [tbentityitem.IsSuggestedItem]
- How help desk scripts work in MMS
- Select Script
- Select Parameters
- Review Expected Results
- Process/Confirm/Execute script
- For Example:
Requirements for this new, MxC Help Desk Scripts, first script.
- Select Script
- Select Store or Zone
- Select Inventory Item
- Click Review
- Display Results
- Apply Results
- Select Script
- The script selected drives the available options
- Need to identify if one or two scripts are required (set all to true, set all to false)
- Look at the Report Portal as an alternative way to display the data.
- Display a description of the function of the script
- Select whether to run for a store or a zone (drop down shown in mock up, could be radio button, slider...)
- Store
- Single store selection modal (used elsewhere)
ZoneDrives the display of Zone ZoneSelection of a Zone Type drives the Zones that are displayedStacy Privalova do you want all zones, or should we just use the Location - abc zones as we have done in the Order Guide?
- Store
- Select the Inventory Item
- See Item Activity search modal (single select)
- Exclude BOMs
- Once all the parameters are selected, click on Review
- The results are displayed for review, prior to the update being applied
- Review can be a light box/overlay, or a new page, whichever works best for the solution
- From the review page, the user can choose to apply the results
- Provide confirmation that the script was run successfully
- New 1/30 - Show details of the number of row affected in the toast
Write an audit record indicating what has changed? Entity Item level or Inventory Item level?Two different audits?First one to show parameters that will be usedSecond to show the results (number of records etc)
- implements
-
CFAMX-6923 SO - HD Scripts - Ability to manage suggested items at a restaurant level (HelpDesk Scripts in MxConnect)
- Closed
- is related to
-
CFAMX-8083 2020.R2(S2): Set SuggestedItem Flag HD Script- All Audit Username appears to be hard-coded
- Done
-
CFAMX-8082 DIT bug - Investigate Bad Data? SQLException on SP expects parameter @value
- Done
1.
|
Review Test Scripts | Done | Gareth Leibbrandt (Inactive) |
|
|||||||||
2.
|
Deploy | Done | Soma Dixon (Inactive) |
|
|||||||||
3.
|
Functional Review with QA | Done | Kevin Reid (Inactive) |
|
|||||||||
4.
|
DIT | Done | Kevin Reid (Inactive) |
|
|||||||||
5.
|
Create Test Cases | Done | Soma Dixon (Inactive) |
|
|||||||||
6.
|
Execute Test Cases | Done | Soma Dixon (Inactive) |
|
|||||||||
7.
|
New UI controls | Done | Kevin Reid (Inactive) |
|
|||||||||
8.
|
Update controller to populate controls | Done | Kevin Reid (Inactive) |
|
|||||||||
9.
|
Review DB schema & update if required | Done | Kevin Reid (Inactive) |
|
|||||||||
10.
|
Create new "review" & "execute" DB scripts | Done | Kevin Reid (Inactive) |
|
|||||||||
11.
|
Update controller to execute scripts & display results | Done | Kevin Reid (Inactive) |
|
|||||||||
12.
|
Implement audit logging | Done | Kevin Reid (Inactive) |
|