From ecec196553a99153f67d95cf6af631e89ea9abaa Mon Sep 17 00:00:00 2001 From: epmkras <115655086+epmkras@users.noreply.github.com> Date: Wed, 14 Aug 2024 11:13:38 -0400 Subject: [PATCH] Update store-configuration.md - add composer instance import/export Enriching file with information about composer instance import/export. --- .../integration-hub/store-management/store-configuration.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/composer/integration-hub/store-management/store-configuration.md b/docs/composer/integration-hub/store-management/store-configuration.md index cbf79597..e5bde743 100644 --- a/docs/composer/integration-hub/store-management/store-configuration.md +++ b/docs/composer/integration-hub/store-management/store-configuration.md @@ -26,7 +26,9 @@ The following Commerce objects are included when importing/exporting store confi - [Catalogs](/docs/api/pxm/catalog/create-catalog) - [Catalog Rules](/docs/api/pxm/catalog/rules) - [Payment Gateway](/docs/api/payments/gateways). The following fields are masked when exporting payment gateways: **password**, **username**, **login**, **merchant_account**, **signature**, **stripe_account**, **merchant_id**, **private_key**, **public_key**, **payer_id**. These fields must be replaced by real values before importing the configuration. +- [Composer Integration Instances](https://elasticpath.dev/docs/composer/). During export, both enabled and disabled instegration instances are retrieved and marked with the flag `enabled` equals to true or false. During import `enabled` flag is ignored and all integration instances are imported. If the configuration includes an integration that has not been published in the Integrations Hub, the process of importing the integration instance will fail. Ensure that all integrations are published in the Integrations Hub before importing the configuration. All the fields containing "key" or "secret" in the name are masked during exporting integration instances. Before importing configuration those fields need to be replaced with real values. During export, both enabled and disabled instegration instances are retrieved and marked with the flag `enabled` equals to true or false. During import `enabled` flag is ignored and all integration instances are imported. + A Store Configuration Orchestrator Delete Action deletes [products](/docs/api/pxm/products/products) from a store. For more information, watch a video. @@ -70,7 +72,8 @@ Once you have [installed Store Configuration Orchestrator](#installing-store-con - **Token URL** - Your Commerce API Token URL. For example, `https://euwest.cm.elasticpath.com/oauth/` (EU) or `https://useast.api.elasticpath.com/oauth/` (US). 1. Click **Connect** to make sure that the authentication is completed successfully. -1. Click **Next**. The **Store Orchestrator Configuration** page is displayed. The table below describes the options you can configure, depending on the Store Configuration Orchestrator action you are performing. +1. Enter **Integrations Hub API Domain** (us-east-2.elasticpathintegrations.com or eu-west-1.elasticpathintegrations.com) +2. Click **Next**. The **Store Orchestrator Configuration** page is displayed. The table below describes the options you can configure, depending on the Store Configuration Orchestrator action you are performing. | Option | Action | Description | |:--- |:--- | :--- |