-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R4, CFA 2021R1
-
Component/s: None
-
Links:
-
INF Reference Number:INF-12213
From: CFAMX-11440
With this new WebService, typically we do not include the WebService Endpoints in the deploy scripts, correct? We would not want to install the Dev endpoint address in the wrong environment or install at all in environments like Training where data is unstable.
Basically, the report will continue to use the old endpoint and algorithm until we install this on the server (or an alternate version with Production environment values):
IF NOT EXISTS (SELECT * FROM tbTaskXSLTWebService WHERE WebServiceType = 'LaborBenchmarkServiceV1')
BEGIN
INSERT INTO tbTaskXSLTWebService (Description, EndpointAddress,
WebServiceType, Username, Password)
VALUES ('CFA LaborBenchmark Service V1', 'https://dev.ext.services.cfahome.com/labormanagement/laborBenchmarkService',
'LaborBenchmarkServiceV1', 'dev_wsc_hotschedules', 'Sh25HJD8XOPgdAQ0qhnp')
END
GO
—
I am fine with adding new web service manually. How will the report know which one to use if both exist in tbTaskXSLTWebService table?
—
If it finds the new one by WebServiceType = 'LaborBenchmarkServiceV1' then it will use that, otherwise it will continue to use the old code (which is not actually stored in tbTaskXSLTWebService because it is all web.config and mx.config based).
When the Day Track Report is run, we reach out to two CFA EndPoints:
- Cash Management Service
- LaborCostv3
The purpose of this feature is to replace the call that is made to the Cash Management Service, with a new call to the Labor Benchmark Service, as documented on CFA Confluence (https://cfacorp.atlassian.net/l/c/1Rb0vnJC)
After initial investigation, it looks like the following will need to happen:
- Cash Management service to be replaced with Labor Benchmark Service
- Sample response of CM Service: CashManagementService Response to Daytrack Request (1).xml
- The CM Service returns data for:
- MinimumStaffingHours
- BPRAboveMinimum
- DailySalesBreakpoint
- The three values returned in by the CM Service are used to calculate the Benchmark hours for each day
- The (calculated) Benchmark Hours value is then used to calculate other values within the report
- The new Labor Benchmark Service, has to be called for each day, and will provide the different benchmark hours for that day
// Sample Response { "locationNum": "02693", "date": "15-SEP-2019", "benchmarkLevels": [ { "benchmarkSort": "10", "benchmarkLabel": "Top 10%", "benchmarkHours": "311.8740" }, { "benchmarkSort": "20", "benchmarkLabel": "Top 20%", "benchmarkHours": "320.6958" }, { "benchmarkSort": "33", "benchmarkLabel": "Top 33%", "benchmarkHours": "328.5855" }, { "benchmarkSort": "50", "benchmarkLabel": "Top 50%", "benchmarkHours": "335.0628" } ] }
Requirements
- Update the Day Track to call the Labor Benchmark Service in place of the Cash Management Service
- Update the report to use the Benchmark Hours provided by the service, rather than calculating a value
- Update the report to remove the final Labor page, which displays a single line of data
- is implemented by
-
CFAMX-10364 Day Track Report - Performance Tests
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed