1 Introduction

Welcome to Intershop Commerce Management 7.10.

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.

1.1 References

For release notes for LTS (long term support) releases, refer to Public Release Note - Intershop Commerce Management B2C/B2X 7.10.26 LTS Releases.

2 Assemblies

2.1 Intershop Commerce Management B2C

2.2 Intershop Commerce Management B2X

3 New & Noteworthy

3.1 Microsoft SQL Server Support

With ICM 7.10.2 Intershop supports Microsoft SQL Server 2017 as alternative to Oracle Database. All features including Replication are supported by SQL Server. We also support Oracle Database 12c Release 2 now.

3.2 Intershop Progressive Web App

The Intershop Progressive Web App is an essential component of Intershop's new cloud strategy and an alternative storefront for Intershop Commerce Management. Through the clear separation of the Intershop Commerce Suite back-end from the visualization layer and the introduction of clearly defined Synaptic Commerce® APIs, partners and customers can design and customize the Intershop Storefront easier than ever before. Web Developers can use the Intershop PWA to implement storefront applications based on the Intershop Commerce Management (ICM) WebShop REST API and/or 3rd party systems. The Intershop PWA has a four-week release cycle, with new features being added on an ongoing basis.

3.3 Microsoft Dynamics 365 Integration

Intershop is developing Microservices to connect the Intershop Commerce Management 7.10 with Microsoft Dynamics 365 for Finance and Operations. The intention is to enhance the performance of the Dynamics 365 ERP-System by using automated Microservices to ensure data consistency, correctness and fast processing. The Microservice architecture allows a flexible adoption to customer-projects and a fast and agile integration in existing software-landscapes. The connectors for Orders and Inventory are part of the ICM 7.10 GA release. On an ongoing basis further standard connectors for Products, Customers and Prices will be made available for the Intershop Commerce Management 7.10 via a four-week release cycle.

4 Limitations

ICM 7.10.2 does support Microsoft SQL Server, however Azure SQL Database support will be delivered with the next update.

5 Release Documents

5.1 System Requirements

To read about the newest system requirement, please refer to:

• System Requirements - Intershop Commerce Management B2C/B2X (valid from 7.10.0.0 - 7.10.5.0)

The Reference - CI Dependencies of Intershop Commerce Management provides a mapping of all:

• CI-versions of the ICM
• Intershop CI Bootstrap version
• Intershop Gradle Tools version
• Intershop Responsive Blueprint Store version

5.2 Feature Lists

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

6 Concepts & Cookbooks

The following documents are updated or entirely new for ICM 7.10:

7 Migration Guides

Intershop provides Migration Guidelines to ease the migration from 7.9 to 7.10:

For migrations within 7.10 versions refer to the following documents:

8 Changelog

8.1 Patch Release 7.10.27.0

• New job and process chains for search index and product assignment maintenance. See Guide - 7.10.27.0 New Job and ProcessChains for Search Index Maintenance. This requires a DBMigrate.

• Open API specifications are now available on production systems, accessible via Intershop System Management, see Cookbook - Developer Tools ac_swagger | Recipe: Show API Documentation for details. 
• Introduction of configurable CORS filters. For each application a list of allowedOrigins can be configured.
• Added Apache HTTPD support for mod_status and HTTP2, see Guide - 7.10 Build and Deployment.
• A new configuration for Single Sign-On (SSO) prevents the automatic registration of users and modification of user data. Project-specific customizations can thus connect external systems and are thus responsible for the stored data.
• REST API Changes:
  • CMS: The CMS REST API that was completed with 7.10.21.0 is no longer BETA. 
  • Punchout API: A new REST operation that allows to transfer the Punchout basket back to the procurement system was added. 
  • Product & Category API:
    • A new REST endpoint attachments was implemented. It allows to download product attachments. Usually this endpoint is not called directly, instead the product API provides links to the documents which can then be downloaded.
    • A bug in the products endpoint was fixed: The inStock attribute now (correctly) returns data from the inventory service, see Guide - 7.10 REST API Changes for details.
  • Promotion: Improved caching for resource /promotions, see Guide - 7.10 REST API Changes. 

8.2 Hotfix Release 7.10.26.4 (LTS Release)

• New pattern for SSO redirect URI, see Guide - 7.10.26.4 New Pattern for SSO Redirect URIs.

8.3 Patch Release 7.10.26.2 (LTS Release)

Based on your feedback and in order to support the planning of updates, upgrades and enhancements, Intershop Commerce Management 7.10 includes long-term support (LTS) releases from ICM Patch Version 7.10.26. For more information, refer to Concept - Continuous Releases.

Further changes:

• Messaging and cache metrics are now available in Prometheus, see Cookbook - Monitoring with Prometheus for details.
• The searchindexes REST API specifications have been separated from the Backoffice API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management.

• REST API: B2B buyers (admin) can now invite other persons to their customer organization, so they are able to make purchases in this context. 

• A new promotion condition at order level allows to compare the total quantity of items in the basket with a specific amount in several ways.

• The Quoting REST API now supports creating a new quote request from an existing quote request.
• Products REST API: Using the parameter returnSortKeys=true now returns additionally the localized names of the available sorting options. (IS-29415)
• XML Sitemap Generation is available for the Progressive Web App (PWA) application type (intershop.REST), see Concept - URL Rewriting (from 7.10.5) | Rewrite Rules for PWA.
• A new promotion condition at order level allows to compare the order total with a specific purchase amount in several ways.
• MSSQL database optimization: Duplicated indexes are removed. A DBMigrate is required on MSSQL to benefit from the change.
• MSSQL database bugfix: If an index was deleted, it was possible that the wrong index was deleted. A DBMigrate is required on MSSQL to fix the problem.
• MSSQL database optimization: Computed FT_INDEX columns are stored as persistence. A DBMigrate is required on MSSQL to benefit from the change.
• Different REST API versions are now documented correctly and consistently with OpenAPI. This is especially relevant for Basket and Order where two REST API versions are available (see IS-30561 and Reference - WebShop REST API 7.10).

8.4 Patch Release 7.10.24.1

• A new promotion condition at line item level allows to create promotions for specific product(s) based on a product attribute, see Discount Rules in the Intershop Commerce Management online help. 
• A new promotion functionality allows to stop all other promotions after a promotion is successfully applied.
• Single Sign-On is now available for inTRONICS (Azure AD B2C)
• The behavior of the page cache invalidation can now be configured, see Cookbook - Page Cache.
• The search index list now shows a warning when rebuilding a search index is a risk, e.g. when product or catalog import is running.
• REST API Changes:

  • In the authentication REST API, the /logout path was changed to token/logout, see Guide - 7.10 REST API Changes for details.

    Note

    This is a REST API break, which will be rolled back with the next release.

8.5 Patch Release 7.10.23.0

• REST API Changes:
  • The Product & Category REST API now allows filtering by variation master SKU.
  • The following REST API specifications have been separated from the Storefront API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management for each site:
    • Basket
    • Customer
    • Order
    • Organization
    • Recommendation
    • Wishlist
• Single Sign-On:
  • Single Sign-On (SSO) now allows using Azure AD B2C, by configuration of Enterprise Organizations, see Cookbook - Single Sign-On (SSO) | Recipe: Configure Azure AD (B2C)
  • It is now possible to configure additional scopes to be requested from SSO provider, see Concept - Single Sign-On (SSO) | Example Configuration and Cookbook - Single Sign-On (SSO).

  • Stronger signature for ICM-specific JWT tokens

8.6 Patch Release 7.10.22.1

• New job to recalculate the sales target actual amount for all contracts, see Job - Recalculate the Sales Target Actual Amount for all Contracts.
  This requires a DBMigrate.
• New role descriptions for B2B roles. For migration information refer to Guide - 7.10 API Changes.
• JDBC Oracle driver update, see Guide - 7.10 API Changes and Support Article - Handling the New Dependency of 3rd_oracle Version 19.3.1.0 for details.
• REST API Changes:

  • New REST API operations for handling order approval in buying organizations based on personal budgets or order size limits. This includes:

    • New REST interfaces to provide lists of approval tasks and their details for specific approvers,
    • New REST interfaces to provide lists of requisitions (one time or subscription) and their details for specific buyers,
    • New REST interfaces to perform approvals (accept or reject)
      Handling cost centers is not yet included.
  • The following REST API specifications have been separated from the Storefront API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management for each site:
    • Authentication
    • Newsletter Subscription (E-Mail Marketing)
    • Promotion
    • Rating & Review
    • Subscription (Recurring Order)
    • Shop
  • Endpoints of the former Localization API are now part of the Shop API
  • Variation products assigned to one variation master can be retrieved via REST API with /products?MasterSKU=<Master SKU>. The corresponding variation attributes (→ /productfilters?MasterSKU=<Master SKU>) can be used to filter the result set. This allows to create variation master pages in PWAs more efficiently than before. In order to do this, MasterSKU must be indexed in the search index, similar to MasterUUID. This is needed so MasterSKU can be used in the REST API. (The REST API only handles skus, not UUIDs.)

  • Variation products on variation master pages, as well as in the REST API (/products?MasterSKU=<sku>) can now be sorted as defined in the backoffice, if no other sorting is specified. This requires configuration of the search index. See Guide - 7.10 REST API Changes.

• Changes in Single Sign-On (SSO):

  • The SSO redirect URIs are simplified, parameters are no longer required, see Concept - Single Sign-On (SSO).

  • The SSO implementations is now independent from Keycloak and supports standard OIDC flows, see Concept - Single Sign-On (SSO).

  • Single Sign-On support for REST:
    • Updated Authentication 1.0.0 REST API
    • REST token handling now supports JSON web token. This requires a DBMigrate. For details see Reference - Usage of JSON Web Token (JWT).

8.7 Patch Release 7.10.21.0

• The CMS REST API is complete with version 7.10.21. The beta flag will remain for another ~ 6 months. This time will be used to get feedback from projects and make adjustments where necessary. The CMS REST API allows to get all relevant information about web content from Intershop Commerce Management in order to render it in a progressive web app or any other client.

• Extended back office contract start date and end date validation:

  • Contract creation: start date and end date must be in the future.

  • Edit contract: contracts in the future are changeable. If a contract is already started, the end date can only be changed for contracts that are still running. Contracts in the past cannot be changed.

• Azure AD B2B can now be configured for Single-Sign-On, see Recipe: Configure Azure AD (B2B) in Cookbook - Single Sign-on (SSO). Also refer to Guide - 7.10 API Changes for API changes.
• Security updates of libraries, see Guide - 7.10.21.0 Security Update of Libraries.
• The attribute supplierSKU was added to the response of /products/<productID>.

8.8 Patch Release 7.10.20.1

• The configuration property intershop.import.bulker.orm.importedToExistingProductsRatio for updating/building the search indexes after a product import allows to switch off the index build by setting the ratio to a negative value. In addition the property can be configured domain-specific.
• The Notifications API specification has been separated from the Storefront API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management for each site.
• Configurations API (Beta): The response data structure was changed from a list to a map representation, see Guide - 7.10 REST API Changes for details. 

8.9 Patch Release 7.10.19.3

• For MSSQL, an error was fixed that caused the stored procedure sp_deleteUserDataByDomain to run forever if there is data that needs to be deleted in the tables BASICPROFILE/BASICADDRESS related to the deleted DOMAINIDs.
  This requires a DBMigrate.

8.10 Patch Release 7.10.19.2

• New Single Sign-on (SSO) feature for the Organization Management (Operations) Backoffice, see Guide - 7.10.19.0 SSO for Enterprise Backoffice with Keycloak.

• Payment instrument account identifiers can be set up with multiple properties and/or complex types, see Cookbook - Payment | Recipe: Define Account Identifiers for Payment Instruments for details.

• The CMS REST API now supports personalized requests.
• A new resource /productfilters was introduced for the filter REST API. This allows to show the necessary information and provide filter functionality in a more efficient way. This replaces the existing resource /filters.
  
• Extensions of the B2B customer storefront REST API for budget and role management: 
  • When creating a user for an organization, it is possible to define roles for this user.
  • When viewing a list of users of an organization, it is now possible to see approval related data.
  • When updating a user, it is now possible to provide approval related budget data.
• The API specification for "CMS", "Search" and "Product & Catalog" have been separated from the Storefront API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management for each site.
• Introduction of a new Cache API, see Guide - 7.10.19.0 New Cache API - Configuration and Metrics

8.11 Patch Release 7.10.18.1

• New Single Sign-on (SSO) feature for SMC. This requires a DBMigrate. For details see:
  • Concept - Single Sign-On (SSO)
  • Cookbook - Single Sign-On (SSO)
• A new optional query parameter extended has been added to the /products/{id} and /products/{id}/variations resources, which will provide more complete information about variation attributes and their values in the new field variationAttributeValuesExtended.
• The category REST resource now supports a category reference as a category id. The category reference is included in CategoryRO as categoryRef.
• The Localization API specification has been separated from the Storefront API specification and can be viewed via a drop down menu within the Swagger UI in Intershop System Management for each site.

• The CMS REST API now allows to retrieve pages in hierarchical structure by calling /cms/pagetree. The depth can be limited for larger trees. Also a node from a lower level can be passed to retrieve only a specific sub-tree.

8.12 Patch Release 7.10.17.0

• A new Configuration REST API for Commerce Management channel, application and service settings has been introduced. Fore more details see
  • Cookbook - Configuration REST API (v1)
• A new REST API (part of the basket REST API) has been introduced to handle limited tender payment methods like gift cards, gift certificate, etc.
• A new REST API to delete all items in basket has been introduced.

• A new optional query parameter omitHasOnlineProducts has been added to the /categories resource. If set to true, the field hasOnlineProducts will not be resolved for:

  • All categories in the category list resource
  • Subcategories in the category item resource
• The new field effectiveUrl has been added to attachments under the products resource.

For the latest REST API documentation refer to: 

• B2B Frontend REST API | Configurations
• B2C Frontend REST API | Configurations

8.13 Patch Release 7.10.16.6

• New Solr version 8.2.0 is used. The ICM assemblies do not contain Solr anymore. The Solr Search Service Adapter 2.0.3 for Solr server 8.2.0 is used by inspired-b2c and inspired-b2x. It is required to adapt your project assembly to choose a desired version. For more details see:
  
  • Cookbook - Deployment of Solr Search Adapters
  • Public Release Note - Solr4 Search Service Adapter
  • Public Release Note - SolrCloud Search Service Adapter 2
• Image management enhancements require a DBMigrate for Oracle and MSSQL. For more details see:
  
  • Concept - Image Framework  | Image Type with Empty Prefix
  • Cookbook - Image Framework  | Recipe: Migrating to Flexible Image-Type Prefix
• Newsletter feature requires a DBMigrate for Oracle and MSSQL.
• ReCaptcha v1 has been removed. A DB migrate is needed to remove obsolete service configurations.
• New feature payment notifications has been introduced. Fore more details see:
  • Concept - Payment Framework | Notifications
  • Cookbook - Payment | Process Notifications Independently
  • Cookbook - Payment | NotificationRouting
  • Internal handling for state transition has been corrected: After a failed REDUCE the payment status is now set to AUTHORIZED instead of AUTHORIZATION_VOIDED.
• New requestable REST attribute    numberOfRatings   has been added to  /products. It shows the total number of ratings for one product. It allows to render this information on product lists without calling /products/<productID> first.
• The new requestable REST attribute numberOfRatings has been added to /products and /categories/<catID>/products that allows to render this information on product lists without calling /products/<productID> first.
• The new API token login feature enables customers to log in to both the Progressive Web App and the inSPIRED storefront, see: 
  • Concept - Integration of Progressive Web App and inSPIRED Storefront

8.14 Patch Release 7.10.15.2

• New URL rewrite rule for search, see Concept - URL Rewriting (from 7.10.5)
• New login type: Login can be done with either username or e-mail address, see Login Types
• New B2C feature Cashback requires a DBMigrate for Oracle and MSSQL. For details see:
  • Concept - Cashback
  • Cookbook - Cashback
• New requestable REST attribute retailSet was added to /products and /categories/<catID>/products. It shows if products from a list are retail sets or not. It allows to handle retail sets differently in lists (e.g. show a price range, instead of a price), without calling /products/<productID> first.
• New REST resource for handling ViewContext objects
• New ReCaptcha v3 has been introduced. For more details see:
  • Concept - ReCaptcha v3
  • Cookbook - ReCaptcha v3

8.15 Patch Release 7.10.14.0

• The existing basket validation is extended and can now also be used via REST API. For more details see
  • Guide - 7.10 API Changes
  • Cookbook - Order Creation: Recipe - List Chains and Handlers
  • Cookbook - Basket Validation

8.16 Patch Release 7.10.13.4

• New REST API for payment redirect (redirect after order creation) and order handling. For more details see REST API documentation.
  • A DBMigrate is needed
  • For details about the procedure of creating a basket, preparing the checkout and creating an order by using the IS7 REST API see Business Guide - WebShop REST API - Basket and Checkout REST API (v1).

  • For details about the order REST API please have a look at Concept - Order REST API (v1).

  • For details about the basket REST API please have a look at Concept - Basket REST API (v1).

• Support for Prometheus Open Metrics added, see Guide - 7.10 API Changes.

8.17 Patch Release 7.10.12.3

• Due to a fix regarding the passphrase of the SSH keys, the old passphrases are no longer valid. The key pair needs to be regenerated and the new public key needs to be sent to the consumer of the effected transfer. For more information see Guide - 7.10 API Changes.

8.18 Patch Release 7.10.12.2

• Due to the introduction of swagger 2.x, the usage of swagger 1.x in custom cartridges will lead to dependency conflicts as they have the same identifier. In this case you have to use Gradle Tools >= 2.11.10. For more information and migration steps see Guide - 7.10.18.0 Security Update of Libraries
• New REST API for payment redirect handling (redirect before order creation). For more details see REST API documentation.
• Added SEO attributes for product and catalog REST-API. For more details see REST API documentation .
  
• A manual migration is required to fix IS-26655, see Guide - 7.10.12.2 Storing of Promotion Information at Orders for details
• API Changes, see Guide - 7.10 API Changes for details: 
  
  • Reworked text index creation for MS SQL
  • DBMigrate on MS SQL to update procedure sp_compile_invalid_objects
  • Option to disable CSS file compression
• With patch release 7.10.5.3 Customer-Specific Assortments were introduced. With the 7.10.12.2 release one existing limitation was removed: The category page of the classic inSPIRED storefront now takes the assortments into account. If sub-categories are empty due to assortments, they are not listed on the category page.

8.19 Patch Release 7.10.10.1

• Added IPv6 support, see Guide - IPv6 Support for Public Client Requests

• A DBMigrate for MSSQL is needed to fix the following issues:

  • IS-26184 - The staging definition for 'ImageReferences' and 'ImageDefinitions' is moved from platform to business

  • IS-27017 - STAGING_DDL$copy_indexes also handles XML Indexes

8.20 Patch Release 7.10.10.0

• New extension of product REST API to show the default category
  • IS-25665 - Adapt REST API for products to return default category

8.21 Patch Release 7.10.9

• A DBMigrate is needed to fix the following issues:
  • IS-26686 - Staging environment removal error
  • IS-26650 - DDL$drop_table and DDL$drop_view does not check for the database type
• With patch release 7.10.5.3 Customer Specific Assortments were introduced. With the 7.10.8.2 release one existing limitation is removed: The main menu of the classic inSPIRED storefront now takes the assortments into account. If categories are empty due to assortments, they are also removed from the main menu. 
• A new preference in the image management was added. It is now possible to select an image type for category images, instead of using the pre-defined type "M". 
• New requestable REST attribute packingUnit was added.
  By using the /products and /categories/<catID>/products REST endpoints, product stubs for display on family pages and search result pages can be retrieved. The optional attrs parameter allows to receive certain product attributes in that call to construct product tiles on said pages.
  
  • packingUnit - can be used to display the packiging unit
• Upgrade from JGroups 3.4.1 to 4.0.19

8.22 Patch Release 7.10.7.3

• New naming schema for (JSON) attributes representing discounted and undiscounted total amounts - see Guide - 7.10 REST API Changes.
• With this release we added an additional attribute packingUnit to the REST response for all /product calls. It contains the packing unit information for the respective product.
• A DBMigrate is needed to fix the following issues:
  • IS-26284 - 'sp_genericPoAvDeleteByDomain' it not correct for MSSQL

8.23 Patch Release 7.10.6.0

• A DBMigrate is needed to fix the following issues:

  • IS-26004 - Remove obsolete and duplicate indexes (MSSQL)

  • IS-26089 - UUID generation in database was not unique (MSSQL)
  • IS-26066 - Function does not handle constraint duplicates (MSSQL)
  • IS-26076 - Alternate keys was not unqiue

8.24 Hotfix Release 7.10.5.4

• With this release we added an additional attribute availableStock to the REST response for all /products and /product calls. It contains the quantity which is available for sale. The data comes from the Inventory Service.
• New REST API for basket handling including payment. For more details see REST API documentation.
• With the newly introduced Promotion Code Search, it is now possible to easily evaluate the validity, assignment and use of promotion codes in the back office. For more details refer the Intershop Commerce Management online help.

8.25 Patch Release 7.10.5.3

• New REST API for basket handling including line Items, addresses and shipping. We are currently working on payment REST API. For more details please have a look at Cookbook - Basket REST API.
• With Customer Specific Assortments it is now possible to create very individual assortments, much more fine-grained than with Catalog Views. They work with the search index and allow a more flexible configuration without performance loss.
  For further details please refer to Concept - Customer-Specific Assortments.
• The Swatch Image source can now be maintained via Image Management or via Product Custom Attributes. For further details please refer to Concept - Product Variations.
• Order Export can now be initialized via DBInit, for further details refer to Cookbook - Order Export.
• New requestable REST attributes minOrderQuantity and inStock were added.
  By using the /products and /categories/<catID>/products REST endpoints, product stubs for display on family pages and search result pages can be retrieved. The optional attrs parameter allows to receive certain product attributes in that call to construct product tiles on said pages.
  
  • minOrderQuantity - can be used to add products to carts and quotes
  • inStock - can be used to effectively render the family page in the list view
• New REST API for searching variation product by attributes. For further details refer to our API documentation (/products/{productsKey}/variations/search).
• It is now possible to return the redirect status code 301 (moved permanently) instead of the default redirect code 302 (moved temporarily). For further details please refer to Cookbook - URL Rewriting.
• It is now possible to exclude special characters for URL rewriting rules, see Cookbook - URL Rewriting.
• Now attribute groups on channel level get an available via REST API flag. A new checkbox and a new custom attribute are added for every attribute group - AvailableViaREST with the values true/false. If an attribute group is available via REST API, then the group and all contained attributes will be included in the regular get product data call. A new parameter attributeGroup is introduced. It returns the requested attribute groups with all their attributes. For the import/export process an additional attribute <available-via-rest> was added to the impex XML file. For attribute groups on organization level the value is always false.

8.25.1 Major Release 7.0.0 of the Responsive Starter Store (a_responsive)

• Starting with version 7.0.0 of the Responsive Starter Store which depends on ICM 7.10.5.0 or later, the current jQuery 3.3.1 is used instead of 1.11.3. All Javascript code of the Responsive Starter Store was migrated to this new jQuery version.
  • For more information see Guide - Responsive Starter Store 7.0.0 - jQuery 3 Migration.
• With this migration all the used third party libraries were updated to their latest versions as well and adapted where necessary.
• We introduced the usage of Captcha for the Contact Us pages. In the channel preferences you are able to configure the Captcha settings by enabling or disabling the feature.

8.26 Patch Release 7.10.3.1

• The Inventory Connector now works with 7.10.3+,  also see the new documents:
  
  • Public Release Note - D365 Finance and Operations Inventory Connector 1
  • Concept - D365 Finance and Operations Inventory Connector
  • Cookbook - D365 Finance and Operations Inventory Connector
• The performance of the variation master page (usually used in B2B scenarios) was improved. This requires a slightly different configuration of the search index. Instead of Master UUID and Is Variation, GroupMasterUUID should be indexed. The change is not mandatory - the previous configuration will still work. Also see
  
  • Concept - Product Variations