- 概要
- はじめに
- 概念
- UiPath CLI を使用する
- 使用ガイド
- CI/CD レシピ
- コマンド リファレンス
- 概要
- 終了コード
- グローバル オプション
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- add-test-data-entity
- テスト データのキューを追加
- 追加-テスト-データ-バリエーション
- 分析
- 開発
- プロジェクトを作成
- 差分
- アクティビティを検索
- GET-ANALYZER-RULES
- get-default-activity-xaml
- エラーを取得
- 手動テスト用のテスト ケースを取得
- 手動テストステップを取得
- get-library-object-repository
- get-object-repository
- get-versions
- Get-workflow-example
- indicate-application
- 要素を示す
- inspect-package
- install-data-fabric-entities
- パッケージのインストールまたは更新
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- パッケージ化
- パブリッシュ
- remote
- 元に戻す
- run, debug & execution
- ファイル名を実行
- 検索テンプレート
- スタートスタジオ
- 実行を停止
- tm
- UIA
- uip tasks
- uip traces
- uip traces feedback
- 移行
- 参照とサポート
Syntax and options for `uip api-workflow bindings sync`, which generates a bindings_v2.json file from an API Workflow JSON for solutions authored outside Studio Web.
uip api-workflow bindings generates the per-project bindings_v2.json file that uip solution resources refresh needs to populate a solution's resource catalogue. Studio Web computes this file in-memory whenever a workflow is opened in the designer; for agent-authored workflows that never get opened in Studio, bindings sync does the same translation offline — it walks the workflow, extracts IntSvc connector activities (skipping Http-kind / implicit-connection activities), dedupes by connection UUID, and writes bindings_v2.json next to the workflow file.
概要
uip api-workflow bindings sync --workflow <path>
uip api-workflow bindings sync --workflow <path>
uip api-workflow bindings sync
オプション
| フラグ | 説明 |
|---|---|
--workflow <path> | Required. Path to the API Workflow JSON file. bindings_v2.json is written into the same directory. |
例
uip api-workflow bindings sync --workflow ./my-workflow/Workflow.json
uip api-workflow bindings sync --workflow ./my-workflow/Workflow.json
データシェイプ(--output json)
{
"Code": "BindingsSync",
"Data": {
"BindingsPath": "/work/my-workflow/bindings_v2.json",
"ResourceCount": 3,
"ActivitiesVisited": 12,
"IntSvcActivities": 4,
"DuplicatesCollapsed": 1,
"ResourceBindings": [],
"PreservedResources": []
}
}
{
"Code": "BindingsSync",
"Data": {
"BindingsPath": "/work/my-workflow/bindings_v2.json",
"ResourceCount": 3,
"ActivitiesVisited": 12,
"IntSvcActivities": 4,
"DuplicatesCollapsed": 1,
"ResourceBindings": [],
"PreservedResources": []
}
}
PreservedResources lists any existing bindings_v2.json entries that were kept as-is because they didn't correspond to an IntSvc activity found during this walk (for example, a resource referenced only by a Http-kind activity).
関連
- uip solution resources — consumes
bindings_v2.jsonto populate the solution resource catalogue and per-user debug overwrites. - uip is connections — get a connection UUID to pass into an activity stub before running
bindings sync. - uip api-workflow registry — emit the connector activity stubs that
bindings syncwalks.