-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R4
-
Component/s: None
-
Labels:None
-
Sprint:CFAMX 2020R4 Sprint 1
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:1
-
Work Type Classification:Sustaining
As a developer I want to perform a gap analysis between the old calls that the Day Track report uses and the new response from the new endpoint so that I can map out a path to using the new endpoint.
Notes
- The new endpoint will migrate us from using XML to using JSON
- Investigate implementing this change as configuration (db scripts are ok), so that we can run the report using either XML or JSON responses. The CFA project to implement the new labor solution is delayed, but we should support being ready to switch over (for all stores), when they are ready, rather than having to try and co-ordinate release dates/times.
Existing calls, SOAP UI - Labor (XML)
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v3="http://xmlns.chick-fil-a.com/services/locations/labor/cost/v3" xmlns:v4="http://xmlns.chick-fil-a.com/enterprise/common/v4">
<soapenv:Header/>
<soapenv:Body>
<v3:LaborCostRequest>
<v4:LocationNumber>01919</v4:LocationNumber>
<v3:startDate>2020-04-01</v3:startDate>
<v3:endDate>2020-04-30</v3:endDate>
</v3:LaborCostRequest>
</soapenv:Body>
</soapenv:Envelope>
SOAP Project:
Existing calls, SOAP UI - Cash Management (XML)
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://xmlns.chick-fil-a.com/financial/cashmanagement/daytrack/v1" xmlns:v4="http://xmlns.chick-fil-a.com/enterprise/common/v4">
<soapenv:Header/>
<soapenv:Body>
<v1:DayTrackProductivityParameters>
<v4:LocationNumber>01919</v4:LocationNumber>
<v1:intervalBeginDate>2019-04-01</v1:intervalBeginDate>
<v1:intervalEndDate>2019-04-30</v1:intervalEndDate>
<v1:BenchmarkLevel>10</v1:BenchmarkLevel>
</v1:DayTrackProductivityParameters>
</soapenv:Body>
</soapenv:Envelope>
SOAP Project:
New target End Point (JSON)
Acceptance Criteria
- A mapping exercise is completed, to be used in a later story to implement the new end point, documenting the source SOAP endpoint for each of the fields in the Day Track Report
- A mapping exercise is completed, to be used in a later story to implement the new end point, documenting the source JSON (Labor v4) endpoint for each of the fields in the Day Track Report
- Google sheet for mapping: https://docs.google.com/spreadsheets/d/1N1tPjB_B8k8UCAzZukRUJB3u-yvtL0lSiuhwtMjVzjE/edit#gid=2045706533
- implements
-
CFAMX-10363 US Team - R4 PB - CM - Adjust Daytrack Report to pull from Labor Benchmark Service
- Closed
1.
|
Review Test Scripts | Done | Unassigned |
|
|||||||
2.
|
Deploy | Done | Unassigned |
|
|||||||
3.
|
Functional Review with QA | Done | Unassigned |
|
|||||||
4.
|
DIT | Done | Unassigned |
|
|||||||
5.
|
Research Data points | Done | Sree Surapaneni |
|