@viu/emporix-sdk 4.2.0 → 4.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.cts CHANGED
@@ -4220,7 +4220,7 @@ type QParamSearchBody = {
4220
4220
  /**
4221
4221
  * A standard query parameter is used to search for specific values.
4222
4222
  *
4223
- * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-references/standard-practices/q-param)
4223
+ * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param)
4224
4224
  *
4225
4225
  */
4226
4226
  q?: string;
@@ -10226,9 +10226,18 @@ type ImportSchedule = Schedule;
10226
10226
  * `dryRunSample` carries the previewed records on a dry run and is absent on a
10227
10227
  * normal one. `origin` echoes what asked for the run, and is absent on runs
10228
10228
  * recorded before that field existed.
10229
+ *
10230
+ * `mappingVersions` lists the published mapping version each stream runs with,
10231
+ * fixed when the run starts — version `0` means the stream has no published
10232
+ * mappings. It is absent on a dry run of the draft mappings and on runs recorded
10233
+ * before 2026-09-28. `dryRunPublished` says which mappings a dry run used.
10229
10234
  */
10230
10235
  type ImportRun = ImportRun$1;
10231
- /** Per-stream progress within a run. */
10236
+ /**
10237
+ * Per-stream progress within a run. A stream `ABORTED` was not run because of
10238
+ * its configuration — typically mappings that were never published — and its
10239
+ * `message` says why.
10240
+ */
10232
10241
  type ImportRunStream = ImportRunStream$1;
10233
10242
  /** A run together with its per-stream progress — what `getRun` resolves to. */
10234
10243
  type ImportRunDetail = RunDetail;
@@ -10257,7 +10266,7 @@ type ImportDiagnosticKind = TraitDiagnosticsKind;
10257
10266
  /** Filters for `listRunDiagnostics` / `downloadRunDiagnosticsCsv`: `{ streamId?, kind?, limit? }`. */
10258
10267
  type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData["query"]>;
10259
10268
  /**
10260
- * Body for `triggerRun`: `{ mode?, dryRun?, force?, sampleSize?, origin?, streamIds? }`.
10269
+ * Body for `triggerRun`: `{ mode?, dryRun?, force?, sampleSize?, origin?, streamIds?, mappings? }`.
10261
10270
  *
10262
10271
  * - `mode` defaults to `DELTA` server-side.
10263
10272
  * - `streamIds` runs only those streams — **ids, not names** (`getStreamOrder`
@@ -10268,6 +10277,10 @@ type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData
10268
10277
  * idempotency.
10269
10278
  * - `sampleSize` is **dry-run only**: how many mapped records to sample per
10270
10279
  * stream into the run's `dryRunSample`. Clamped to 1–100, defaults to 25.
10280
+ * - `mappings` is **dry-run only** too: `"published"` (the default) checks what
10281
+ * a real run would execute, `"draft"` checks saved mapping changes before they
10282
+ * are published. A real run always uses the published mappings, so the field
10283
+ * has no effect there.
10271
10284
  * - `origin` is free text naming *what* asked for the run (`"Dashboard"`, an
10272
10285
  * integration scenario, your own scheduler), as opposed to `trigger`, which
10273
10286
  * only ever records `MANUAL` or `SCHEDULED`. Omitted or blank, the service
@@ -10276,7 +10289,11 @@ type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData
10276
10289
  * audit trail is worse than a refused request.
10277
10290
  */
10278
10291
  type ImportRunInput = NonNullable<PostImporttoolTriggerRunData["body"]>;
10279
- /** Lifecycle status of an {@link ImportRun}. */
10292
+ /**
10293
+ * Lifecycle status of an {@link ImportRun}. `ABORTED` means the service refused
10294
+ * to start the run because of its configuration — mappings that were never
10295
+ * published, or a changed target schema — and nothing was read or written.
10296
+ */
10280
10297
  type ImportRunStatus = NonNullable<ImportRun["status"]>;
10281
10298
  /** Run mode — `FULL` re-reads everything, `DELTA` only what changed. */
10282
10299
  type ImportRunMode = NonNullable<ImportRunInput["mode"]>;
@@ -10466,6 +10483,19 @@ declare class ImportService {
10466
10483
  * `streamIds` runs a subset — see {@link ImportRunInput} for what is rejected,
10467
10484
  * and note it takes ids where {@link getStreamOrder} reports names.
10468
10485
  *
10486
+ * A run executes each stream's **published** mappings. Publishing needs
10487
+ * `importtool.import_manage` and is not part of the public API, so it happens
10488
+ * in the Management Dashboard's Import Tool rather than through this SDK; a dry
10489
+ * run with `mappings: "draft"` checks unpublished changes first. A stream whose
10490
+ * mappings were never published is `ABORTED` in the run details, and the run
10491
+ * finishes `PARTIAL`.
10492
+ *
10493
+ * **A refused run still resolves.** When `streamIds` names such a stream, or
10494
+ * every enabled stream is in that state, the service answers `200` with the
10495
+ * run anyway, and the run then finishes `ABORTED` with a `message` naming the
10496
+ * streams. Read it back with {@link getRun}, or follow it with
10497
+ * {@link streamRun}, before treating a resolved call as a started import.
10498
+ *
10469
10499
  * Not retried on a 5xx: a POST that timed out may already have queued a run.
10470
10500
  *
10471
10501
  * @example
@@ -10586,7 +10616,8 @@ declare class ImportService {
10586
10616
  *
10587
10617
  * Returns a **new** run — the retry is its own run with `retry: true`, not a
10588
10618
  * mutation of the original. Poll it with {@link getRun} or follow it with
10589
- * {@link streamRun} exactly as you would a triggered run.
10619
+ * {@link streamRun} exactly as you would a triggered run. Like one, it runs the
10620
+ * published mappings and can finish `ABORTED`.
10590
10621
  *
10591
10622
  * Not retried on a 5xx, for the same reason {@link triggerRun} is not: a POST
10592
10623
  * that timed out may already have queued the retry.
@@ -10697,7 +10728,7 @@ type GetChangelogRetrieveTenantChangelogsData = {
10697
10728
  * * `related:elemMatch(...)` — ElemMatch syntax, for example `q=related:elemMatch(entity:group entityId:1gr5e52e-6e27-4ac5-9471-2467d3fb7501)`.
10698
10729
  * * `compoundLogicalQuery` — Nested `OR` / `AND` expressions, for example `q=compoundLogicalQuery:((entity:group type:update) OR (related:elemMatch(entity:group)))`.
10699
10730
  *
10700
- * See also [Query Parameter](https://developer.emporix.io/api-references/standard-practices/q-param).
10731
+ * See also [Query Parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param).
10701
10732
  */
10702
10733
  q?: string;
10703
10734
  /**
@@ -12226,7 +12257,7 @@ type Payment = {
12226
12257
  type PaymentMethod = {
12227
12258
  /**
12228
12259
  * Payment provider, possible values:
12229
- * * `payment-gateway` - When the Emporix Payment-Gateway service should be used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments.
12260
+ * * `payment-gateway` - When the Emporix Payment-Gateway service is used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway.
12230
12261
  * * `custom` - When a custom provider is used. In this case the created order has the `IN_CHECKOUT` status.
12231
12262
  * * `none` - For payment by cash or invoice.
12232
12263
  *
@@ -12237,11 +12268,11 @@ type PaymentMethod = {
12237
12268
  */
12238
12269
  customAttributes?: {
12239
12270
  /**
12240
- * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
12271
+ * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
12241
12272
  */
12242
12273
  token?: string;
12243
12274
  /**
12244
- * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
12275
+ * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
12245
12276
  */
12246
12277
  modeId?: string;
12247
12278
  /**
package/dist/index.d.ts CHANGED
@@ -4220,7 +4220,7 @@ type QParamSearchBody = {
4220
4220
  /**
4221
4221
  * A standard query parameter is used to search for specific values.
4222
4222
  *
4223
- * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-references/standard-practices/q-param)
4223
+ * See: [Standard Practices - Query parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param)
4224
4224
  *
4225
4225
  */
4226
4226
  q?: string;
@@ -10226,9 +10226,18 @@ type ImportSchedule = Schedule;
10226
10226
  * `dryRunSample` carries the previewed records on a dry run and is absent on a
10227
10227
  * normal one. `origin` echoes what asked for the run, and is absent on runs
10228
10228
  * recorded before that field existed.
10229
+ *
10230
+ * `mappingVersions` lists the published mapping version each stream runs with,
10231
+ * fixed when the run starts — version `0` means the stream has no published
10232
+ * mappings. It is absent on a dry run of the draft mappings and on runs recorded
10233
+ * before 2026-09-28. `dryRunPublished` says which mappings a dry run used.
10229
10234
  */
10230
10235
  type ImportRun = ImportRun$1;
10231
- /** Per-stream progress within a run. */
10236
+ /**
10237
+ * Per-stream progress within a run. A stream `ABORTED` was not run because of
10238
+ * its configuration — typically mappings that were never published — and its
10239
+ * `message` says why.
10240
+ */
10232
10241
  type ImportRunStream = ImportRunStream$1;
10233
10242
  /** A run together with its per-stream progress — what `getRun` resolves to. */
10234
10243
  type ImportRunDetail = RunDetail;
@@ -10257,7 +10266,7 @@ type ImportDiagnosticKind = TraitDiagnosticsKind;
10257
10266
  /** Filters for `listRunDiagnostics` / `downloadRunDiagnosticsCsv`: `{ streamId?, kind?, limit? }`. */
10258
10267
  type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData["query"]>;
10259
10268
  /**
10260
- * Body for `triggerRun`: `{ mode?, dryRun?, force?, sampleSize?, origin?, streamIds? }`.
10269
+ * Body for `triggerRun`: `{ mode?, dryRun?, force?, sampleSize?, origin?, streamIds?, mappings? }`.
10261
10270
  *
10262
10271
  * - `mode` defaults to `DELTA` server-side.
10263
10272
  * - `streamIds` runs only those streams — **ids, not names** (`getStreamOrder`
@@ -10268,6 +10277,10 @@ type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData
10268
10277
  * idempotency.
10269
10278
  * - `sampleSize` is **dry-run only**: how many mapped records to sample per
10270
10279
  * stream into the run's `dryRunSample`. Clamped to 1–100, defaults to 25.
10280
+ * - `mappings` is **dry-run only** too: `"published"` (the default) checks what
10281
+ * a real run would execute, `"draft"` checks saved mapping changes before they
10282
+ * are published. A real run always uses the published mappings, so the field
10283
+ * has no effect there.
10271
10284
  * - `origin` is free text naming *what* asked for the run (`"Dashboard"`, an
10272
10285
  * integration scenario, your own scheduler), as opposed to `trigger`, which
10273
10286
  * only ever records `MANUAL` or `SCHEDULED`. Omitted or blank, the service
@@ -10276,7 +10289,11 @@ type ImportRunDiagnosticsQuery = NonNullable<GetImporttoolListRunDiagnosticsData
10276
10289
  * audit trail is worse than a refused request.
10277
10290
  */
10278
10291
  type ImportRunInput = NonNullable<PostImporttoolTriggerRunData["body"]>;
10279
- /** Lifecycle status of an {@link ImportRun}. */
10292
+ /**
10293
+ * Lifecycle status of an {@link ImportRun}. `ABORTED` means the service refused
10294
+ * to start the run because of its configuration — mappings that were never
10295
+ * published, or a changed target schema — and nothing was read or written.
10296
+ */
10280
10297
  type ImportRunStatus = NonNullable<ImportRun["status"]>;
10281
10298
  /** Run mode — `FULL` re-reads everything, `DELTA` only what changed. */
10282
10299
  type ImportRunMode = NonNullable<ImportRunInput["mode"]>;
@@ -10466,6 +10483,19 @@ declare class ImportService {
10466
10483
  * `streamIds` runs a subset — see {@link ImportRunInput} for what is rejected,
10467
10484
  * and note it takes ids where {@link getStreamOrder} reports names.
10468
10485
  *
10486
+ * A run executes each stream's **published** mappings. Publishing needs
10487
+ * `importtool.import_manage` and is not part of the public API, so it happens
10488
+ * in the Management Dashboard's Import Tool rather than through this SDK; a dry
10489
+ * run with `mappings: "draft"` checks unpublished changes first. A stream whose
10490
+ * mappings were never published is `ABORTED` in the run details, and the run
10491
+ * finishes `PARTIAL`.
10492
+ *
10493
+ * **A refused run still resolves.** When `streamIds` names such a stream, or
10494
+ * every enabled stream is in that state, the service answers `200` with the
10495
+ * run anyway, and the run then finishes `ABORTED` with a `message` naming the
10496
+ * streams. Read it back with {@link getRun}, or follow it with
10497
+ * {@link streamRun}, before treating a resolved call as a started import.
10498
+ *
10469
10499
  * Not retried on a 5xx: a POST that timed out may already have queued a run.
10470
10500
  *
10471
10501
  * @example
@@ -10586,7 +10616,8 @@ declare class ImportService {
10586
10616
  *
10587
10617
  * Returns a **new** run — the retry is its own run with `retry: true`, not a
10588
10618
  * mutation of the original. Poll it with {@link getRun} or follow it with
10589
- * {@link streamRun} exactly as you would a triggered run.
10619
+ * {@link streamRun} exactly as you would a triggered run. Like one, it runs the
10620
+ * published mappings and can finish `ABORTED`.
10590
10621
  *
10591
10622
  * Not retried on a 5xx, for the same reason {@link triggerRun} is not: a POST
10592
10623
  * that timed out may already have queued the retry.
@@ -10697,7 +10728,7 @@ type GetChangelogRetrieveTenantChangelogsData = {
10697
10728
  * * `related:elemMatch(...)` — ElemMatch syntax, for example `q=related:elemMatch(entity:group entityId:1gr5e52e-6e27-4ac5-9471-2467d3fb7501)`.
10698
10729
  * * `compoundLogicalQuery` — Nested `OR` / `AND` expressions, for example `q=compoundLogicalQuery:((entity:group type:update) OR (related:elemMatch(entity:group)))`.
10699
10730
  *
10700
- * See also [Query Parameter](https://developer.emporix.io/api-references/standard-practices/q-param).
10731
+ * See also [Query Parameter](https://developer.emporix.io/api-documentation/standard-practices/q-param).
10701
10732
  */
10702
10733
  q?: string;
10703
10734
  /**
@@ -12226,7 +12257,7 @@ type Payment = {
12226
12257
  type PaymentMethod = {
12227
12258
  /**
12228
12259
  * Payment provider, possible values:
12229
- * * `payment-gateway` - When the Emporix Payment-Gateway service should be used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments.
12260
+ * * `payment-gateway` - When the Emporix Payment-Gateway service is used to handle a payment. For details about custom attributes that are required for a particular payment mode, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway.
12230
12261
  * * `custom` - When a custom provider is used. In this case the created order has the `IN_CHECKOUT` status.
12231
12262
  * * `none` - For payment by cash or invoice.
12232
12263
  *
@@ -12237,11 +12268,11 @@ type PaymentMethod = {
12237
12268
  */
12238
12269
  customAttributes?: {
12239
12270
  /**
12240
- * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
12271
+ * Payment token used for the tokenized credit card flows. The field is used when provider type is `payment-gateway`. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
12241
12272
  */
12242
12273
  token?: string;
12243
12274
  /**
12244
- * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/user-guides/system-management/payment-gateway/payments
12275
+ * Identifier of a payment mode. The payment mode has to be configured in the Emporix Payment Gateway service beforehand. For more details, check https://developer.emporix.io/api-documentation/api-guides/checkout/payment-gateway
12245
12276
  */
12246
12277
  modeId?: string;
12247
12278
  /**
package/dist/index.js CHANGED
@@ -946,7 +946,7 @@ var HttpClient = class {
946
946
  };
947
947
 
948
948
  // package.json
949
- var version = "4.2.0";
949
+ var version = "4.2.3";
950
950
 
951
951
  // src/version.ts
952
952
  var SDK_VERSION = version;
@@ -4487,6 +4487,19 @@ var ImportService = class {
4487
4487
  * `streamIds` runs a subset — see {@link ImportRunInput} for what is rejected,
4488
4488
  * and note it takes ids where {@link getStreamOrder} reports names.
4489
4489
  *
4490
+ * A run executes each stream's **published** mappings. Publishing needs
4491
+ * `importtool.import_manage` and is not part of the public API, so it happens
4492
+ * in the Management Dashboard's Import Tool rather than through this SDK; a dry
4493
+ * run with `mappings: "draft"` checks unpublished changes first. A stream whose
4494
+ * mappings were never published is `ABORTED` in the run details, and the run
4495
+ * finishes `PARTIAL`.
4496
+ *
4497
+ * **A refused run still resolves.** When `streamIds` names such a stream, or
4498
+ * every enabled stream is in that state, the service answers `200` with the
4499
+ * run anyway, and the run then finishes `ABORTED` with a `message` naming the
4500
+ * streams. Read it back with {@link getRun}, or follow it with
4501
+ * {@link streamRun}, before treating a resolved call as a started import.
4502
+ *
4490
4503
  * Not retried on a 5xx: a POST that timed out may already have queued a run.
4491
4504
  *
4492
4505
  * @example
@@ -4729,7 +4742,8 @@ var ImportService = class {
4729
4742
  *
4730
4743
  * Returns a **new** run — the retry is its own run with `retry: true`, not a
4731
4744
  * mutation of the original. Poll it with {@link getRun} or follow it with
4732
- * {@link streamRun} exactly as you would a triggered run.
4745
+ * {@link streamRun} exactly as you would a triggered run. Like one, it runs the
4746
+ * published mappings and can finish `ABORTED`.
4733
4747
  *
4734
4748
  * Not retried on a 5xx, for the same reason {@link triggerRun} is not: a POST
4735
4749
  * that timed out may already have queued the retry.