Unused Workforce Management routes being deprecated in late March

Announcements
1

UPDATE: This notice was originally posted on January 24. On March 16, we've removed the second section of impacted APIs. Only the unused APIs listed on this notice as of March 16 will be removed.

Category: API

Summary: Unused Workforce Management routes being deprecated alongside the release of WEM-12.

Context: WEM-12 is a large set of changes to Workforce Management. It introduces the concept of Business Units, which now contain Management Units. It also introduces Planning Groups and Service Goal Templates, which supercede Service Goal Groups. Forecasts, Schedules, and other objects are moving to be part of the Business Unit instead of the Management Unit. Business Units can contain many more agents than Management Units (5000 instead of 1000), and allow you to forecast and schedule across multiple Management Units.

Impact: There should be no impact to customers as long as they don't start using routes we are deprecating as part of this notice. Any routes that customers are using today are being kept functional. Once we release the Business Units feature, we will post a second deprecation notice that will deprecate some routes customers are using today, but only after we have provided viable alternatives for them to switch to.

Date of Change: APIs are being marked as deprecated now and will be removed no sooner than March 25, 2020.

Impacted APIs:

The following routes are unused and being deprecated immediately and will be removed when we release WEM-12. You should not start using them. New routes that perform this functionality will be released with WEM-12.

GET|PATCH|DELETE /workforcemanagement/managementunits/{managementUnitId}/scheduling/runs/*

POST|DELETE|PATCH /workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/schedules/*

GET|POST /workforcemanagement/managementunits/{muId}/intraday

GET /workforcemanagement/managementunits/{muId}/settings

PATCH /workforcemanagement/managementunits/{muId}/settings

GET|POST|PATCH|DELETE /workforcemanagement/managementunits/{managementUnitId}/servicegoalgroups/*

GET|POST|PATCH|DELETE /workforcemanagement/managementunits/{managementUnitId}/weeks/{weekDateId}/shorttermforecasts

POST /workforcemanagement/managementunits/{muId}/timeoffrequests/fetchdetails

PUT /workforcemanagement/managementunits/{managementUnitId}/weeks/{weekDateId}/shifttrades/{tradeId}/state

POST /workforcemanagement/agents/managementunits

1 Like
2

There is a report from a business partner where they are in the process of developing an app that executes some of these 'deprecated' routes, and the development will continue for the time being. (So, we are a bit confused as to what we mean by "The following routes are unused and" because those routes ARE used on the customer org.)

What is our (Genesys) expectation in terms of transition to new routes? For example, does the business partner have to stop the development until they see the announcement for the new routes, or given we say "Any routes that customers are using today are being kept functional", can the business partner continue to develop as they have designed thus far, in which case they have to update the app logic to use the new routes in, say, a couple of months down the road?

Please let us know. Thanks.

3

Per our Change Management Policy, we generally give 60 days notice before removing any resources from service in order to allow customers time to transition as needed.

Out of curiosity, which route in this list is being used by the partner?

4

We are just developing application which enable import/export agent shift, for release near future(next month) using these API.

[GET] "/api/v2/workforcemanagement/managementunits/{id}/weeks/{week}/schedules/{id}"
[GET] "/api/v2/workforcemanagement/managementunits/{id}/weeks/{week}/schedules"
[PATCH] "/api/v2/workforcemanagement/managementunits/{id}/weeks/{week}/schedules/{id}"
[GET] "/api/v2/workforcemanagement/managementunits"
[GET] "/api/v2/workforcemanagement/managementunits/{Id}"
[GET] "/api/v2/workforcemanagement/managementunits/{id}/activitycodes"
[GET] "/api/v2/workforcemanagement/managementunits/{id}/users"

5

This topic was automatically closed 62 days after the last reply. New replies are no longer allowed.