Introduction

Welcome to Intershop Commerce Management 12.

This Public Release Note contains information about the latest features of Intershop Commerce Management. In addition, it serves as a quick reference for the latest documentation.

References

For further documents related to ICM 12, refer to Overview - Intershop Commerce Management 11+.

New & Noteworthy

This release contains the support of JDK 21 which replaces replaces JDK 17, and goes forward with the javax - jakarta replacement.

To support the K8s job server, replication tasks will be “scheduled” as jobs and no longer directly executed by the target (mostly live) application server. In case there is no job server configured, the jobs will be executed in the target server.

The following REST APIs have been updated with the initial ICM 12.0 release:

• Batch Processes REST API

• Product and Catalog Management REST API (Beta)

• Punchout REST API
  For all REST API changes, see Reference - Intershop Commerce Management 12 REST API.

Release Documents

Feature List

Please see our feature list for more details about the new release:

• Feature List - Intershop Commerce Management 12.0

Guides, Concepts & Cookbooks

For a list of all available ICM 12 documents, use the ICM 12 filter in our Knowledge Base.

Migration Guides

For migrations to ICM 12 version, refer to:

• Overview - ICM 12 Migration

Changelog

Hotfix Release 12.2.1

• Added replacement for the OPTIONS method in the OCI Punchout Resource, see Reference - Punchout REST API 2.5.0 (OCI).

Minor Update Release 12.2.0

• The calculation result view Java API has been extended with service taxes per bucket per tax class.
  Therefore, a new value in the basket calculation has been introduced that allows to get the taxes on shipping costs grouped by their tax rates per bucket. It can be accessed via LineItemCtnrCalculationResultView.getShippingBucketCostItemTaxesGroupedByTaxRate(ComputedShippingBucketItem) or *ShippingBucketBO.getShippingCostTaxesGroupedByTaxRate().

• The Transport Framework now supports Azure Blob Storage in addition to the previously supported Azure File Storage. This allows for greater flexibility when transferring data between ICM and other connected systems in cloud environments. This feature will be used by default for the data transfer from ICM to Sparque, see Guide - Transport Framework.

• Payment service handling changes:

  • icm-as-libraries-api_service: A new accountIdentifier field has been added to the AuthorisationResult.
    (The api_service serves as an interface and central location where, among other things, the common objects for the payment service implementations are stored.)

  • A new PaymentServiceInformation event type in the transaction history has been added to provide an easy way to transfer additional information from Payment Service Providers to user interfaces such as the PWA Storefront and the ICM back office.

• cXML-related functionality provided by Punchout REST API 2.3.0 has been moved to a dedicated API specification, see Reference - Punchout cXML REST API 3.0.0. As a result, all cXML endpoints in the Punchout REST API 2.4.0 have been deprecated. Note that OCI functionality described in the Punchout REST API 2.3.0 and 2.4.0 remains fully operational.

Minor Update Release 12.1.0

• Process chains of the jobs ProcessChain.InitIndexesProductAssignments and ProcessChain.RebuildIndexesProductAssignments were moved to SLDSystem site. This was necessary because the framework expects it to be in a site folder. See Job - ProcessChain.InitIndexesProductAssignments and Job - ProcessChain.RebuildIndexesProductAssignments.

• With the new Order REST API 1.6.0, users with the account_admin role can view all orders of a customer and use a filter to restrict views to a specific user now, similar to the Responsive Starter Store functionality. For further compatible REST API updates, see Reference - Intershop Commerce Management 12 REST API.

• A new Java API has been introduced, which allows for a registration of objects to be cleaned up to avoid usage of deprecated Object.finalize().