Added
Custom units of measure
We've added several new services that allow you to create custom units of measure. See our Unit of measure docs for more information.
Notifying users when other users are changing their current order
In some cases it's possible for multiple users to interact with the same order. This happens when, for example, an order is created on the Companion, but the consumer is sent to the POS to finish the transaction. In the meantime, the user on the Companion might still make (unwanted) changes.
To better handle this, we'll start notifying active users whenever we notice the order is being handled by another user. When prompted with this message, the user can choose to either continue working on the order, or to be detached from the order.
You can influence this with the following app setting: App:Order:ShowTakeoverAlert
(defaults to true). You might also want to add UserIDs to App:Order:IgnoreTakeoverUpdateUsers
to prevent interactions by non-actual-employee user types triggering the alert.
Small additions
- We've added a new variable to Cookbook: Variable Order.ReturnInfo.ReturnWithoutProducts. It expects a true or false value.
by including this in your Cookbook recipe you can filter for a return-without-retake
- Two extension points for validation of serial numbers have been added.
- An extension point that depicts parse barcode actions.
- Expose case interaction author information.
- Added config data to
ListCheckoutOptions
. - Added
SetSettings
service. - We now expose user type on order updated hub.
Improved
Small improvements
- Digital giftcards can no longer be shipped without being paid for.
- Some indices for heavy workloads.
- We've changed the Elasticsearch implementation to focus more on AfterSearch instead of Scrolling, increasing search performance and memory utilization.
- Better user matching.
- Small Case improvements.
- Update indexing of email and phone numbers.
- Improve setting cleanup features by also matching unused/deleted-ou/defaultvalues.
Deprecations
⚡ Removed from typings
These deprecations and requirements are halfway to coming into effect. With these deprecations, the following services and/or fields are no longer be exposed by our typings. Failing to enter the mentioned required fields after the specified core release, will mean the services will no longer work.
Medium
- Field Key is required and will be enforced as such in 2.0.691.
- CreateWorkspace.Key
- GetWorkspaces.Key
Low
- Subscriptions.Subscription.InquiryID is deprecated and will be removed in 2.0.687: Use
Inquiry.ID
instead.- GetUserSubscriptionsResponse.Subscriptions.Subscription.InquiryID
- Subscriptions.Subscription.InquiryName is deprecated and will be removed in 2.0.687: Use
Inquiry.Name
instead.- GetUserSubscriptionsResponse.Subscriptions.Subscription.InquiryName
🚫 Effective
These deprecations and requirements are now effective. With these deprecations, the following services and/or fields are no longer available in EVA and can no longer be used. Failing to enter the mentioned required fields, will mean the services will not work.
High
- EditableByUserTypes is deprecated since 2.0.683: Use SetCustomFieldOptions instead.
- CreateCustomField.EditableByUserTypes
- UpdateCustomField.EditableByUserTypes
- Field Corrections.ReasonID is required since 2.0.683.
- CompleteCloseCashJournal.Corrections.ReasonID
- Result.Page.EditableByUserTypes is deprecated since 2.0.683: Use ListCustomFieldOptions instead.
- ListCustomFieldsResponse.Result.Page.EditableByUserTypes
- Result.Page.VisibleByUserTypes is deprecated since 2.0.683: Use ListCustomFieldOptions instead.
- ListCustomFieldsResponse.Result.Page.VisibleByUserTypes
- VisibleByUserTypes is deprecated since 2.0.683: Use SetCustomFieldOptions instead.
- CreateCustomField.VisibleByUserTypes
- UpdateCustomField.VisibleByUserTypes
Low
- ConnectionType is deprecated since 2.0.683: Not used anymore.
- CreateDevice.ConnectionType
- UpdateDevice.ConnectionType
- HardwareID is deprecated since 2.0.683: Not used anymore.
- CreateDevice.HardwareID
- UpdateDevice.HardwareID
- NetworkName is deprecated since 2.0.683: Not used anymore.
- CreateDevice.NetworkName
- UpdateDevice.NetworkName
- Result.ConnectionType is deprecated since 2.0.683: Not used anymore.
- GetDeviceResponse.Result.ConnectionType
- Result.Devices.HardwareID is deprecated since 2.0.683: Not used anymore.
- GetStationResponse.Result.Devices.HardwareID
- Result.Devices.NetworkName is deprecated since 2.0.683: Not used anymore.
- GetStationResponse.Result.Devices.NetworkName
- Result.HardwareID is deprecated since 2.0.683: Not used anymore.
- GetDeviceResponse.Result.HardwareID
- Result.NetworkName is deprecated since 2.0.683: Not used anymore.
- GetDeviceResponse.Result.NetworkName
- Result.Page.ConnectionType is deprecated since 2.0.683: Not used anymore.
- ListDevicesResponse.Result.Page.ConnectionType
- Result.Page.Devices.HardwareID is deprecated since 2.0.683: Not used anymore.
- ListStationsForOrganizationUnitResponse.Result.Page.Devices.HardwareID
- Result.Page.Devices.NetworkName is deprecated since 2.0.683: Not used anymore.
- ListStationsForOrganizationUnitResponse.Result.Page.Devices.NetworkName
- Result.Page.HardwareID is deprecated since 2.0.683: Not used anymore.
- ListDevicesResponse.Result.Page.HardwareID
- Result.Page.NetworkName is deprecated since 2.0.683: Not used anymore.
- ListDevicesResponse.Result.Page.NetworkName
- Result.Page.OrderLineID is deprecated since 2.0.683: Not used anymore.
- ListPaymentTransactionsResponse.Result.Page.OrderLineID
- Result.Station.Devices.HardwareID is deprecated since 2.0.683: Not used anymore.
- GetDeviceResponse.Result.Station.Devices.HardwareID
- Result.Station.Devices.NetworkName is deprecated since 2.0.683: Not used anymore.
- GetDeviceResponse.Result.Station.Devices.NetworkName
- Station.Devices.HardwareID is deprecated since 2.0.683: Not used anymore.
- SelectStationResponse.Station.Devices.HardwareID
- Station.Devices.NetworkName is deprecated since 2.0.683: Not used anymore.
- SelectStationResponse.Station.Devices.NetworkName
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.