Core 2.0.762

Security settings​

Security settings have been grouped and now all require a new (unscoped) functionality Security, which is not automatically granted when this release hits.

While this will not impact your current setting configuration, for future changes your environment administrators will have to manually attach this new functionality to the corresponding roles authorized to make calls on application security in your organization. Please note that support is available: if you are unsure, you can request New Black to assist you.

✅ Watchtower improvements​

We have made the following two general improvements to Watchtower:

• Improved resiliency for IO or LiveGuard not starting up.
• Made the image pulling process more robust.

✅ CreatedByID​

You can now view all employee IDs involved in a sale, including those who created the order, added/sold products and who completed the sale. This ensures accurate tracking of contributions for commission purposes.

{
    "PaymentTransactions": [
        {
            "ID": 42522,
            "CreatedByID": 703,
            "DeviceID": 182,
            "OrderID": 76289,
            "PaymentDate": "2024-11-01T16:00:36.577Z",
            "Amount": 25.0000,
            "Status": 10,
            "IsConfirmed": true,
            "PendingOrConfirmed": true,
            "PaidAmount": 25.0000,
            "PaymentName": "Cash",
            "Change": 0.0000,
            "TypeID": 9,
            "Type": {
                "Code": "CASH",
                "Name": "Cash",
                "IsRoundingType": false,
                "PrintOnDocuments": true
            },
            "CurrencyID": "EUR",
            "ExchangeRate": 1.0,
            "Description": "Cash",
            "SettledAmount": 0.0000,
            "IsSettled": false,
            "RequiresCapture": false,
            "CaptureMoment": 0,
            "HasDispute": false,
            "HasUnresolvedDispute": false,
            "IsRefund": false,
            "IsAuthorizationAdjustment": false,
            "IsAuthorizationExpired": false,
            "AvailableActions": {
                "Cancel": false,
                "Refund": false,
                "Update": false,
                "Approve": false,
                "Capture": false
            }
        },
        {
            "DeviceSerialNumber": "P400Plus-27547",
            "ID": 42523,
            "BackendID": "DKG7RTVQN82",
            "CreatedByID": 1700,
            "DeviceID": 144,
            "OrderID": 76289,
            "PaymentDate": "2024-11-01T16:01:12.393Z",
            "Amount": 30.2300,
            "Status": 10,
            "IsConfirmed": true,
            "PendingOrConfirmed": true,
            "PaidAmount": 30.2300,
            "PaymentName": "PIN",
            "Change": 0.0000,
            "TypeID": 3,
            "Type": {
                "Code": "PIN",
                "Name": "PIN",
                "IsRoundingType": false,
                "PrintOnDocuments": true
            },
            "CurrencyID": "EUR",
            "ExchangeRate": 1.0,
            "Description": "PIN",
            "SettledAmount": 0.0000,
            "IsSettled": false,
            "RequiresCapture": false,
            "CaptureMoment": 0,
            "HasDispute": false,
            "HasUnresolvedDispute": false,
            "IsRefund": false,
            "IsAuthorizationAdjustment": false,
            "IsAuthorizationExpired": false,
            "AvailableActions": {
                "Cancel": false,
                "Refund": false,
                "Update": false,
                "Approve": false,
                "Capture": false
            }
        }
    ]
}

✅ PrimaryProductIDs / RelatedProductIDs​

To accommodate large product sets and and the exposing of group relations, we are refactoring the ProductRelations services.

 // Unidirectional relation between product 1 and products 2, 3. Note that Bi-directional is similar.
// From
 "Relations":[
    {
       "PrimaryProductID":1,
       "RelatedProductID":2
    },
    {
       "PrimaryProductID":1,
       "RelatedProductID":3
    }
 ]

// To
 "Relations":[
    {
       "PrimaryProductID":1,
       "PrimaryProductIDs":[1],
       "RelatedProductIDs":[2, 3]
    },
 ]

 // Group relation for products 1, 2, 3, queried for product 1.
 // From the previous implementation response

 "Relations":[
    {
       "PrimaryProductID":1,
    },
 ]

 // To
 "Relations":[
    {
       "PrimaryProductID":null, // No primary product, they are all related to each other
       "RelatedProductIDs":[1, 2, 3]
    },
 ]

 // Instead of
 "Relations":[
    {
       "PrimaryProductID":1,
       "RelatedProductID":2
    },
    {
       "PrimaryProductID":1,
       "RelatedProductID":3
    }
 ]
 

🆕 DownloadStockOverview​

We are introducing a new service for the purpose of downloading large stock overviews: DownloadStockOverview

🆕 Access Foreign Card Data in GetOrder API​

You can now access foreign card data for Dynamic Currency Conversion (DCC) transactions through the GetOrder API.

This update allows you to view original currency amounts, foreign currency payment amounts, and exchange rates for transactions involving foreign cards.

{
    "PaymentTransaction": {
        "ID": 4200,
        "BackendID": "P6FLNK",
        "DeviceID": 144,
        "OrderID": 75620,
        "Data": "{\"AuthCode\":\"123456\",\"MerchantAccount\":\"NewBlackPOS\",\"CurrencyConversions\":[{\"Amount\":14.31,\"Rate\":1.4309,\"CurrencyCode\":\"SGD\"}],\"MerchantReference\":\"EVA-70-42\"}",
        "PaymentDate": "2024-10-29T15:52:58.47Z",
        "Amount": 10.0000,
        "Status": 10,
        "IsConfirmed": true,
        "PendingOrConfirmed": true,
        "PaidAmount": 10.0000,
        "PaymentName": "VISA",
        "Change": 0.0000,
        "TypeID": 258,
        "Type": {
            "Code": "VISA",
            "Name": "VISA",
            "IsRoundingType": false,
            "PrintOnDocuments": false
        },
        "CurrencyID": "EUR",
        "ExchangeRate": 1.0,
        "Description": "PIN",
        "SettledAmount": 0.0000,
        "IsSettled": false,
        "RequiresCapture": false,
        "CaptureMoment": 0,
        "HasDispute": false,
        "HasUnresolvedDispute": false,
        "IsRefund": false,
        "IsAuthorizationAdjustment": false,
        "IsAuthorizationExpired": false
    }
}

✅ PushReturnOrder​

The following change is introduced as part of a bigger development - this feature is not ready for use

We've extended the PushReturnOrder service with two new properties to allow for creating return offer orders:

• IsOffer -> optional boolean which defaults to false.
• OfferExpirationDate -> nullable dateTime. If not provided, the default value from a setting (which is still upcoming) will apply.

🆕 Serial number support for CompleteReservationCleanupTask​

Serial number support has been added for the CompleteReservationCleanupTask, enabling the functionality to provide or withhold serial numbers based on requirements.

🆕 PushLoyaltyPrograms​

To allow for pushing multiple Loyalty programs at once, we are introducing the following service: PushLoyaltyPrograms.

{
  LoyaltyPrograms: [{
    // ... same as PushLoyaltyProgram
  }],
  DisableEventExports: true,
}

// Response
{
  SuccessfullyAdjustedLoyaltyPrograms: [{
    ID: 1
  }],
  FailedToAdjustLoyaltyPrograms: [{
    BackendID: "some-lp-bid",
    ErrorIdentifier: "LoyaltyPrograms:CannotUpdateConditionType"
  }]
}

✅ GetAssemblyNameForDeviceTypes​

You can now see the assembly name Upos810T as an option when creating or editing a Cash Drawer or Fiscal Thermal Printer in the Admin Suite.

🆕 Anonymous access​

Access to anonymous services can be managed through a new setting: AllowEcommerce.

This new setting defaults to true, but when set to false it will revoke all public access to all anonymous EVA services.

This can be used in scenarios where your use of the EVA platform is limited only to in-store transactions. However, even in that scenario, some services need to remain publicly available, like Login and ResetUserPassword. Those services have therefore been split off and are listed as "public" instead, and as such remain unaffected by the above setting.

So, hence forth, EVA distinguishes between two types of public services; "anonymous" and "public".

✅ Security settings​

The defaults of some settings have been adjusted to enhance security.

While existing environments will have their current values inserted into their database through a migration, ensuring they are not affected by this change, we would like to remind you that setting the following values will result in a more secure environment:

• Security:RequireExternalLoginFunctionality now defaults to true
• Security:UseContextIndependentFunctionalityChecksAndFiltering` now defaults to true
• SignalR:ClientAppHub:LimitOnIPAddress now defaults to true
  • This new setting ensures the CFD, POS and remote barcode scanner, as well order and session transfers can only run within the subnet of the OU.
• Security:AllowLoginWithApiKeys now defaults to false
• MagicLink:Enabled now defaults to false

Additionally, some legacy settings were cleaned up in the process:

🆕 More DataLakeBackfill types​

We are adding the following new types to the DataLakeBackfill service:

• Stock mutations
• User Tasks
• ZonedCycleCounts
• Shipments

🆕 Voucher Printing Functionality​

The following change is introduced as part of a bigger development - this feature is not ready for use

We're laying the groundworks for printing vouchers directly from your orders, making it easier to manage and distribute promotional coupons.

🆕 Updates to Data lake packages​

We're extending the following Data lake packages with a few new properties:

• ZonedCycleCounts
• UserTasks
• Orders
• Stock

✅ OU Subnet input​

EVA now prevents you from entering faulty subnets for OUs (which could break the Login flow).

• Fixed an issue with the AutoShip feature for Tap to Pay payments.
• We fixed an issue when accessing cases with deleted parent topics.
• We addressed two issues which could cause cycle counts with multiple products to not be created.
• EVA now displays the right error result for a failed PushCompany attempt.
• Loyalty program users were incorrectly allowed to purchase more than one product at a subscription price despite a QuantityLimitPerUser setting.
• The tax table was not being populated in the GetOrder function for exchange orders when the total amount was zero.

🆕 Introduced​

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

Deprecated​

High​

• High DownloadOverview is deprecated and will be removed in 2.0.794: Use DownloadStockOverview instead.
  • ListStockForOrganizationUnits.DownloadOverview
• High PageConfig.Filter.BackendID is deprecated and will be removed in 2.0.794: Use ProductIDs instead.
  • ListStockForOrganizationUnits.PageConfig.Filter.BackendID
• High PageConfig.Filter.Barcode is deprecated and will be removed in 2.0.794: Use ProductIDs instead.
  • ListStockForOrganizationUnits.PageConfig.Filter.Barcode
• High PageConfig.Filter.CustomID is deprecated and will be removed in 2.0.794: Use ProductIDs instead.
  • ListStockForOrganizationUnits.PageConfig.Filter.CustomID
• High PageConfig.Filter.ProductID is deprecated and will be removed in 2.0.794: Use ProductIDs instead.
  • ListStockForOrganizationUnits.PageConfig.Filter.ProductID

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.