WFM Adherence Report Data: Routing Status STILL different from documentation

[Orion_Rapp]

Greetings,

On March 13th I posted that the data downloaded as a result of using this API:

/api/v2/workforcemanagement/managementunits/{managementUnitId}/historicaladherencequery

The WfmHistorialAdherenceResultWrapper class in the SDK defines RoutingStatus as an object with three properties.

In my original post, you kindly acknowledged the issue and resolved to fix it.

However, occasionally we still get results that look like the following:

We have to code around the problem still. Can this issue be reopened?

Many thanks,
Orion

[anon11147534]

Hi,

Sorry that you are still experiencing this problem. I would recommend contacting Care again to make the dev teams aware of the issues.

[brian.trezise]

As mentioned on your previous post, the data being returned is correct, it was the documentation (and the sdk which is generated from the documentation) that was incorrect.

The documentation is now corrected (see link and screenshot below), however you'll need to update your SDK client version to pick up the corrected schema. The below link also contains links to the latest SDK documentation in the various "Invocations" tabs

POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/historicaladherencequery

[brian.trezise]

Or, I just re-read my response on the original post, and I wasn't clear as to what the actual bug was. The bug was that the SDK was wrong, not the data. Apologize for the lack of clarity there. If you update to the latest version of the SDK it should work now.