Steps to Repeat have a lot of orders create an order that is currently handled by the optimization search for a mask of orders hitting the currently optimized order a technical error is shown Actual Behavior Order wild card search can be jammed by not finally processed orders Expected Behavior The search

Description This database column belongs to the table oms."Shop2PaymentDefDO". The associated public JPA methods in shop2PaymentDefDO have been marked as @Deprecated and there are new methods to reflect the modification: @Deprecated public Integer getAuthizationDurationInDays() @Deprecated public

Description [No Description] Domain Order Management Task Order Management Moved out of state Resolved Closed Major JiraWorkItem 38809 Communication IOM Intershop Order Management 38755 Parent

Description [No Description] Domain Order Management Task Order Management Moved out of state Resolved Closed Major JiraWorkItem 38807 Communication IOM Intershop Order Management 38755 Parent

Description Added test-methods for FileProcessChainStepContainerBOImpl. Skywalker Task SaaS Moved out of state Resolved Closed Major JiraWorkItem 29113 IS Intershop 7 28903 Parent

Description identify all affected docs fix Confluence pages (done) ToDOo: see https://intranet.intershop.com/kb/index.php?c=Search&r=Search&loff=0&qlog=yes&qtxt=%22the+time+that+cached+pages+are+kept%22 for a list of the affected docs in the section System Management | Site Management | Page Cache Preferences

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

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

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

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

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.

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

Description Description: Missing error handling for personal data requests in ViewPersonalDataRequests-CallSendMailPipeline Pipeline. This leads to the following error log message when requesting personal data of a storefront user via back office while the mail server is configured wrong or not available:

Description Description: Under special circumstances the UserGroupPromotionCacheHelper method getExceededDate may generate NullPointerException Steps to repeat: An AS live system did throw the periodic exception: ERROR xxxxxxxxx.aaaaa.local ES1 appserver0 6661001656-6661001656WS-Site - ish.cartridges

Description Current Behavior When searching for many SKUs in the backoffice a technical error occurs. "com.intershop.beehive.core.capi.pipeline.PipelineExecutionException: Exception occurred while executing pipelet 'ExecutePageableQuery'. " Expected Behavior Result list is shown. Steps to Repeat login

Description Description: ICM use intershop.SMTPServer=defaultMailServer.domain.com as example SMTP server configuration. But domain.com is an existing registered domain in US. We should use .example domain as specified in RFC. Tasks: check for example domain configurations in ICM replace these properties