From bf8af993ecbf7e0c1374323abe18525077314efc Mon Sep 17 00:00:00 2001 From: mrstark14 Date: Fri, 4 Sep 2026 18:48:09 +0530 Subject: [PATCH] fix: route v4 endpoints to objectName (#ENGCE-61098) --- .../references/author/plugins/connector/impl.md | 6 +++--- .../references/integration-service/resources.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/skills/uipath-maestro-flow/references/author/plugins/connector/impl.md b/skills/uipath-maestro-flow/references/author/plugins/connector/impl.md index 802532f400..98897d034d 100644 --- a/skills/uipath-maestro-flow/references/author/plugins/connector/impl.md +++ b/skills/uipath-maestro-flow/references/author/plugins/connector/impl.md @@ -35,8 +35,8 @@ Definitions in `definitions[]` are CLI-owned. `uip maestro flow node add` copies An activity is `4.0.0` when its `configuration` JSON reports `"version":"4.0.0"`. Author it through the Configuration workflow below like any other connector activity; `describe`/version mechanics are in [/uipath:uipath-platform — resources.md § `--activity-version`](../../../../../uipath-platform/references/integration-service/resources.md#--activity-version). Four deltas: -1. **No `objectName` in `--detail`** — resolved from the configuration's `activityName` (`model.context.objectName` is empty). -2. **`method` / `endpoint`** — from `connectorMethodInfo` (`registry get`) or `availableOperations[]` (`is resources describe --activity-version 4.0.0`). +1. **`objectName` source** — read the definition's `configuration` `objectName` (the `model.context[]` `objectName` entry is declared with no value). It is the `describe` positional, but do NOT pass it in `--detail` — `node configure` reads it from the definition itself. If configuration carries no `objectName`, the registry copy is stale: run `uip maestro flow registry pull --force`, delete the `definitions[]` entry, and re-add the node. +2. **`method` / `endpoint`** — from `connectorMethodInfo` (`registry get`) or `availableOperations[]` (`is resources describe --activity-version 4.0.0`). 3. **Operation label ≠ HTTP verb** — a semantic operation (e.g. `Update`) pairs with any verb (e.g. `POST /usergroups.users.update`). `flow validate` accepts it; do not "fix" the method to match the label. 4. **Not connection-scoped** — `--connection-id` on `registry get` adds no custom fields. @@ -103,7 +103,7 @@ uip is resources describe "" "" \ Then run `cat ` and read the full cached metadata. Pass `--operation` as the node definition's `model.context[].method` verbatim. E.g. Jira `curated_get_issue` → `GETBYID`; Data Service `QueryEntityRecordsCurated` → `POST`. Do not use `connectorMethodInfo.operation` or `connectorMethodInfo.method` as the describe lookup key. -> **`4.0.0` activities** — positional is the `activityName`, `--activity-version 4.0.0` is mandatory, `--operation` takes the verb from `model.context[].method` (never a guessed semantic label), and `--connection-id` is ignored: `uip is resources describe "" "" --activity-version 4.0.0 --operation --output json`. See [§ 4.0.0 Activities](#400-activities). +> **`4.0.0` activities** — positional is the `objectName`, `--activity-version 4.0.0` is mandatory, `--operation` takes the verb from `model.context[].method` (never a guessed semantic label), and `--connection-id` is ignored: `uip is resources describe "" "" --activity-version 4.0.0 --operation --output json`. See [§ 4.0.0 Activities](#400-activities). Read `availableOperations[].method` and `availableOperations[].path` for method and endpoint; `parameters[]` for query/path parameters and `reference` objects; `requestFields[]` for body names, types, required status, descriptions, and `reference` objects; and `responseFields[]` for the response schema. diff --git a/skills/uipath-platform/references/integration-service/resources.md b/skills/uipath-platform/references/integration-service/resources.md index 5cb4ee5a48..ad8c261abe 100644 --- a/skills/uipath-platform/references/integration-service/resources.md +++ b/skills/uipath-platform/references/integration-service/resources.md @@ -68,13 +68,13 @@ Results are cached locally. Use `--refresh` to bypass cache after re-auth or sch ### `--activity-version` -Pass `--activity-version 4.0.0` only when the activity's `configuration` JSON reports `"version":"4.0.0"`. Otherwise do not pass the flag at all. Any value other than `1.0.0` (the default) or `4.0.0` fails with `Invalid --activity-version value`. `4.0.0` responses cache under a separate key (`.v4.schema.json`), so switching never serves the other version's metadata. +Pass `--activity-version 4.0.0` only when the activity's `configuration` JSON reports `"version":"4.0.0"`. Otherwise do not pass the flag at all. Any value other than `1.0.0` (the default) or `4.0.0` fails with `Invalid --activity-version value`. `4.0.0` responses cache under a separate key (`.v4.schema.json`), so switching never serves the other version's metadata. -The resource argument follows the same rule: `4.0.0` activities are addressed by **activity name** — pass the `activityName` from the `configuration` JSON (`4.0.0` metadata has no `objectName`). Everything else uses the object name. +The resource argument follows the same rule: `4.0.0` activities are addressed by **object name** — pass the `objectName` from the `configuration` JSON. ```bash uip is resources describe --output json -uip is resources describe --activity-version 4.0.0 --output json +uip is resources describe --activity-version 4.0.0 --output json ``` ---