@salesforce/b2c-tooling-sdk 1.15.1 → 1.17.0

package/data/job-steps/ExportFacebookFeed.md

@@ -0,0 +1,26 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportFacebookFeed
+
+**Type ID:** `ExportFacebookFeed`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports Catalog Feed for Facebook.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+This step takes no configuration parameters.
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportGiftCertificates.md

@@ -0,0 +1,30 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportGiftCertificates
+
+**Type ID:** `ExportGiftCertificates`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports Gift Certificates.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportInventoryLists.md

@@ -0,0 +1,31 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportInventoryLists
+
+**Type ID:** `ExportInventoryLists`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports inventory lists.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `InventoryListIDs` | No | — | — | Optional comma separated list of inventory list ids to be exported. If not specified, the inventory list assigned to the Site is exported. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportMetaData.md

@@ -0,0 +1,32 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportMetaData
+
+**Type ID:** `ExportMetaData`  
+**Scope:** Organization (add to an organization-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Export System Object Type extensions and Custom Object Type definitions.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportCustomTypes` | Yes | `true` | — | Export Custom Object Type definitions. |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `ExportSystemTypes` | Yes | `true` | — | Export System Object Type extensions. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportOrders.md

@@ -0,0 +1,42 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportOrders
+
+**Type ID:** `ExportOrders`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports all orders matching the selected criteria using Search Service, with a maximum of 1000 orders per run. After an order has been exported successfully, its export status is EXPORTED. If an order did not export successfully, its order export status is FAILED. It is important to note that an asynchronous write action performed on an order by another process can result in an optimistic locking exception during order export.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `Canceled` | No | `true` | — | Include orders in order status CANCELED. |
+| `Completed` | No | `true` | — | Include orders in order status COMPLETED. |
+| `Confirmation Status` | Yes | `All` | `All`, `Not Confirmed`, `Confirmed` | The confirmation status. |
+| `Created` | No | `true` | — | Deprecated. Created orders cannot be exported. |
+| `Export Status` | Yes | `Ready for Export` | `All`, `Not Exported`, `Exported`, `Ready for Export`, `Export Failed` | The export status. Recommendation is to use READY FOR EXPORT to signal the export is needed. |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `Failed` | No | `true` | — | Deprecated. Failed orders cannot be exported. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `New` | No | `true` | — | Include orders in order status NEW. |
+| `Open` | No | `true` | — | Include orders in order status OPEN. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+| `Payment Status` | Yes | `All` | `All`, `Not Paid`, `Partially Paid`, `Paid` | The payment status. |
+| `Replaced` | No | `true` | — | Include orders in order status REPLACED. |
+| `Shipment Status` | Yes | `All` | `All`, `Not Shipped`, `Partially Shipped`, `Shipped` | The shipment status. |
+| `Use Order Export Delay` | No | `false` | — | See 'Order Export Delay' at 'Site Preferences' -> 'Order Preferences' -> 'Order Export Settings' |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportPageLocalization.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportPageLocalization
+
+**Type ID:** `ExportPageLocalization`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Export page content for localization purposes
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileFormat` | Yes | — | `JSON`, `RESOURCE` | The format in which the data will be exported. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `Locale` | Yes | — | — | The locale for which the Page data will be exported. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+| `PageIDs` | No | — | — | A JSON object containing the single property 'page_ids', which is an array of Page IDs. When not specified, 'PageIDsFile' must be used. |
+| `PageIDsFile` | No | — | — | When no 'PageIDs parameter is supplied, this is the name of a file containing one Page ID per line. Its is referenced relative to the 'Impex/src' folder.' |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportPriceBook.md

@@ -0,0 +1,31 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportPriceBook
+
+**Type ID:** `ExportPriceBook`  
+**Scope:** Organization (add to an organization-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports price data.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+| `PriceBookID` | Yes | — | — | The ID of the Pricebook which will be exported. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportProductLists.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportProductLists
+
+**Type ID:** `ExportProductLists`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports product lists of a site. If all the options are selected, all product lists that were created by anonymous or registered customers, either empty or non-empty, that are either new (has never been exported) or modified (changed since the last time it was exported) will be exported. If none of the options are selected, all non-empty product lists that are owned by a registered customer will be exported.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `IncludeAnonymousLists` | No | `true` | — | Includes anonymous product lists in the export. An anonymous product list is a product list that does not belong to a registered user. |
+| `IncludeEmptyLists` | No | `true` | — | Includes empty product lists. Empty product lists do not have any items added to them. When disabled, these lists are excluded from the export. |
+| `ModifedListsOnly` | No | `false` | — | Limits the export to modified lists only. A modified product list is a list that has changed in some way since it was last exported. If the NewListsOnly option is also set, the export will contain new or modified product lists only. |
+| `NewListsOnly` | No | `false` | — | Limits the export to new lists only. A new product list is a list that has never been exported previously. If the ModifedListsOnly option is also set, the export will contain new or modified product lists only. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportPromotions.md

@@ -0,0 +1,30 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportPromotions
+
+**Type ID:** `ExportPromotions`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports promotions.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportShippingMethods.md

@@ -0,0 +1,30 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportShippingMethods
+
+**Type ID:** `ExportShippingMethods`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports shipping methods.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportSourceCodeGroups.md

@@ -0,0 +1,30 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportSourceCodeGroups
+
+**Type ID:** `ExportSourceCodeGroups`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports source code groups.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportStores.md

@@ -0,0 +1,31 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportStores
+
+**Type ID:** `ExportStores`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports stores.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+| `StoreID` | Yes | — | — | Define the ID of the store to be exported or '*' to export all stores. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ExportTaxTable.md

@@ -0,0 +1,30 @@
+<!-- prettier-ignore-start -->
+# Job Step: ExportTaxTable
+
+**Type ID:** `ExportTaxTable`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Export)
+
+Exports tax data.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `ExportFile` | No | — | — | Export file name and path relative to 'IMPEX/src'. Required if not using FileNamePrefix. |
+| `FileNamePrefix` | No | — | — | Prefix for the export file. A timestamp is appended and site information as applicable. To order the files chronologically, sort alphanumerically. Path is relative to 'IMPEX/src' and can include a subdirectory. Required if not using ExportFile. |
+| `OverwriteExportFile` | No | `true` | — | If selected, the option overwrites an existing file. If not selected and a file exists, the job step exits and reports an error. |
+
+## Working With IMPEX Files
+
+This step writes a file into the instance IMPEX area (typically under `IMPEX/src/...`). The produced file can be consumed by a later step in the same flow (for example a replication or a custom processing step) or downloaded via WebDAV. See the `b2c:b2c-custom-job-steps` skill for IMPEX hand-off patterns.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ImportABTests.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ImportABTests
+
+**Type ID:** `ImportABTests`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Import)
+
+Imports A/B tests.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `AfterImportFileHandling` | Yes | `Archive` | `Keep`, `Delete`, `Archive`, `Archive Zipped`, `Archive In Subfolders`, `Archive Overwrite Existing` | What to do with the import file after successful or failed import. The handling is not performed if there was a locking problem, or if ImportFailedHandling is ERROR and the file failed to validate. |
+| `ArchiveFolder` | No | `archive` | — | Folder to store archived import files. Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'. Folder location relative to 'IMPEX/' folder. If not defined 'IMPEX/archive/' is used. |
+| `FileNamePattern` | No | — | — | Regular expression pattern to select import files, e.g. 'import_.*\.xml'. Matching files are imported in alphanumerical order. If not defined all files in working folder are imported. |
+| `ImportFailedHandling` | Yes | `WARN` | `ERROR`, `WARN` | The step exit status that will be used when the import process failed. |
+| `ImportMode` | Yes | `Merge` | `Merge`, `Delete`, `Replace`, `Update` | The import mode. |
+| `NoFilesFoundHandling` | Yes | `NO_FILES_FOUND` | `OK`, `ERROR`, `WARN`, `NO_FILES_FOUND` | The step exit status that will be used when no matching files were found. |
+| `WorkingFolder` | No | — | — | The folder that contains the import files, relative to the 'IMPEX/src/' folder. If not defined 'IMPEX/src/' is used as working folder. |
+
+## Working With IMPEX Files
+
+This step reads files from the instance IMPEX area. `WorkingFolder` is resolved relative to `IMPEX/src/` (and defaults to `IMPEX/src/`); use `FileNamePattern` to select which file(s) to import. A prior step — custom or standard — that writes a file under `IMPEX/src/...` can hand off directly to this step. See the chaining example in the `b2c:b2c-custom-job-steps` skill.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ImportActiveData.md

@@ -0,0 +1,33 @@
+<!-- prettier-ignore-start -->
+# Job Step: ImportActiveData
+
+**Type ID:** `ImportActiveData`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Import)
+
+Imports active data from the provided CSV files.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `AfterImportFileHandling` | Yes | `Archive` | `Keep`, `Delete`, `Archive`, `Archive Zipped` | What to do with the import file after successful or failed import. The handling is not performed if there was a locking problem, or if ImportFailedHandling is ERROR and the file failed to validate. |
+| `ArchiveFolder` | No | `archive` | — | Folder to store archived import files. Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'. Folder location relative to 'IMPEX/' folder. If not defined 'IMPEX/archive/' is used. |
+| `FileNamePattern` | No | — | — | Regular expression pattern to select import files, e.g. 'import_.*\.csv'. Matching files are imported in alphanumerical order. If not defined all files in working folder are imported. |
+| `ImportFailedHandling` | Yes | `WARN` | `ERROR`, `WARN` | The step exit status that will be used when the import process failed. |
+| `NoFilesFoundHandling` | Yes | `NO_FILES_FOUND` | `OK`, `ERROR`, `WARN`, `NO_FILES_FOUND` | The step exit status that will be used when no matching files were found. |
+| `WorkingFolder` | No | — | — | The folder that contains the import files, relative to the 'IMPEX/src/' folder. If not defined 'IMPEX/src/' is used as working folder. |
+
+## Working With IMPEX Files
+
+This step reads files from the instance IMPEX area. `WorkingFolder` is resolved relative to `IMPEX/src/` (and defaults to `IMPEX/src/`); use `FileNamePattern` to select which file(s) to import. A prior step — custom or standard — that writes a file under `IMPEX/src/...` can hand off directly to this step. See the chaining example in the `b2c:b2c-custom-job-steps` skill.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ImportAssignments.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ImportAssignments
+
+**Type ID:** `ImportAssignments`  
+**Scope:** Organization (add to an organization-level job flow)  
+**Category:** Standard / system job step (Import)
+
+Imports assignments
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `AfterImportFileHandling` | Yes | `Archive` | `Keep`, `Delete`, `Archive`, `Archive Zipped`, `Archive In Subfolders`, `Archive Overwrite Existing` | What to do with the import file after successful or failed import. |
+| `ArchiveFolder` | No | `archive` | — | Folder to store archived import files. Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'. Folder location relative to 'IMPEX/' folder. If not defined 'IMPEX/archive/' is used. |
+| `FileNamePattern` | No | `.*\.xml` | — | Regular expression pattern to select import files, e.g. 'import_.*\.xml'. Matching files are imported in alphanumerical order. If not defined, all files in the working folder are imported. |
+| `ImportFailedHandling` | Yes | `WARN` | `ERROR`, `WARN` | The step exit status that will be used when the import process failed. |
+| `ImportMode` | Yes | `Merge` | `Merge`, `Delete`, `Replace`, `Update` | The import mode. |
+| `NoFilesFoundHandling` | Yes | `NO_FILES_FOUND` | `OK`, `ERROR`, `WARN`, `NO_FILES_FOUND` | The step exit status that will be used when no matching files were found. |
+| `WorkingFolder` | No | — | — | The folder that contains the import files, relative to the 'IMPEX/src/' folder. If not defined 'IMPEX/src/' is used as working folder. |
+
+## Working With IMPEX Files
+
+This step reads files from the instance IMPEX area. `WorkingFolder` is resolved relative to `IMPEX/src/` (and defaults to `IMPEX/src/`); use `FileNamePattern` to select which file(s) to import. A prior step — custom or standard — that writes a file under `IMPEX/src/...` can hand off directly to this step. See the chaining example in the `b2c:b2c-custom-job-steps` skill.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ImportCatalog.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ImportCatalog
+
+**Type ID:** `ImportCatalog`  
+**Scope:** Organization (add to an organization-level job flow)  
+**Category:** Standard / system job step (Import)
+
+Imports catalog data.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `AfterImportFileHandling` | Yes | `Archive` | `Keep`, `Delete`, `Archive`, `Archive Zipped`, `Archive In Subfolders`, `Archive Overwrite Existing` | What to do with the import file after successful or failed import. The handling is not performed if there was a locking problem, or if ImportFailedHandling is ERROR and the file failed to validate. |
+| `ArchiveFolder` | No | `archive` | — | Folder to store archived import files. Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'. Folder location relative to 'IMPEX/' folder. If not defined 'IMPEX/archive/' is used. |
+| `FileNamePattern` | No | — | — | Regular expression pattern to select import files, e.g. 'import_.*\.xml'. Matching files are imported in alphanumerical order. If not defined all files in working folder are imported. |
+| `ImportFailedHandling` | Yes | `WARN` | `ERROR`, `WARN` | The step exit status that will be used when the import process failed. |
+| `ImportMode` | Yes | `Merge` | `Merge`, `Delete`, `Replace`, `Update` | The import mode. |
+| `NoFilesFoundHandling` | Yes | `NO_FILES_FOUND` | `OK`, `ERROR`, `WARN`, `NO_FILES_FOUND` | The step exit status that will be used when no matching files were found. |
+| `WorkingFolder` | No | — | — | The folder that contains the import files, relative to the 'IMPEX/src/' folder. If not defined 'IMPEX/src/' is used as working folder. |
+
+## Working With IMPEX Files
+
+This step reads files from the instance IMPEX area. `WorkingFolder` is resolved relative to `IMPEX/src/` (and defaults to `IMPEX/src/`); use `FileNamePattern` to select which file(s) to import. A prior step — custom or standard — that writes a file under `IMPEX/src/...` can hand off directly to this step. See the chaining example in the `b2c:b2c-custom-job-steps` skill.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->

package/data/job-steps/ImportContent.md

@@ -0,0 +1,34 @@
+<!-- prettier-ignore-start -->
+# Job Step: ImportContent
+
+**Type ID:** `ImportContent`  
+**Scope:** Site (add to a site-level job flow)  
+**Category:** Standard / system job step (Import)
+
+Imports content. If no library-id is specified in the import file, the data is imported into the private library of the current site. If a library-id is specified in the import file, the data is imported into the specified shared library. There is no way to specify a private library using the "library-id" attribute in the import file.
+
+This is a built-in (standard) job step provided by the B2C Commerce platform. Add it to a job flow in **Business Manager → Administration → Operations → Jobs**, or reference it by its type ID in a `jobs.xml` flow inside a site-import archive.
+
+## Configuration Parameters
+
+| Parameter | Required | Default | Allowed Values | Description |
+| --- | --- | --- | --- | --- |
+| `AfterImportFileHandling` | Yes | `Archive` | `Keep`, `Delete`, `Archive`, `Archive Zipped`, `Archive In Subfolders`, `Archive Overwrite Existing` | What to do with the import file after successful or failed import. The handling is not performed if there was a locking problem, or if ImportFailedHandling is ERROR and the file failed to validate. |
+| `ArchiveFolder` | No | `archive` | — | Folder to store archived import files. Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'. Folder location relative to 'IMPEX/' folder. If not defined 'IMPEX/archive/' is used. |
+| `FileNamePattern` | No | — | — | Regular expression pattern to select import files, e.g. 'import_.*\.xml'. Matching files are imported in alphanumerical order. If not defined all files in working folder are imported. |
+| `ImportFailedHandling` | Yes | `WARN` | `ERROR`, `WARN` | The step exit status that will be used when the import process failed. |
+| `ImportMode` | Yes | `Merge` | `Merge`, `Delete`, `Replace`, `Update` | The import mode. |
+| `NoFilesFoundHandling` | Yes | `NO_FILES_FOUND` | `OK`, `ERROR`, `WARN`, `NO_FILES_FOUND` | The step exit status that will be used when no matching files were found. |
+| `WorkingFolder` | No | — | — | The folder that contains the import files, relative to the 'IMPEX/src/' folder. If not defined 'IMPEX/src/' is used as working folder. |
+
+## Working With IMPEX Files
+
+This step reads files from the instance IMPEX area. `WorkingFolder` is resolved relative to `IMPEX/src/` (and defaults to `IMPEX/src/`); use `FileNamePattern` to select which file(s) to import. A prior step — custom or standard — that writes a file under `IMPEX/src/...` can hand off directly to this step. See the chaining example in the `b2c:b2c-custom-job-steps` skill.
+
+## Related
+
+- Run a job that uses this step: `b2c job run <job-id>` (see the `b2c-cli:b2c-job` skill).
+- Author custom steps to chain with this one: `b2c:b2c-custom-job-steps` skill.
+- Find more docs: `b2c docs search <term>` and `b2c docs read <id>`.
+
+<!-- prettier-ignore-end -->