Description
Why?
We are releasing a new feature that will allow users to have more than one historical file in the system and load multiple files. Part of this feature replaces the old purge functionality, which would purge one file with a multi-purge. That means the current purge API endpoints will no longer be usable, so we are replacing them with new endpoints.
What is changing?
We are deprecating and replacing a few old API endpoints with new ones.
Old API’s
POST - /api/v2/workforcemanagement/historicaldata/deletejob
GET - /api/v2/wokrforcemanagement/historicaldata/deletejob
New API’s
POST - /api/v2/workforcemanagement/historicaldata/bulk/remove/jobs
GET - /api/v2/workforcemanagement/historicaldata/bulk/remove/jobs/{jobid}
GET - /api/v2/workforcemanagement/historicaldata/bulk/remove/jobs
Change Category
API
Change Context
We released a new feature, The ability for the Historical Data Import to accept multiple file imports, which will allow users to have more than one historical file in the system and load multiple files. Part of this feature replaces the old purge functionality, which would purge one file with a multi-purge. That means the current purge API endpoints will no longer be usable, so we are replacing them with new endpoints.
Change Impact
Customers that have used them will need to now use the new API's
Date of Change
Immediate
Impacted APIs
POST - /api/v2/workforcemanagement/historicaldata/deletejob
GET - /api/v2/wokrforcemanagement/historicaldata/deletejob
References
Deprecation - [WEM-1223]
New feature introducing the new API's - [WEM-431]