Description The listed SOAP-services introduced a deprecation on Supplier id as used by the shop. See https://jira.intershop.de/browse/IOM-5488 Tasks: Delete it Update generated html-documentation Update confluence documentation AddressService-v1.0 ApprovalService-v1.0 CustomerService-v1.0 Immateria

Description It was allowed to define different roles with the same name (Entity RoleDO). But roles are defined system wide and have a flat structure (no hierarchy). Duplicate hence does not make sense. Moreover we can't exclude that some bugs could arise with duplicate names. Note: there was already

Description documentation of OrderMapperOut and OrderPosMapperOut v1.1 DocumentNote Domain Order Management Task Order Management Moved out of state Resolved Closed Major JiraWorkItem 38810 Documentation IOM Intershop Order Management 0 Hyperlink 38755 Related 43337 Parent

Description The IOM ShopService v1.0 stores dispatches without a relation to an order object: actual behaviour: No validation check against element Dispatch/Shop attribute orderId at DispatchMapperInBean No feedback at the SOAP response The client (supplier) thinks everything is okay but at the database

Description The IOM ReturnService v1.0 stores returns without a relation to an order object: actual behaviour: No validation check against element Return/Shop attribute orderId at ReturnMapperInBean No feedback at the SOAP response The client (supplier) thinks everything is okay The validity check takes

Description The IOM ShopService v1.0 stores responses without a relation to an order object: actual behaviour: No validation check against element Response/Shop attribute orderId at ResponseMapperInBean No feedback at the SOAP response The client (supplier) thinks everything is okay but at the database

Description Things to be taken into consideration: Keep It Simple, Stupid! a.k.a KISS principle 1. Object-oriented approach 2. Design patters (SOLID, DRY, etc.) 3. Make the calculations part simple 4. Write appropriate comments in proper English The solution will only be provided in trunk. Domain Order

Description Currently there are two methods for promotion creation: PromotionRepository.createPromotion and RebateMgr.createPromotion. The two methods differ slightly with respect to promotion combinability. However, there should only be one method for promotion creation, preferrably in a PromotionMgr

Skywalker Task SaaS Moved out of state Resolved Closed null Major JiraWorkItem 24432 IS Products a_responsive/7.11.0.0-devrel23 as/11.0.4 as/11.0.5 data/1.0.5 data/1.1.0 data/1.1.1 responsive/33.0.3 responsive/33.0.4 responsive/33.0.5 responsive/33.0.6 responsive/40.0.0 responsive/40.0.1 responsive/40

Description Description: A lot of LOCALIZATIONENTRY entries will lead to multiple AsyncEventDistribution RepositoryLocSheetImpl threads Steps to repeat: An ICM cluster with 8 AS and a huge LOCALIZATIONENTRY table will lead to multiple AS threads. The effect occurs if you click multiple times on the BOs