Description When sending this date in comparison to an existing ocr for that order: equal -> caught by constraint older -> caught by trigger younger -> should return no error The messages for 1 and 2 are different because handled differently. Imo the constraints (in the specification) of this date should

Description current behavior The order-level promotion prices are not distributed on the orderPosDOs, but directly on the OrderPosItemDO as item price and with a rounding on cent values (no handling of possible rest amount). e.g 2.747 /2 -> 1.37 as item amount, and 1.37*2 = 2.74 although 2.747 should

Description Current Behaviour: When creating an order negative position numbers are not allowed, the creation fails with 400. But this constraint is not specified in the order-YAML. Expected Behaviour: Whether order creation with negative position numbers is allowed or the constraint is documented officially

Description Description: In the pipeline ViewCart-HandleAddProducts (app_sf_responsive) the error handling is missing. For example, if something goes wrong in ProcessBasket-AddProducts, the error is not handled correctly. Steps to repeat: see pipeline ViewCart-HandleAddProducts Node GetProductsToAdd

Description It returns the shop's name of the EXPRESS method as type of the date. Additionally the shop's name is returned as null, but should be STANDARD see test IOM-11140-202, position 2 Steps to Repeat It returns the shop's name of the EXPRESS method as type of the date. Additionally the shop's name

Table of Contents Introduction References Glossary Deployments Access Permissions Access to Operations Backoffice (PRD) Access to SMC (PRD) During the Setup Phase Restrictions Introduction This document describes permissions and responsibilities for accessing and deploying Intershop Commerce Platform

Description PUBLIC, as decided, the sorting should be equal (the same) in all presentations Domain Order Management Bug Order Management Verified Closed Major JiraWorkItem 63574 OMT IOM Intershop Order Management 0 Pull Request 63267 Related iom/3.6.0.0

Description Actual behavior: REST API returns StatusCode 400 (Bad Request). An exception can be found in the log file as shown below. Expected behavior: Order is created in IOM. Steps to repeat: Setup IOM environment with version 3.4.3.0 Try to import order that has two or more different taxes on any

Description Description: ProcessBasket-MergeBasket throws NPE when using pipelet CreateAdHocLineItem Steps to repeat: 0. Migration from ICM 7.7.x to 7.10.30.2 1. Use pipelet'CreateAdHocLineItem (bc_requisition)' to create an AdHoc ProductLineItem for a Voucher in the basket. 2. There exists no product

Table of Contents Introduction Option 1: ICM Update and SolrCloud Migration Tasks for the Implementation Partner Advantages Disadvantages Option 2: ICM 7.10.26-LTS and Solr 4 Tasks for the Implementation Partner Advantages Disadvantages Introduction The Intershop Commerce Management (ICM) 7.10.31.0