US Team - CM - Adjust Daytrack Report to use LaborCostv4

As a system pulling data from for the Day Track Report I want to support either an XML (LaborCostv3) or JSON (LaborCostv4) data source

The Labor team that provides data for the Daytrack Report to read from will be moving this data to a new source. To make it available to us, they will be standing up an API and a new DEI job. See details below for how these willed be hit/called:

• Labor Cost and Labor Hours will be provided in JSON format instead of XML (see example here: Strategy Document
• Labor team is standing up a "Labor Metric API" for historical data (ie further into the past than current and previous day’s dates)
  • InFORM to hit this API (replacing need for LaborCostV3)
  • LaborCostV3 to be retired once all locations are on Ceridian
  • Labor team will provide documentation with specs on hitting this API
• Labor team is creating a new “LaborCostV4” service that, when called, provides data for current and previous day’s business dates.
  • InFORM to call LaborCostV4
  • If the location is not set up with Ceridian yet, LaborCostV4 will then call LaborCostV3 and provide the data in JSON format
• Details of the new endpoint can be found here: https://cfacorp.atlassian.net/l/c/k6777X3f