-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: CFA 2019R4
-
Component/s: Customers
-
Labels:
-
Sprint:CFAMX 2019R4 Sprint 1, CFAMX 2019R4 Sprint 2
-
SCRUM Team:Brotherhood of Mutants
-
SOW (Time Tracking) Project:44918
-
Work Type Classification:Sustaining
As a developer Carlos wants to understand the steps that are needed to allow me to successfully implemented code so that TBC records can be edited
Notes
- The following data can be edited on a TBC
- Description
- Invoice Number
- Customer (in order to update description and Invoice # the customer must be set)
- This spike comes out of
CFAMX-4353 - There are three scenarios to deal with:
- TBC uploaded with a customer - change customer
- TBC uploaded without a customer - select an existing customer
- TBC uploaded without a customer - add and select a new customer
Acceptance Criteria
- Confirm that the architecture documentation is updated to reflect the code being implemented
- Confirm that the document written by Sree Surapaneni is updated to reflect any new scenarios
- Confirm that there is a plan, with a story written, to support Selecting an existing Customer when a TBC is uploaded without a customer
- Confirm that there is a plan, with a story written, to support Creating & Selecting a New Customer when a TBC is uploaded without a customer
- Confirm that there is a plan, with a story written, to support changing the Customer when a TBC is uploaded with a customer
- Confirm that a design review has been undertaken with other developers
- implements
-
CFAMX-4492 TBC - R4 - Re-write & redesign the TBC/Outside Sales in MXC
- Closed
There are no Sub-Tasks for this issue.