Core 2.0.751

No breaking changes.

🆕 Displaying Product Requirements​

Certified Invoice templates, both thermal and PDF, now show product requirements when:

• A product requirement is mandatory.
• A product requirement is optional and has been filled out.

✅ Individual countries​

🆕 DisplayName in Create and UpdateStockLabel for Translations​

The CreateStockLabel and UpdateStockLabel services now include a DisplayName property.

This will allow for a proper translation flow that is based on the DispalyName property of those two services.

🆕 ProductBackendID in ListPriceListManualAdjustment​

The ListPriceListManualAdjustment service now includes a new ProductBackendID property.

🆕 GetCheckoutOptions filters​

The following filters have been added to the GetCheckoutOptions service:

• Name
• Handler
• Status (IsActive / Inactive)
• OU set

✅ Migrating gift card configurations​

EVA will from now on determine a gift card's balance based on gift card configurations in GetAvailableGiftCardConfigurations instead of GetApplicationConfiguration which will allow for taking the OU context into account.

🆕 Financial Period Verification Steps​

We've introduced three new settings that affect the verification process for opening and closing financial periods. These settings relate to updating organization unit location, linking loyalty programs, and linking employees. For instructions on how to enable these settings, click here.

✅ Default stock label for RTS​

To make EVA more efficient, any product added to an RTS order will automatically have its stock label set to the one defined in the Orders:ReturnToSupplier:DefaultStockLabel setting.

✅ Watchtower​

• Solved an issue that could cause DNS resolution to fail in case of network issues.
• Made the pulling of containers more reliable in case of network issues.
• Updated watchtower version to 2024.11.1 (prefix with your device model number)
• Pulling of updates is now spread across devices (in a 30-minute window) to avoid all devices pulling at the same time to improve network congestion

🆕 Shipment custom fields​

We've made changes to the ShipmentCustomfieldEligibility extension point to allow for making Shipment custom fields (in)visible for specific shipment types, such as Return to Supplier shipments.

extend ShipmentCustomFieldEligibility

            set output.IsVisible to false
            set output.IsRequired to false

            for each line in Shipment.ShipmentLines do //(checking each shipmentLine is necessary because in theory, a shipment can contain lines from multiple orders)
              line.Order.IsReturnToSupplier 
                set output.IsVisible to true
              end
            end

🆕 Bidirectional Supplier and Target OU Relationship​

We have recently added a new Mobile OU type, introduced in core notes 2.0.747. Expanding on this development, we've implemented a feature that enhances stock transfers between Shop and Mobile type OUs. The feature enables a bidirectional stock transfer between the supplier OU (Shop) and the target OU (Mobile).

This configuration differs from typical unidirectional supplier relationships by allowing a two-way flow of stock, specifically designed to support Mobile OUs. With this functionality, the Shop OU can both supply to and retrieve stock from the Mobile OU. This feature is active only when a supplier relationship between Shop OU type (as supplier) and Shop + Mobile OU type (as target) is configured, and the organization structure between the Shop and Shop + Mobile OU is a parent-to-child relationship. The bidirectional stock relation will trigger automatically if the OU structure involves a Parent OU of type Shop with a Child of OU type Shop and Mobile.

In such scenarios, sales transactions will use the AutoTransferInterbranchOrder service rather than the standard PlaceOrder.

Mind that this is part of an upcoming feature which is still in the works.

✅ Package selection fallback​

When no package is selected for a carrier which has packages configured, EVA will fall back on the package set as default.

✅ Updated GlobalBlue Printed Tax Forms​

GlobalBlue tax forms have been updated to include the following new fields:

• Till/StationID
• Employee's ID SISC (specific to Poland only; additional configuration required)
• Employee's First and Last Name (specific to Poland only)

A full sample can be viewed here.

• We fixed a short-lived issue where the UploadCouponExcel could not be done async.
• Resolved an issue where (cookbook)financial events would fail to process if a recipe's impacted account had a null value.
• We resolved an issue that caused incorrect refund calculations for return orders involving product bundles and product bundle discounts.

🆕 Introduced​

These deprecations are now announced for the first time. Usage of these services and/or fields will return the appropriate EVA-Warnings header.

High​

• Service ListCheckoutOptions is deprecated and will be removed in 2.0.781, use GetCheckoutOptions instead.
• High EVA.UserTasks.Services.CycleCounts.SetCycleCountSettings is deprecated and will be removed in 2.0.783: Use regular settings instead. SetCycleCountSettings

🚫 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.

Deprecated​

Highest​

• Highest Prices.BackendID is deprecated since 2.0.751: Use the External-IDs mode header and the ID parameter.
  • UpdateSimplePrices.Prices.BackendID
• Highest Prices.CustomID is deprecated since 2.0.751: No longer supported - switch to ProductID either with an (EVA) ID or a BackendID through the External-IDs mode header.
  • UpdateSimplePrices.Prices.CustomID
• Highest SkipPriceListRecalculation is deprecated since 2.0.751: This parameter will be removed and default to true, use ForcePriceListRecalculation if an immediate price list recalculation is required.
  • UpdateSimplePrices.SkipPriceListRecalculation

Medium​

• Medium Status is deprecated since 2.0.751: No longer used.
  • GetGiftCardOptionsResponse.Status

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.