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.
For release notes for LTS (long term support) releases, refer to Public Release Note - Intershop Commerce Management B2C/B2X 7.10.26 LTS Releases.
Assembly Name | Description |
---|---|
com.intershop.assembly:commerce_management_b2c | Base assembly for Intershop Commerce Management B2C (this is the base of all B2C projects). |
com.intershop.responsive:inspired-b2c | Demo store "Inspired" B2C (source of this assembly is the starting point for B2C projects). |
Assembly Name | Description |
---|---|
com.intershop.assembly:commerce_management_b2x | Base assembly for Intershop Commerce Management B2X (this is the base of all B2B projects). |
com.intershop.responsive:inspired-b2x | Demo store "Inspired" B2X (source of this assembly is the starting point for B2B projects). |
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.
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.
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.
ICM 7.10.2 does support Microsoft SQL Server, however Azure SQL Database support will be delivered with the next update.
To read about the newest system requirement, please refer to:
The Reference - CI Dependencies of Intershop Commerce Management provides a mapping of all:
Please see our feature lists for more details about the new release:
The following documents are updated or entirely new for ICM 7.10:
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:
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.
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.products
endpoint was fixed: The inStock attribute now (correctly) returns data from the inventory service, see Guide - 7.10 REST API Changes for details.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:
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.
returnSortKeys=true
now returns additionally the localized names of the available sorting options. (IS-29415)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.
Stronger signature for ICM-specific JWT tokens
New REST API operations for handling order approval in buying organizations based on personal budgets or order size limits. This includes:
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.
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).
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.
supplierSKU
was added to the response of /products/<productID>.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.sp_deleteUserDataByDomain
to run forever if there is data that needs to be deleted in the tables BASICPROFILE/BASICADDRESS related to the deleted DOMAINIDs.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.
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
.CategoryRO
as categoryRef
.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.
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:
effectiveUrl
has been added to attachments under the products resource.For the latest REST API documentation refer to:
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.numberOfRatings
has been added to /products and /categories/<catID>/products that allows to render this information on product lists without calling /products/<productID> first.
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.Note
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).
sp_compile_invalid_objects
A DBMigrate for MSSQL is needed to fix the following issues:
packingUnit
was added.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 unitpackingUnit
to the REST response for all /product calls. It contains the packing unit information for the respective product.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.
minOrderQuantity
and
inStock
were added.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 quotesinStock
- can be used to effectively render the family page in the list viewavailable 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.
Master UUID
and Is Variation
, GroupMasterUUID
should be indexed. The change is not mandatory - the previous configuration will still work. Also seeThe 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.