-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2022R2
-
Component/s: None
-
Labels:None
-
Sprint:2022.R2 New Features Sprint 3, 2022.R2 New Features Sprint 4
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:5
-
Work Type Classification:Sustaining
Story
As a user, I do not want to be required to add a customer to certain Outside Sales types at finalize day.
Details
CFA is about to start sending food truck sales to inform using the Outside Sales destinationID (1000013). In order to finalize a day in InFORM, the user is required to make sure a Customer is attached to an Outside Sale. CFA would like to change this so that food truck sales, and certain other outside sales, no longer require this customer attachment.
Current Functionality
When a CFA employee rings an Outside Sale in the POS, they are prompted to attach a customer account to the sale. They have the option, however, to choose to defer this this step in the POS and not attach a customer to the sale.
During the Finalize Day process, if there are Customer Sales that do not have a customer (account name) attached to them, the user is required to navigate to the "TBC/Outside Sales" section of the workflow and attach an account to the sales record.
The user can not finalize the day without first connecting a customer to the sale.
Desired Functionality
CFA does not want users to be required to attach customers to outside sales unless the outside sale includes a tender type of TBC (To Be Collected). TBC may not be the sole tender type attached to an outside sale. There may be a mix of TBC, Cash, Credit, etc.. but the goal is to make sure that any outside with a tender type of TBC is required to have a customer and any outside sale without the tender type of TBC does not need a customer name.
Additional Details
It is known that this change will need further work to fix some reports and changes. This story is specifically to allow the user to finalize the day without a customer assignment for these outside sales types.
New Config
We need to attach this functionality and the future functionality for this feature to a new config that we can switch on and off.
"Operations > Mobile > Administration > Customer Not Required for Outside Sales"
AC
Confirm in Finalize Day
- Outside Sales where the tender type is not "TBC" or does not include "TBC", do not require a Customer assignment in order for the user to complete the "TBC/Outside Sales" task in the workflow.
- Outside Sales where the tender type is not "TBC" or does not include "TBC", do not require a Customer assignment in order for the user to finalize the day.
The user is not warned during the finalize day process if an Outside Sale where the tender type is "TBC" or "TBC + other tender" does not include an assigned customer.- The user IS warned during the finalize day process if an Outside Sale does not have an assigned customer and the tender type for the sake is "TBC" or "TBC + other tender type". Jason Powell Edit 2/8/22
- When the config defined above is OFF, the workflow functionality does not include the desired functionality from this story.
Confirm in "Customers > Customer Sales"
- A customer assignment is not required for Outside Sales that do not include the TBC tender type.
- The user is not prompted to add a customer via the modal.
- Customer assignment is still required for outside sales that do include TBC as a tender type.
Confirm in "Workflow > TBC/Outside Sales"
- Customer sales that do not include TBC are not listed in the grid.
- implements
-
CFAMX-18792 INF-12342 Remove Outside Sales from Customer Sales and send Foodtruck through Outside Sales
- Open
1.
|
Create Test Scripts | Done | Tristan Strong |
|
|||||||||
2.
|
Review Test Scripts | Done | Unassigned |
|
|||||||||
3.
|
Deploy | Done | Tristan Strong |
|
|||||||||
4.
|
Execute Test Cases | Done | Tristan Strong |
|
|||||||||
5.
|
Functional Review with QA | Done | Sree Surapaneni |
|
|||||||||
6.
|
DIT | Done | Sree Surapaneni |
|
|||||||||
7.
|
Design Review | Done | Sree Surapaneni |
|
|||||||||
8.
|
Story Documentation | Done | Unassigned |
|
|||||||||
9.
|
Add new configuration | Done | Sree Surapaneni |
|
|||||||||
10.
|
Make sure that the validation changes do not break other functionalities (report, export etc.. ) | Done | Sree Surapaneni |
|
|||||||||
11.
|
Change the TBC validation to respect the new configuration in Finalize day | Done | Sree Surapaneni |
|
|||||||||
12.
|
Dev Testing | Done | Sree Surapaneni |
|