Breaking
No breaking changes.
Compliance
🇦🇹 Austria
The Certified invoice stencil for Austria can now include the following properties:
- Totaler Rabatt
- (Total recommended retail price - Total current price) + Other discounts
- Sie Sparen
- This matches the total discount amount
🇵🇱 Poland
- Resolved a bug that caused synchronization failures with the Exorigo printer in Poland due to a character limit in the fiscal receipt footer.
🇵🇹 Portugal
- Fixes and improvements made to SAF-T files generation.
🇪🇸 Spain
✅ Certified Invoices for Catalunya
For organizational units located in Catalunya using the Certified Invoice Template for Spain, certified invoices will feature translations distinct from those used in other Spanish regions. Below are the specific translation differences:
| Term in Spanish | Translation in Catalunya |
|---|---|
| Artículo | Article |
| P. unitario | P. unitari |
| Duplicado | Duplicat |
| Total sin IVA | Total sense IVA |
| Tipo de IVA | Tipus de IVA |
| Importe del IVA | Import del IVA |
| Pagado | Pagat |
| Cliente | Client |
| Productos | Producte |
| Líneas | Línies |
| Cash | Efectiv |
| Versión del software | Versie del software |
| Empleado | Empleat |
| Código terminal | Codi terminal |
Properties
🆕 PrintCreateRepair template
To make the use of properties in the PrintCreateRepair template more consistent, we've made some slight changes.
Details
- Added the Repair model to PrintCreateRepair template
- Added SerialNumber and **SerialNumberID to the same model
🆕 LoyaltyProgram in scripting
The following extension points have been updated to allow for the use of the LoyaltyProgram:
- CheckoutOptions
- OrderCustomFieldEligibility
- OrdersMonitor
Sample
extend OrderCustomFieldEligibility
if Order.LoyaltyProgram.BackendID = 'BigOnLoyalty1' then
set output.IsRequired to true
end
🆕 Customer's BackendID in GetCaseByID
To make for more efficient case management via API, EVA now includes the customer's BackendID in the GetCaseByID response.
✅ Limiting Case titles
Case titles are now limited to 255 characters.
Services
✅ Errors for failed Digital Giftcard creation
If the creation of Digital Giftcard fails, ShipOrder will now return a more specific error message for improved clarity.
Details
The error will take the following form:
Message: "Failed to execute the action Activate for orderline xxxx"
Type: "GiftCards:ActionFailed"
"Code": "EQHQHYDQ"
✅ Migration from UserInteractions to Interactions
Currently EVA works with two different models when it comes to Cases, Repairs and User communication, namely both UserInteractions and Interactions. To make this work more efficiently, we're migrating from UserInteractions to solely Interactions.
This has no further impact, as all CRUD services for UserInteractions will continue to work as expected as well all event exports and stencils.
✅ Registering EVA Pay emails as interactions
EVA Pay emails which are sent out, will now be stored as an interaction on the user. This also entails they can now be fetched by means of a ListUserInteractions call.
Settings
✅ Changes to the in-store return flow
In Core 2.0.732 we laid the groundwork for an improved in-store return process for such cases where a webshop and a retail store belong to different companies (with different tax IDs).
We've now made made a few more changes and made the new return flow the default flow - but with a setting allowing for potential opt-out.
Details of the new return flow
- New Return Order Creation: Previously, a return order would be created by the retail store. With the new setup, the return order will be created by the Webshop OU.
- Payment Method Requirement: This process is applicable only for orders paid with an auto-refundable payment method.
- Credit Invoice Handling: The webshop will facilitate the generation and sending of the credit invoice.
- This behaviour is enabled by default, but can be disabled using the setting
UseSpecialInStoreReturn.
Fixes
- Assortment Data lake exports could be duplicated.
- EVA will prevent custom field duplicates when updating users and, additionally, calling
UpdateUserwith multiples values for the same custom field now displays the appropriate error code. - Fixed an error where physical receipts could be sent out as an e-receipt.
- Searching by means of the EmailAddress will now automatically turn the input into lower case to prevent issues with findability.
- When a Custom field on a Case is updated, a webhook event will now be properly triggered.
- Shipment Data lake exports will now be triggered upon shipment delivery, shipment receipt and expected delivery date update.
Deprecations
⚡ Removed from typings
These deprecations are now halfway through their deprecation timeline. As of now, these services and/or fields will no longer be exposed by our typings.
Setting
- Highest ReturnableStockOrganizationUnitReasonsSettings:SoldFromOrganizationUnitEnabled is deprecated and will be enforced to True from 2.0.777: Temporarily created to allow for Swift typings backporting.
For more details on the impact categories, please see When are changes communicated?.
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.