Description
In the case where a user requests either historical adherence for a work team
POST /api/v2/workforcemanagement/teams/{teamId}/adherence/historical
or shrinkage for a work team
POST /api/v2/workforcemanagement/teams/{teamId}/shrinkage/jobs
If it happens that the work team is either empty, or that no members of that work team are in a management unit, the api would incorrectly return a 403, even if the requesting user is authorized to view that data should it exist. We are changing the response code for this situation to a 400 to differentiate between the cases of “user doesn’t have access to this data” and “invalid work team configuration to call this route”.
Note: If the work team configuration is corrected to have users in a management unit, and the user is not authorized to view the data, they will continue to receive a 403.
Change Category
Informational
API
Change Context
Differentiate between the cases of “user doesn’t have access to this data” and “invalid work team configuration to call this route.”
Change Impact
You will receive a 400 response where previously you would receive 403s that (may or may not, but most likely not) have been accurate.
If the users are genuinely not authorized for the information after correcting the work team configuration, the user will continue to receive a 403.
Date of Change
March 30, 2025
Impacted APIs
POST /api/v2/workforcemanagement/teams/{teamId}/adherence/historical
POST /api/v2/workforcemanagement/teams/{teamId}/shrinkage/jobs
References
[WFM-24637]