- Menu
- Sitemap
Public Release Note - Intershop Order Management 4.X
1 Introduction
Welcome to Intershop Order Management 4!
Intershop Order Management (IOM) is an application of the Intershop Commerce Platform that is designed to combine omnichannel commerce processes into one system. It automates and streamlines the life cycle of orders and payments. IOM processes orders from multiple touchpoints (webshop, mobile shop, call center, etc.), allocates them to multiple fulfillment solutions (fulfillment centers, drop-ship distributors, physical stores, etc.), and tracks all orders and payment transactions.
IOM offers a centralized platform for managing distributed inventory, order, invoice, and payment life cycles, and provides call center functionality, enabling real-time visibility for customers' purchasing behavior, stock levels, payments, etc. As part of the Intershop Commerce Platform, it utilizes the platform's transaction, PIM, and merchandising features.
IOM offers the possibility to tailor your business models as flexible and free as you need and depict them in your e-commerce environment. The order management system adjusts the order processing for various sales channels and suppliers and can be seamlessly integrated with existing components of your IT environment.
1.1 Glossary
Term | Description |
|---|---|
REST | Representational State Transfer |
OMT | Abbreviation for Order Management Tool, the graphical management tool of the IOM |
OMS | Abbreviation for Order Management System, the technical name of the IOM |
Kubernetes | An open-source system for automating deployment, scaling, and management of containerized applications. Also see Docker and Helm. |
IOM | Abbreviation for Intershop Order Management |
ICM | Abbreviation for Intershop Commerce Management |
Helm | A package manager for Kubernetes. Also see Docker |
Docker | An operating system-level virtualization software. Also see Kubernetes and Helm |
API | Application Programming Interface |
1.2 General Information
System Requirements - Intershop Order Management 4.2 (latest)
Guide - IOM 4.1 - 4.2 Migration (latest)
andPublic Release Note - IOM Helm Charts 2.1 and https://github.com/intershop/helm-charts/tree/main/charts/iom (latest)
Public Release Note - IOM dbaccount Docker Image 1.5 (latest)
1.3 Additional References
See Overview - IOM Public Release Notes for an appropriate version of the ICM-IOM-Connector
2 Release IOM 4.2
2.1 References
2.2 What’s New
2.2.1 Major Enhancements
2.2.1.1 New Transmission API Version 2.0
A new version of the transmission REST API is available, which introduces improved search and update options. Refer to Reference - IOM REST API - Transmissions 2.0 and Overview - Intershop Order Management REST API.
Based on this new version, the back office has been enhanced and supports the same options in the transmissions section too.
2.2.1.2 Added Order Change Requests to the Order Details Page
To show existing change requests and their status, the list of order change requests of an order is now shown on the order details page. Also refer to Concept - IOM Feature Toggles of OMT.
2.2.1.3 Support of WildFly Metrics in Prometheus Format
In order to better support monitoring of the application, the IOM now supports over 20.000 metrics of the WildFly application server in the Prometheus format. For more detail see iom/helm-charts/Metrics.rst.
2.2.1.4 Update of Infrastructure Components
The following infrastructure components were updated:
WildFly was updated to version 26.1.2.Final
IOM now uses Adoptium OpenJDK 17.0.4.1+1
2.2.2 Miscellaneous
2.2.2.1 OrderMapperOut V1.1 JNDI
OrderMapperOutBean_v1_1.java now offers the static constant OrderMapperOut.LOGIC_ORDERMAPPEROUT_V1_1 to support the JNDI lookup more easily.
2.2.2.2 Change in the Order Approval Process
Due to the fact that approval preconditions (e.g. credit limit) may change over time, this has led to inconsistent behavior in the approval process in some rare cases.
With IOM 4.2 approval rules will not be executed for the second time again. IOM will only consider existing OrderApprovalReasonDOs/ApprovalResponseDOs and respect the selected approval/rejection accordingly.
2.3 Setup & Configuration
For installation instructions see:
Docker images are available at:
Helm Charts are available at:
2.4 Fixed Defects
ID | Title |
|---|---|
Manual credit note requests fail due to too many order positions in the back office | |
Commodity group search is broken in the back office | |
Manual credit note on aggregated invoices: the credit note is mapped to all invoice's orders | |
Warning log full with: bakery.logic.job.file.FTPFileTransferBean finished successfully, but the success was not registered at JobStateDefDO | |
CloseInvoicingPCBean repeatedly failing but unable to analyze because it does not show which row is affected | |
Race conditions + suppressed exceptions in invoice calculation | |
OrderMapperOut's JNDI binding supports only StoreOrder 1.0, but not 1.1 | |
ShopDO.getEventRegistryEntryList() is not thread safe | |
Rejecting an order approval may lead to an order being approved anyway | |
Stock import cannot handle empty files despite ImportConfigurationDO.canDatapackBeEmpty being set to true | |
Missing unique constraint on Supplier2ReturnReasonDefDO | |
Product import refuse article with error "wrong supplier-article-no" |
3 Release IOM 4.1
3.1 References
3.2 What’s New
3.2.1 Major Enhancements
3.2.1.1 Azure PostgreSQL Flexible Server is supported now
IOM 4.1. supports the usage of Azure PostgreSQL Flexible Server. These changes require the usage of:
3.2.1.2 Update of infrastructure components
The following infrastructure components were updated:
Wildfly was updated to version 26.1.0.Final
IOM now uses Adoptium OpenJDK 11.0.15+10
IOM Docker images are now based on Ubuntu 22.04
3.2.2 Miscellaneous
3.2.2.1 Split of accounting-related exports
Exports to accounting/debtor management systems can now be enabled for specific use cases instead of using a “global” switch. See migration notes for details.
3.3 Setup & Configuration
For installation instructions see:
Docker images are available at:
Helm Charts are available at:
3.4 Fixed Defects
ID | Title |
|---|---|
"Returns" tab in OMT might break in case of invalid/unprocessed returns | |
Setting root certificate for db is failing | |
Potential vulnerability in OMT needs to update spring framework to version to 5.3.18 | |
In OMT, sorting orders on customer details page by date does not work | |
Copyright on start page is outdated | |
In OMT it is not possible to edit and save product data within the channel tab | |
In OMT it is not possible to modify the shop or supplier articleNo within the channel tab | |
Empty positions tab after a supplier action | |
Wrong treatment of fields street, streetName, and houseNumber leads to repetition of house number in e-mails | |
Cancelation comment is not visible in OMT anywhere | |
Creation user is not shown for credit note | |
Logic to reduce stock on order export ignores canceled items | |
Manual credit note request fails due to too many order positions |
3.5 Changelog
3.5.1 Release IOM 4.1.5
3.5.1.1 Fixed Defects
ID | Title |
|---|---|
Accepting orders via SOAP API fails with promotion rounding error |
3.5.2 Release IOM 4.1.4
3.5.2.1 Fixed Defects
ID | Title |
|---|---|
Stock import can't handle empty files despite ImportConfigurationDO.canDatapackBeEmpty being set to true |
3.5.3 Release IOM 4.1.3
3.5.3.1 New configuration option
ID | Title |
|---|---|
Support (optional) minimum date to consider when aggregating invoices |
3.5.3.2 Fixed Defects
ID | Title |
|---|---|
Database error during the migration from older versions (commenting on trigger) | |
InvoiceAggregationIntervalDefDO is not prepared with migration scripts | |
The database function process_article_aggregation fails after migrated to iom/4.1.2 | |
Race conditions + suppressed exceptions in invoice calculation |
3.5.4 Release IOM 4.1.2
3.5.4.1 Fixed Defects
ID | Title |
|---|---|
Manual credit note on aggregated invoices: the credit note is mapped to all invoice's orders | |
Warning log full with: bakery.logic.job.file.FTPFileTransferBean finished successfully, but the success asn't registered at JobStateDefDO |
3.5.5 Release IOM 4.1.1
3.5.5.1 Fixed Defects
ID | Title |
|---|---|
java.lang.ArithmeticException: Rounding necessary when trying to view invoice | |
LazyInitializationException when trying to transmit an order | |
REST ReservationService.createReservation raises 500 if configured OrderSupplierEvaluationRuleDefDO #6 (Delivery due date) for a shop |
4 Release IOM 4.0
4.1 References
4.2 What’s New
4.2.1 Major Enhancements
4.2.1.1 IOM application- and config images are merged to a single image
From now on IOM consists of a single Docker image only. The IOM application- and config images were merged into a single image. This change reduces operational efforts in the Intershop Commerce Platform since it becomes possible to trigger deployments by simply pushing an image.
These changes require the usage of:
4.2.1.2 Optimized execution of database initialization steps during the upgrade process
Beginning with IOM version 4, execution of database initialization steps is tracked internally in granularity of:
execution of stored procedures
execution of migration scripts
execution of configuration scripts
If one of these steps has already been executed, it will be automatically skipped unless changed according to the SQL code. This will result in a shorter upgrade time in many cases, especially when rolling out new project versions.
4.2.1.3 Update of infrastructure components
The following infrastructure components were updated:
Wildfly was updated to version 26.0.1.Final
IOM now uses Adoptium OpenJDK 11.0.14+9
4.2.1.4 Base OS of project images is updated on build
Project2docker, the successor of caas2docker (see migration notes), is now upgrading the base OS of project images whenever a new project image is built. This ensures, that project images always include the latest changes on OS level. Especially for security fixes, this is very important.
4.2.1.5 Ubuntu Mirror can now be defined when building project images
Project2docker now provides the configuration variable UBUNTU_MIRROR_X86 to define a mirror server for Ubuntu distribution and ports. Since default Ubuntu servers are sometimes overloaded and slow, the definition of a mirror makes the image-building process faster and more reliable.
4.2.1.6 IOM image now uses JRE instead of JDK
The usage of JRE instead of JDK by IOM Docker images decreases the image size by about 150MB. A decreased image size leads to decreased resource consumption when running IOM in Intershop Commerce Platform or locally in devenv-4-iom.
4.3 Setup & Configuration
For installation instructions see:
Docker images are available at:
Helm Charts are available at:
4.4 Fixed Defects
ID | Title |
|---|---|
Using the custom-block in order position row breaks the left alignment of common-block | |
"<" and "!=" used for object comparison in SalesPriceCalculatorUtilBean | |
RMA uses wrong shop name in OMT #2 | |
HTTP-201 is documented incorrectly at the return code for update transmissions endpoint | |
E-mail functionality broken when using alphanumeric bucket identifiers | |
User management + transmissions API unusable | |
RMA, Dispatch and Response Transmissions broken | |
Product import fails because of ArticleDO with same supplierArticleNo | |
PromotionDO recalculated values are not updated on cancelations | |
It is possible to register the same tax and location with overlapping time limits in TaxDO | |
Dispatch validation with unknown items causes NPE | |
Order REST API deliveryDate mapping mismatch | |
Random shipping address assigned to invoice documents - intermediate fix |
Disclaimer
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.