TechTalk Newsletter
Download - TechTalk 4 2022 Stay informed by signing up for TechTalk here. ENFDEVDOC doc_access_contract doc_status_final doc_type_techtalk dev_doc 10 29933bbf284ff71419a1081216dd82ac ConfluenceCloud 48287845088 /spaces/ENFDEVDOC/pages/48287845088 1844226834
Support Articles
Table of Contents Introduction Disable Customer Creation Notification E-mails E-Mail Notification to New SMB Business Customers E-Mail Notification to New Private Customers Disabling Requisition Notification E-mails Introduction This article shows the configurations required to disable various e-mail
Guidelines
Table of Contents Introduction References Process Log in to the Docker Registry via an OIDC Provider Docker CLI Login Docker Pull Introduction Intershop provides the base images of all current products as Docker images. These Docker images can be downloaded by authorized users and used for development
Guidelines
Table of Contents 1 Introduction 1.1 References 2 The IOM Return Process 2.1 Configure Return Management 2.2 Create a Return 2.3 Validate a Return 2.4 Create a Credit Note 2.5 Send a Customer Email 2.6 Submit a Return << previous page Guide - IOM RMA Business Process This guideline is part of the Intershop
References
Table of Contents 1 Introduction 1.1 References 2 The Return and Cancelation Business Process 2.1 Return Capture, Validation, and Approval Process 2.2 Return Notification Process 2.3 Finalize Return Process 2.4 Order Cancelation Process Introduction This document is part of the IOM Business Processes
References
This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-requisition-approval-1x2x1.yaml References The following page lists available REST APIs for ICM 7.10 and their version dependencies: Reference - Intershop Commerce Management 7.10 REST API API Specification openapi:
References
This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-cost-center-1x1x0.yaml References The following page lists available REST APIs for ICM 7.10 and their version dependencies: Reference - Intershop Commerce Management 7.10 REST API API Specification openapi: 3.0.1
References
This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-shop-1x3x1.yaml References The following page lists available REST APIs for ICM 7.10 and their version dependencies: Reference - Intershop Commerce Management 7.10 REST API API Specification openapi: 3.0.1 info: title:
References
This API specification is available for download as an Open API 3.0 YAML file: icm-cc-1x2x0.yaml References The following page lists available REST APIs for ICM 7.10 and their version dependencies: Reference - Intershop Commerce Management 7.10 REST API API Specification openapi: 3.0.1 info: title:
Support Articles
Table of Contents Introduction How to Change a Replication Processor Introduction Sometimes it might be necessary to change a replication processor within an existing customer replication environment / project. For example, staging information must be transferred via FullDomainSpecificStagingProcessor
Guidelines
Table of Contents 1 Introduction 2 Debtor Management: Split SalesOrders / PurchaseOrders Export Configuration 3 Require IOM Helm Charts 2.3.0 4 Removals Introduction This guide lists all migrations required from Intershop Order Management 4.2 to 4.3. The document is aimed at project developers. Debtor
References
Description Statuses of a process control object. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all
References
Description Statuses of an approval response. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all states
References
Description Statuses of a payment notification. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all states
References
Description Statuses of a cancelation. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all states of
References
Description Statuses of an invoicing. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all states of Invoicing
References
Description Statuses of a document. Note For services, that are using this model the statuses must be used prefixed with STATE_. I.e., for the status INITIAL it will be returned STATE_INITIAL. Product Version 4.0 Product To Version Status New Labels States The following table lists all states of Document
Concepts
Table of Contents 1 Introduction 1.1 References 2 Single sign-on in the Backoffice 2.1 Prerequisites 2.2 Supported Identity Providers (OIDC) 2.3 Configuration 2.4 Limitations Introduction This concept explains how to enable single sign-on in the Intershop Order Management back office and how it works
References
Description A message to be used for order processing, e.g., to announce an order entry Product Version 4.0 Product To Version Status New Labels States The following table lists all states of Order Transmission Status Model with IDs and short descriptions. State ID Description INITIAL 0 Transmission
Overviews
Table of Contents 1 Introduction 1.1 References Introduction This page lists all status models of the IOM and is aimed at project developers. In IOM business objects are tied to an own status model, which represents the current status of the business object. Status models are used to define status change