Core 2.0.713

🔑 Core drop notes structure​

In our continuous effort to make our Core Drop more easily digestible, we've made the following changes to its format:

• We try to categorize all drop entries as best we can by the closest common denominator, e.g. Extension point entries, or Services. This will make it a little easier for you to discern what's important to you.
• Although the difference can be subtle, we try and categorize the entries on whether they're new additions 🆕 or improvements ✅
• The introductory text for each entry will be more concise, with Detailed information available via the Expansion bar.

No breaking changes.

🆕 Properties in EventExport extension point​

The extension point EventExport now has two additional properties available for use in its script:

• Order.SoldToOrganizationUnitID
• Order.Type

By using these properties you can indicate to export the event or not based on if an order was shipped from store.

extend EventExport
    
     set export to false 
     
     if Order.SoldToOrganizationUnit.Type = 'Shop'
     then set export to true 
  end 
  
  output export

🆕 Properties to differentiate orders in extension points​

We have introduced two new properties to specific extension points to help differentiate between the two:

• Order.SoldFromOrganizationUnit.IsShop
• Order.SoldFromOrganizationUnit.IsWebShop

By using these properties, you can indicate whether it is a store order or a webshop order.

These properties are autocompleted in scripts extending types ReturnableStatus, OrdersMonitor, OrganizationUnitCustomFieldEligibility, OrderCustomFieldEligibility, and StockNotification.

extend ReturnableStatus

if Order.SoldFromOrganizationUnit.IsWebShop then  

// Condition

end

🆕 ShowMessage in BarcodeResult extension point​

We've added an additional action to the possible results when parsing barcodes via the BarcodeResult extension point.

This action, called ShowMessage, will allow you to display a custom message upon scanning a specific barcode format.

For samples, please see Sample scripts.

✅ Handling conflicting outputs in ReturnableStatus extension point​

The ReturnableStatus script now better handles conflicting results.

🆕 Repair task subtype: Pickup​

We've added a new subtype for the Repair task: Pickup. This new type will only be created when the setting called UserTasks:EnablePickupRepairUserTasks is specifically set to true.

For more information, see Pickup.

🆕 Repair is ready: Templates​

We've added two new templates for messaging your customer the repair is ready and will either be shipped or can be picked up. You can use RepairShipped and RepairReadyForPickup respectively.

The former is triggered whenever a shipping method is not pickup and its open amount is zero, while the latter is sent whenever a repair is ready and indicated to be picked up (see also the entry above).

🆕 Foreign currency and auto confirm​

A few payment parameters, namely ForeignCurrencyID, ForeignAmount, and AutoConfirm have been added to the PushSalesOrder service under the order Payments object.

🆕 Color coding for custom statuses​

We've done the back-end work for assigning a color to a custom order status by adding the Color property to CreateOrderCustomStatus.

The available options will be: grey, green, yellow, blue, red and white. You will soon be able to specify these colors when creating or updating custom order statuses in Admin Suite.

🆕 Currency on purchase order lines​

A new property Currency has been added to the AddPurchaseOrderLines service.

The addition has been made to accomodate scenarios where the currency of the organization unit receiving the purchase order is different from the sender i.e. resulting in proper cost calculations. The applied conversion rate will be based on the currency conversion rate specified in the OU if configured. Alternatively, the rate applied will be based on the real time rate pulled from Fixer.io.

🆕 LayerID of the attached discount​

The PrefigureDiscountResult, available on the response of both SearchProducts (-> SearchProductsOptions) and PrefigureDiscounts, will now return the LayerID of the attached discount.

This will allow you to check at a glance if a discount's requirements were met, but when the discount wasn't applied because of another discount's application within the same layer.

✅ Showing products affected by discounts​

The property EligibleProductIDs in the response of the PrefigureDiscounts call now shows the affected products.

✅ TotalAmountInTax in invoices​

Invoices now use the TotalAmount from the invoice lines instead of the order lines.

This means the TotalAmountInTax now matches the UnitPriceInTax * QuantityInvoiced on (non-certified) invoices

🆕 List settlements service​

A new service called ListPaymentTransactionSettlements has been added to list all settlement transactions.

🆕 ListBlobsForStencils​

We've added a new service called ListBlobsForStencils.

This will be used to replace ListBlobs (which is slated for deprecation in C2.0.722 (2024-01-02)) and will filter on blobs with the category "template_media".

✅ PushUsers_Async​

The service PushUsers_Async can now optionally accept any user entries which are correct, while displaying those entries resulting in errors. Set IgnoreErrors to true to make use of this.

✅ Promotion visibility for partners/franchisers​

We now ensure stores cannot see/interact with discounts from stores they don't have rights to. This is based on users' visibility groups and their edit rights on the OUs connected to the discount.

For more information, expand the following section.

✅ Fallback destination for certain templates​

Even when you have no AsyncRequestCompleted templates configured on your environment, EVA will now send you the necessary (standard) email messages regardless. These are emails for Stock replenishment downloads for example.

✅ Handling deleted users with async processing​

We now impersonate deleted users in edge cases where async processing would fail due to a user having been deleted in the meantime.

🆕 Asynchronous calls to RT server in Italy​

In Italy, the option to perform asynchronous calls to the RT server during the checkout process is now available by means of a setting called UseAsyncSigning. More on this here

✅ Logic for preselecting OU for returns​

We've altered the logic for prefilling the return OU field in Admin Suite: EVA can now optionally prefill the field with the OU the employee is currently logged into.

✅ Pincode synchronization​

We've improved the way the setting LoginWithIdentificationPin:Method handles your chosen PIN method. This will solve an issue where the pincode would be forgotten when restarting the Suite Apps.

• The recent changes to prettify (return) order export responses from Arvato needed a fix to work properly.
• CreateZonedCycleCounts would not return a result in Created or Updated whenever this was called through the async-message process.
• Fix broken ListUserRequirements query with UserType filter.
• Properly allow for deleting an unused role set.
• Filtering stations by DeviceType should only show stations with a non-deleted device of that type.
• Creating a Cash expense will no longer lead to the event exports sending out an event with ID 0.
• We fixed an issue where AvailableShippingMethods would sometimes respond that a customer would have to pay a shipping cost, while they shouldn't.
• We fixed an issue where employees did not receive the assigned functionalities when they logged in at stores within Visibility Groups through SSO.
• PrintFullStockCountLabels will no longer return "Unable to find a device".

  this was due to ListStationsForOrganizationUnit returning stations without a thermal printer

• ListPriceListOrganizationUnits will now properly return the OUs for the price list.

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

Deprecated​

Medium​

• Medium ID is deprecated and will be removed in 2.0.721: Replaced by InvoiceExportIDs so that multiple invoice exports can be retried at once..
  • RetryInvoiceExport.ID

Required​

Medium​

• Medium Field InvoiceExportIDs is required and will be enforced as such in 2.0.721.
  • RetryInvoiceExport.InvoiceExportIDs

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.