Core 2.0.738

Context: We intend for each setting to be linked to a specific functionality within EVA. This ensures that only designated roles will have the ability to modify certain settings, allowing for more precise control over your environments.

Example: For instance, the setting APIGiftCard:BaseUrl will be associated with the functionality named GiftCardConfiguration.

Implementation Plan: Given the extensive nature of EVA's settings (approximately 1500 in total), we will be rolling these out in batches, once every EVA Drop - effectively once every four weeks. The first, second and third batches of these adjustments have already been included in EVA Core drop 2.0.726, 2.0.730 and 2.0.735.

Timeline: This new batch of changes is now available on your Test and Acceptance environments. These changes will be deployed to Production environments next week with EVA Core drop 2.0.739 (May 28). We anticipate completing this process over approximately 5 more EVA Drops until all settings are included.

Action Required: We encourage you to review this batch of settings, which are already documented on our Docs. Ensure that the roles assigned within your organization align appropriately with the functionalities necessary for access to these settings.

Anti money laundering​

To adhere to the money laundering rules for the UK, EVA will be triggering customer requirements for sales with over 10.000 GBP in the order basket.

The following fields will then become mandatory:

• First Name
• Last Name
• Address 1
• Zip / Postal Code
• City
• Country
• Nationality
• Date of Birth
• (Optional) Phone number

The default payment transaction model, as received via GetPaymentTransaction for example, optionally shows a Data element if the following conditions are met:

• You are an API type user
• And you have the functionality PaymentData (scope View)
• And the payment method explicitly maps data for visibility (by default, none are visible)

In case of Adyen payment methods, the following properties can be displayed in the element:

• AuthCode
• MerchantAccount
• MerchantReference

The API key will no longer be returned in the following services:

• GetDevice
• WatchtowerGetDeviceDetails
• ListWatchtowerDevices
• WatchtowerGetDeviceByHardwareID

The addition of:

• nullable CreationTime and LastModificationTime to ListFullStockCountLabelProductDto;
• IncrementQuantity to AddProductToFullStockCountLabel;
• Product model to AddProductToFullStockCountLabel's response`, which comes with the following properties:
  • ProductID
  • BackendID
  • CurrentCountUserID
  • PreviousQuantity
  • PreviousCountUserID
  • Properties
  • Quantity
  • CreationTime LastModificationTime

The use of manual codes in Magic links is only enabled when the new setting MagicLink:AllowManualCode is set to true.

Afterwards, a new property called IncludeManualCode (which defaults to null) can be set to true to have the email sent with a short code for users to manually input into your application.

A new service called ConfirmMagicLink can then be called with both the RequestToken and the ManualCode to obtain either the TemporaryToken or ApiKey when the values are valid - which is the same flow as before.

This setup honors all previous integrated MagicLink flows and scenarios. Front end work is still underway.

• RequiredData:MaximumOrderAmount
• RequiredData:MinimumOrderAmount

If an amount is specified in either, then those values will become exposed in GetShoppingCart and GetOrder as order requirements. In practice this means an order cannot be placed below nor above the specified value.

Note: The minimum and maximum values include any discounts and exclude shipping costs.

This means that when using a relevant service, such as CardBalanceCheck, for a giftcard provider using the APIGIFTCARD configuration, the corresponding endpoint will return the following new properties:

• BaseUrl/card-info

• BaseUrl/purchase

• BaseUrl/refund

  • DateOfPurchase
  • DateOfExpiration
  • Expired:true/false

• BaseUrl/activate

• BaseUrl/issue

  • DateOfPurchase
  • DateOfExpiration

These properties (when applicable) will then be returned in the response of your service call.

Additionally, these properties are now usable in the following stencils:

• ThermalReceipt
• CertifiedInvoice
• GiftCardOrderShippedConfirmation
• OrderShippedConfirmation (orderline)
• DigitalGiftCardMessage
• DigitalGiftCardSenderMessage
• DownloadDigitalGiftCard

The file path for this new export: EVA/{region}/repairs/{date.Year:0000}/{date.Month:00}/{date.Day:00}/{id}

This export is available by default - no need to schedule a new task.

  {
  "ID": "",
  "OrganizationUnitID": "",
  "AssignedUserID": "",
  "ReceiveMethodID": "",
  "ExpectedArrivalDate": "",
  "CaseID": "",
  "ProductID": "",
  "OrderLineID": "",
  "RepairOrderID": "",
  "SerialNumber": "",
  "StatusID": "",
  "ShippingOptionID": ""
}