Breaking
PushSalesOrder security features
As announced in v2.0.637
, we will be insisting on some additional PushSalesOrder
security features. Time has come for this release to set the boundaries to our support, requiring customers to migrate to these features.
⛔ This will affect all systems calling PushSalesOrder
and will be persisted through to production as well, so please follow up diligently.
💡 The migration of functionality- and user type requirements is an unusual one, which is why you will not see it within our regular automated communication or lists of deprecations!
1. Separate functionality PushSalesOrder
Currently, calling this service requires the Create scope on functionality Orders, but this is a little common for such a specific purpose service. Soon, EVA will require the non-scoped functionality PushSalesOrder instead, allowing you to narrow down the use more specifically.
- After 4 releases (
2.0.715
), in all non-production environments, this new functionality PushSalesOrder is required to call this service. - After 8 releases (
2.0.719
), production environments too will require this.
2. Required user type API
At the moment, we have no limitations to what user type can call this service. But again, due to the specific nature of this service, we want to move towards requiring a special API user. If this is currently not yet the case, this might mean a new user and API key have to be created and configured, which might have some impact for the third party applications using this service.
- After 12 releases (
2.0.723
), in all non-production environments, this API user type is required to call this service. - After 16 releases (
2.0.727
), production environments too will require this.
Added
- Added
LayerLevel
to the response ofListProductContentEdits
. - Added
BackendID
to the response ofListCompanies
.
Fixes
- We fixed an issue where reusing the same Excel files in Replenishments gave errors.
Deprecations
⚡ Removed from typings
These deprecations are now halfway through their deprecation timeline. As of now, these services and/or fields will no longer be exposed by our typings.
High
GetOrganizationUnitsForUser
is deprecated and will be removed in2.0.743
: UseGetLoginOrganizationUnitsForUser
instead.
🚫 Effective
These deprecations are now effective. As of now, these services and/or fields are no longer available in EVA and can no longer be used.
Low
- Property
OrderTheLinesFromASupplier
on serviceChangeOrderLinesToCarryOut
is deprecated since2.0.711
: UseMustBeOrdered
instead.
Release dates may vary
The exact date for deploying a Core release to production environments may vary. See How we handle Core releases for more details.