Welcome to Intershop Order Management 2.11!
Intershop Order Management is an Intershop Commerce Suite orders and payments. Intershop Order Management processes orders from multiple touch points (web shop, mobile shop, call center and more), allocates them to multiple fulfillment solutions (fulfillment centers, drop-ship distributors, physical stores and more), and tracks all order and payment transactions. that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of
Intershop Order Management offers a centralized platform for managing distributed inventory, order, invoice and payment life cycles, and provides call center functionality, enabling real-time visibility into customers' purchasing behavior, stock levels, payments, and more. As part of Intershop Commerce Suite, it utilizes the suite's transaction, PIM and merchandising features.
Intershop Order Management (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.
|Intershop Order Management||Intershop Commerce Management B2X||IOM Connector|
|API||Application Programming Interface|
|FTP||File Transfer Protocol|
|GDPR||General Data Protection Regulation|
|ICM||Abbreviation for Intershop Commerce Management|
|IOM||Abbreviation for Intershop Order Management|
|OMS||Abbreviation for Order Management System, the technical name of the IOM|
|OMT||Abbreviation for Order Management Tool , the graphical management tool of the IOM|
|REST||Representational State Transfer|
|SOAP||Simple Object Access Protocol|
Additional entries can now be configured and will be displayed at main menu. Also see Cookbook - IOM Custom Menu Entries in OMT.
The following image shows the custom menu item Statistics that includes an exemplary order overview from another application.
It's now possible to configure the duration of user sessions in OMT by providing an according configuration entry in PlatformConfigDO.
Added a new (migrated) configuration setting at PlatformConfigDO to control the default value used in OMT for return creation.
Also see Guide - IOM 2.11 Migration of Setup.
If deployment of IOM and project artifacts exceeds the preconfigured timeout of 300s, the Wildfly application-server will end the deployment process with an error. The according configuration setting was added to $OMS_ETC/system.std.*.properties and can easily adapted:
As of IOM 22.214.171.124 the Wildfly application-server has a well defined behavior in case of
The restart will only work if the Wildfly application-server is under control of IOM-watchdog. This is the case when running IOM-HA-nodes, but not when running a single-node only (standalone installation).
A new boolean column
reactivateOnStart was added to
oms."ScheduleDO", with false as default value. When set to true, jobs that had previously reached their max. retry count will get reactivated at server start up.
More information on jobs can be found in Cookbook - IOM Job Framework.
The following changes have been made. Also see Reference - IOM REST API.
Previously the hard-coded character U+0015(<Negative Acknowledge, or NAK) was used in most places, but not consistently and the import of data containing the separator character was not possible for all CSV types.
Also see Guide - IOM Product Import section Description ImportConfigurationDO, attribute csvQuote.
A new function was added to the data object
userMailLO that is used in e-mail templates for customers. The function supports the access to a property directly with a known group and key now.
getDispatchPropertyValue('group', 'key')if used in a dispatch mail.
For all functions see section Java Classes of Reference - IOM Customer E-mails.
For installation instructions please see:
Please note that the installation requires installed and preconfigured:
For a complete list of all interfaces please see Overview - IOM Interfaces.
|IOM-9358||Deprecated OMT user property SHOW_INACTIVE_MANDANTS|
|IOM-8711||Deprecated ShopUserMailReturnAnnouncementLO#getProperties, ShopUserMailReturnAnnouncementLO#setProperties|
|IOM-8710||Deprecated ShopUserMailPositionLO#getProperties, ShopUserMailPositionLO#setProperties|
|IOM-8737||Invoice detail page shows mark as paid button despite missing permission|
|IOM-8732||Invoice detail page shows download link despite missing permission|
|IOM-8704||Order address edit form breaks for three level shop hierarchy|
|IOM-8665||User profile page shows admin menu item as active|
|IOM-8643||Reservation workflow for "decrease stock level on order export" supports happy path only|
|IOM-8639||Daterangepicker can only select per 5 minutes, which raises errors in preselection|
|IOM-8611||Wrong or missing permission checks for return request approvals|
|IOM-8610||Wrong success message on rejecting return requests|
|IOM-8595||Can't set OrderPosNo to DispatchPos-mapping to more than one OrderPosition with the same article|
|IOM-8594||Unable to accept order due to concurrency problem at customer creation|
|IOM-8578||Logged-in user is able to deactivate himself|
|IOM-8567||Customer address of type invoice shows packingStation|
|IOM-8564||Violations of unique key UserSessionDO_userRef_key during normal operation|
|IOM-8554||Focus at login page is on the company logo|
|IOM-8533||E-mail preview broken (mail without supplier context)|
|IOM-8527||The customer search ignores possible matches from the addresses|
|IOM-8497||Sort buttons avoid clicks|
|IOM-8466||Returns on positions on the same product are not processed|
|IOM-8462||Return with multiple positions can not be created|
|IOM-8220||reset_iom_jobs causes wrong misfire / retry behavior|
|IOM-7944||Wrong message when trying to create a return for not yet delivered orders by batch action|
|IOM-7663||Selected expanded enumerations do not persist their values into the corresponding database tables|
|IOM-7642||Error, when logged-in user deletes himself|
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.