Drop 77

🆕 Settings​

• Receive and complete RTS orders automatically after performing an RTS task by enabling Orders:ReturnToSupplier:AutoReceiveShipmentOnTaskCompletion in Core 2.0.758.
• Show the employee's choice of shipment receive method with Shipment:OverrideUserDefinedReceiveMethod in Core 2.0.758.
• Configure a Warehouse endpoint for RTS orders specifically with several new settings, since Core 2.0.755

🆕 Templates​

• Inform your customers that their repair product has been received safely with stencil template DeferredRepairReceived since Core 2.0.758.
• Add a VerificationCode to your PickupReminder stencil template, since Core 2.0.757.
• Display the UnitCost in a PackingSlip template, available since Core 2.0.756.

🆕 Store-specific active discounts​

• Upcoming! Soon our POS will be able to show employees a comprehensive overview of all currently active discounts in their store, being worked on since Core 2.0.757.

✅ Sign order as a requirement​

• Script your SignOrder checkout option to be a requirement, with the SignOrderRequirement since Core 2.0.757.

✅ EVA ID in PushUsers​

• Create and update users directly via the EVA ID since Core 2.0.755.

🆕 Added​

New Assessment Available on EVA Academy​

A new assessment focused on Pricing is now available.

Check all available assessments here.

Main Freeze Notification​

Please take into account Main freeze impacting the release timelines for Drops 78 & 79.

IP-whitelisting​

We have moved our translation catalogs deployment for our applications from this release onwards. This does require a change for the EVA urls you have whitelisted in your networks.

The following URL should be added to your whitelist:

• *.static.on-eva.app

For more information, refer to the IP-whitelisting documentation.

🆕 Added​

Counting non-cash payments​

POS now supports being prompted to count non-cash payment types when opening or closing financial periods. Read more here.

Mobile finance impediments​

We introduced a set of possible financial period closing impediments explicitly for organization units of type Mobile.

Payment Type grouping​

Payment Types that fall under the same Custom Payment Method can now be grouped in folders in checkout.

Order remark in overview​

When selecting an order in the Order Overview, we now also display the Order Remark.

Separate Loyalty and Regular Subscriptions​

We've introduced a new feature that separates loyalty linked subscriptions from regular subscriptions in the sidebar. This separation is visible during the basket, and when creating or editing customer profiles. Learn more about this feature here.

Financial period report​

We added several bits of information to the financial period reports under More Options.

✅ Improved​

Creating return orders​

We drastically improved the process of creating unreferenced return orders. Where before you would have to add all descired lines to an order - and then convert it to a return, converting lines to return lines now is independent of already existing return lines. We simply show the return button if there are non-return lines in the order, allowing you to convert these to return lines as you please.

Serial numbers for gift cards​

POS now also accepts scanning barcodes of type SERIALNUMBER when checking gift card balance or configuring a gift card number.

Serial numbers for regular products​

POS now also accepts scanning barcodes of type SERIALNUMBER for regular products.

Order line corrections​

We made improvements to the edit order functionality in POS. It's now possible to revert previously made order line corrections, and we take discounts into account when making the correction to the line.

Local Mode indication​

We improved our modal which shows when POS switches to local mode. We no correctly indicate which functionalities are definitely still available, and additionally we have add a section mentioning functionalites that are Possibly Unavailable.

Verify order requirement​

If you are running a script to check order validation based on the customer object, the corresponding Verify order checkout option tile will always be displayed in the POS' checkout.

Removing Fiscal ID or VAT number​

When having set a Fiscal ID or VAT number on an order, they are now also manually removable.

🔧 Fixed​

🆕 Added​

FindRepairCustomerViaSerialnumber​

By enabling the new setting FindRepairCustomerViaSerialnumber, you can add an additional option for attaching consumers to repairs:

• Add via Loyalty App
• Scan Product Serial Number

The latter, new option will ensure the consumer is attached to the repair if the scanned serial number corresponds to a consumer bought product.

✅ Improved​

Reservation cleanup tasks​

We are altering the logic for triggering refunds after a Reservation cleanup task, ensuring proper use of refunds.

Runner task scanning​

The Runner tasks scanning flow is now similar to the other scanning flows, such as for receiving goods. This means the scanner page will now display all scanned items and additionally allow for the scanning of new products. Using the scanner for a runner task will no longer make the scanned product pop up.

Shipping methods for SFS​

When creating a shipment for Ship from Store, the App will display only relevant shipping methods/carriers as based on the order type.

External label printers in SFS​

We've made some improvements for the use of external label printers in our Ship from Store flow.

When the setting ShipFromStore:ExternalLabelHandlerPrintType is set to 1 or 2, the printer selection display will no longer pop up. You can complete the task without selecting a printer.

Scanning received shipments​

Scanning shipments which have already been received, will no longer lead to "Shipment not found" errors. Instead it will either tell the user the shipment has already been received.

Receive goods calendar​

The Receive goods calendar section will now display expected shipments more clearly on a month-by-month basis along with when it was shipped exactly.

Swiping in Move Stock Batch​

The Move Stock Batch now also supports a swipe to delete action.

Minor change for SFS tasks​

Aside from making some back-end optimizations for Ship from Store subtasks, the following visual change is implemented:

• The text in the SFS Pick/Pack overview now states Start next task later instead of *Create Pack/Ship task Later.

Minor change for Repairs​

The Product Details screen, entered when tapping a product in the Repair's overview, now contains more information about the product and its warranty status (if available).

🆕 Added​

Reverse interstore orders (Receive)​

We now allow for reverse interstore orders within very specific contexts. Read more here

Payment Type grouping​

Payment Types that fall under the same Custom Payment Method can now be grouped in folders in checkout.

Required Custom Fields for Percentage and Amount Discount Action​

When applying a Percentage or Amount discount action, the requirement of "Required custom fields" (if configured) is now supported.

✅ Improved​

General Performance​

This release comes with a refactor in some of our data handling, improving overall performance.

Verify order requirement​

If you are running a script to check order validation based on the customer object, the corresponding Verify order checkout option tile will always be displayed in the Checkout App's checkout page.

🔧 Fixed​

🆕 Added​

Remark Field in Address Requirements​

We have added a new Remark field to the address requirements. By default, this field is hidden. It becomes visible in the edit/create customer flows when enabled. For instructions on how to update address requirements, see our Address requirement documentation.

Scanning Serial Numbers​

The Loyalty App can now recognize serial number scans that match any of your configured regular expressions. When a scanned value matches a configured serial number, the app automatically opens the detail view of the purchased product within the user's profile. If there is no match, the app will populate the search field with the scanned barcode data.

Preferred Label for User Requirements​

A preferred label now appears on User Requirements set to Display Type: Preferred.

Related Repairs Card​

We've added a new card to the Cases details section called Related Repairs. This card shows repairs linked to the case.

More on this here.

✅ Improved​

Case Topic Translations​

Case topics now support translations in the Loyalty App, based on the user's preferred language.

User Requirements - Preferred Label​

When a user requirement is set to Preferred, the "Preferred" label will appear in the title field of that requirement.

Split Subscriptions​

The app now adheres to the Subscriptions:SplitUserSubscriptions setting to display and list subscriptions and loyalty programs. These appear in the customer details overview and the sidebar list of active subscriptions and programs. Learn more about this setting here.

Warranty Badge​

If a warranty is applicable to an item, a warranty badge will be visible in the following areas:

🔧 Fixed​

🆕 Added​

UI Improvements in Admin Suite​

We are progressively rolling out UI enhancements to the Admin Suite across various modules, expected to continue until Drop 80. These updates will include:

• Improved design and clarity of headers, footers, and buttons on pages and modals.
• More concise and clear instructional text.
• Refreshed filter sidebars.
• Capitalized chapter titles.
• Titled cards in chapters with multiple tabs.

These updates will not alter existing features unless explicitly noted in a separate drop note under the impacted module. We are implementing these changes primarily to improve overall consistency and user experience.

A notification will appear on the Admin Suite main dashboard, providing more details about the UI update. Up until this release, the following modules have been impacted:

The chapters that have received UI enhancements in this drop include:

Main Freeze Notification​

Please take into account Main freeze impacting the release timelines for Drops 78 & 79.

Link to Admin 1.0​

The "Need the old admin? Click here" link, found at the bottom of the Admin Suite overview page, will be accessible until February 3, 2025 (Drop 80), extending the original deadline of August 19, 2024 (Drop 75). This extension allows us to incorporate additional feedback.

For more information on the Admin 1.0 switch off process, visit this page.

Remark Field in Address Requirements​

We have introduced a new Remark field to the address requirements. By default, this field is hidden and will only appear in specified flows when enabled. For instructions on how to update address requirements, see our Address requirement documentation.

When enabled, the Remark field becomes visible in the following scenarios:

• While adding or editing an address in the Consumer details page.
• During address add/edit in the Ship from Store detail pages, applicable to all task subtypes.
• When adding/updating a consumer address from the Cases details page.
• In the address add/edit modal on the Organizations page.
• While editing or adding addresses in Companies chapter.

Displayed Product ID Settings​

The scope of the App:CustomerProductValue setting has expanded. For a complete list of affected areas when using this setting and additional details, please refer to the Product ID documentation.

Display of Backend ID on Organization Unit Sets​

The Backend ID of Organization Unit (OU) Sets will now be visible under the OU set name in relevant chapters of the Admin Suite (if one is available). Should a Backend ID be unavailable for an OU set, the OU's Backend ID will be shown instead.

✅ Improved​

Product Type filters​

With the introduction of limit on results from GetProductPropertyType, product property filters no longer allowed for selecting any property that would be returned in the results beyond 50. To fix this, we implemented a search list field everywhere product property types are used like this.

Field "x" Icon Removal​

The "x" icon used to clear field inputs was deemed unnecessary across various fields and across multiple chapters. As a result, it has been removed from multiple locations.

🔧 Fixed​

🆕 Added​

Address Requirements Chapter​

A new chapter called Address Requirements has been added. More information on what can be done using this chapter can be found here.

✅ Improved​

Assembly Name Based on Device Type​

When adding or editing a device, the Assembly Name field automatically updates to show options relevant to the chosen Device Type.

Support for multiple values in Settings​

We have improved the way we display multiple values when adding settings.

🆕 Added​

More information for closed financial periods​

The Financial periods chapter now includes three new tabs for Closed financial periods.

• Bookkeeping
• Payments
• Corrections

✅ Improved​

Invoices​

While the entire Invoices chapter has undergone a visual improvement, we've made a functional change to its filter in that it now has more suitable selection fields for both Organization units and Suppliers. These allow for selecting multiple OUs or suppliers respectively.

🔧 Fixed​

🔧 Fixed​

🆕 Added​

Consumers Chapter Updates​

A few updates have taken place on the Consumers chapter, as follows:

• The tab called Personalized promotions has been renamed to Loyalty.
• The Subscriptions card that existed on the General Information tab has been relocated to the new Loyalty tab.
• The cards dispalyed within the new Loyalty tab is impacted by the setting Subscriptions:SplitUserSubscriptions.
• The option to subscribe / enroll consumers.

More on this setting and detailed docs reflecting these changes can be found here.

✅ Improved​

Loyalty Program Management via Subscriptions​

The LoyaltyProgram handler is no longer available in the dropdown when managing subscriptions. Loyalty programs are now managed via a separate, dedicated flow. For configuration details, refer to the Loyalty Programs documentation.

Grayed Out Organization Units in Dropdown​

When an organization unit (single or set), is selected for an employee under their permissions card, it will appear grayed out in the dropdown list for any subsequent Add permissions attempt(s).

Fixed Header in Roles and Rights Table​

As you scroll through the Functionalities card, the column headers will now stay fixed at the top.

🔧 Fixed​

🆕 Added​

Required Custom Fields for Percentage and Amount Discount Action​

Required Custom Fields on a Percentage or Amount discount action is now available. The custom fields usable on this discount action are of type Order.

New Quantity Limit Fields on Loyalty Programs​

We've added two new fields to the Loyalty Programs configuration options: Overall quantity limit per order and Overall quantity limit per user. These fields are optional and can be found under Payment Types and Product Limitations.

Enable Partial Payment Option for Payment Types in Loyalty Programs​

A new field, Allow Partial Payment, has been introduced when configuring payment types within a loyalty program.

🔧 Fixed​

✅ Improved​

Content Culture selection​

When selecting a specific content culture in the Content Preview in the Products Chapter, we now only return a selection of content cultures that are available to the Organization Unit the user currently has selected. If the selected OU is the root OU, we will return all available content cultures.

🔧 Fixed​

🆕 Added​

UnitPriceInTax​

While we already recently introduced a new column in the Stock overview called Sales price, we're now expanding this with the new optional column Sales price including VAT.

RTS-able​

You can now expand the list of stock locations from which you can return items to suppliers by assigning them the recently introduced Return to supplierable feature via your Stock locations chapter.

🔧 Fixed​

🔧 Fixed​

✅ Improved​

Pending payments​

When using a payment method which relies on some sort of 'pending state' (e.g. Multibanco in PT), EVA Pay will now reflect on the checkout page whether any payments are already pending.

Additionally, for Multibanco specifically, we disabled the back button after having selected it as a payment method to prevent the user from navigating back and adding extra payments, potentially causing overpayment.