Onventis 2023.3

The new shop cart

We are currently working on a new user interface for our shop cart. Since the last release you are able to test the BETA version of the new shopping cart and provide feedback. Here you can read about the latest updates to the new shopping cart (BETA).

With a new  look & feel the new shop cart offers are a more intuitive usability with many more interesting features and improvements yet to come. Currently the new shop cart is in BETA status, hence some features that you might use may not be implemented yet. Therefore, you will be directed to the old shopping cart by default, that still offers all functionalities that you are used to.

Please be aware that the new and the old shopping cart have the same basis, every change you make in the new shopping cart will impact the old shopping cart and vice versa.

Shopping Cart – Default

We would like to inform you that with the Release 2023.5 the new shopping cart will be the new default, when you open the shopping cart. However, you will still have the possiblity to switch and work with the old shopping for anticipated two releases (2023.5 and 2023.6)

Shopping Cart – Performance improvements

We implemented performance improvements, in order to offer a more smoother user experience when working with the new shopping cart and filling information like supplier, cost allocation information or material groups. 

Shopping Cart – Position layout

We changed the layout of shopping cart positions. Now only one panel per line is displayed. Information per panel are displayed in two blocks.

All panels are expanded by default. If the user decides to manually collapse a panel, this decision is saved, so the user does not have to repeat this action.

Further, with the drag icon in the right hand corner, panels can be moved and arranged according to the user’s preferences. This arragement is also saved for the user.

Shopping Cart – Highlight missing mandatory information

In case the shopping cart position contains missing mandatory information we now show a red exlamation mark icon in the shopping cart checkout. When you hover on this icon, the number of invalid shopping cart positions are shown. 

When you click on this icon, you are directed to the first shopping cart position with missing mandatory information.

The red exclamation mark icon is also shown directly next to the shopping cart position. When you hover on this icon here, all missing mandatory information are listed. 

Shopping cart – Inheritance Page

We now group the information to be inherited on the inheritance page, so the necessary information can be found and inherited in an easier and more efficient way.

How to give feedback?

Feedback is the key to improvement.

You have feedback for the new shopping cart that you would like to share with us? We appreciate your feedback on the beta version of the new shopping cart. You can share you thoughts about the new shopping cart (BETA) by clicking on the “Feedback” button on the right hand side of the shopping cart. When you do so, a modal opens where you can tell us what you like or dislike about the new shop cart, the reasons for your decisions and other valuable information.

Additionally you can share your thoughts here, by filling the form below.

All data is collected anonymously unless you choose to provide your email address in question 3 of the feedback form.

We are looking forward to your feedback!

Organisational unit specific transaction template

We now offer the possibility to define transaction templates per organisational unit. To do so, you have to navigate to Configuration, Section “Templates”, select “Transactions” and map an organisational unit to a transaction template. You can configure each transaction template in multiple languages. It is only possible to map a transaction template to one organisational unit. During configuration, you will only be able to select those organisational units that have not been mapped yet.

Please note, the first selected and configured input language in the organisational unit specific transaction template is the fallback language that is taken for the Order PDF if the transaction template is not configured in the supplier’s language. For example, if the supplier’s language is french but the transaction template is configured in french, the header and footer text is displayed in the language, the transaction template was first configured in e.g. English.

If you don’t want to set up transaction templates per organistional unit, nothing changes for you. The organisational wide transaction template will be taken as a default.

If configured, the header and footer text configured in the transaction templates will be shown in the purchase order (and Order PDF) and in the sales order.

Supplier E-Mail on PDF

We have adjusted the PDF so that now also the E-Mail of the supplier is part of the order / order change PDF.

Tax rate on PDF

In case the tax rate is configured to be shown on the order PDF, we now also display a + in front of the tax, to better highlight, that the tax is added on top.

Customs declaration will be set to required as default in shopping cart if setting is active

Given the organisational setting is active “Customs declaration” requirement as standard” (Tab “General” section “Settings”) the checkbox “Customs declaration required” will be checked automatically in the shopping cart for free-text positions.

Up to now this setting was only considered for order line items.

Service Note Export

A new access right was introduced, that must be activated to enable the user with the related user role to export the service note list. Now it is possible to define user individual, if the user should be allowed to export the service note list or not

Service Note creation

We added a new setting “Automatically close order confirmation step for entered service notes ” in the order processing workflow (Tab: “Service Note”). By activating the setting, it is possible for suppliers and customers (if the customer is allowed to enter service notes) to enter the service note without having a sales order confirmation. In case a service note is approved and successfully entered, the order confirmation step will be closed automatically.

This will lead to a log in the history page of the order, stating “the order was confirmed automatically by an entered service note”.

SAP Calculation Scheme

We extended the amount of allowed characters to maximum for using the calculation scheme in the shopping cart and the order, so that it is possible to use the calculation scheme also in different languages.

Sales order approval

We fixed a bug, that the history page of a sales order approval shows a wrong approver.

In case of a sales order change approval, where the orderer user is configured as the approver and this user is blocked, the log of this approval step in the history page wrongly showed that the approval was forwarded to the super admin. However, the approval was actually forwarded to the deputy of the order user.

This bug is now fixed, and the log now shows the correct message, that the approval was forwarded to the deputy.

Costtype for external catalogs.

We have aligned the behavior regarding the assignment of Customer Accounting and Cost Type between OCI, CXML Punchout, Punchin and API. Now all externally transferred items will pull the correct values if an Eclass or UNSPSC is transferred that is maintained in the material group mapping. If a material group is transferred directly, it will override an external classification.

Condition update when transferring to a purchase order

We fixed a bug that caused the conditions of items from a static catalog were not updated before they were transferred to the order.

UNSPSC for the material group mapping via OCI-Punchout

After already supporting UNSPSC for CXML based punchouts we have now added this feature for OCI as well. Now it is possible to find the Material group via UNSPSC during the shopping cart transfer. If both an UNSPSC and an Eclass are passed, the Eclass wins.

Delivery date for external catalogs = 0 or NULL

We implemented logics to address previously unaccounted edge cases in the transfer of articles from external shops.

• In case external shops sent delivery time = 0 to the shopping cart, the delivery date default settings will be considered. If no delivery date default settings are configured, the delivery date will be set to the current date.
• In case the delivery time is transferred empty, the delivery date default settings are considered aswell, but if no delivery dates defaults are configured, the delivery date is set to today.

Extension of the UNSPSC transfer in the OCI inbound scenario

We have extended the possibilities of the UNSPSC transfer for the OCI inbound (Onventis is called via OCI) by the field EXT_Category_ID. Here, either the UNSPSC stored on the article is transferred or, if none is stored there, the fallback from the catalog cover.