Data Exchange

Data Exchange

MCP routing

• Preferred path: use MCP unica tools unica.view {}, unica.search, unica.view on the object node, unica.check, unica.docs, and unica.run.
• Runtime идёт через unica.run: вызов без op отдаёт словарь операций и контракт каждой — argsSchema, execution, previewRequired, ifRevRequiredOnApply. Контракт вызова бери оттуда, а не из этого текста; выбирай только операцию с implemented: true и не выдумывай аргументов записи с argsSchema: null; превью исполнением не является. Не обходи контракт прямым runner-ом.
• Use unica.view on the role node when exchange behavior depends on rights, privileged mode, or separated data.
• Do not call internal metadata, runtime, analyzer, standards, or package adapters directly. They are hidden behind MCP unica.

References

• Read ../../references/platform/integration-contracts.md for message contracts, file exchange, idempotency, versioning, and error semantics.
• Read ../../references/platform/platform-mechanics.md for exchange registration, tenant boundaries, background workers, and temporary files.
• Read ../../references/platform/runtime-diagnostics.md for ЖР/ТЖ timeline when exchange fails at runtime.

Workflow

1. Identify the exchange model: plan exchange, РИБ, file batch, queue, direct API, or hybrid integration.
2. Inspect metadata and modules with unica.view on the object node and unica.search: plans, nodes, registration rules, message numbers, loading handlers, and conflict resolution.
3. Define the exchange contract: node identity, external ids, schema version, ordering, idempotency, retry behavior, duplicate detection, and compatibility rules.
4. Check change registration deliberately: keep регистрация изменений explicit, state which objects are registered, when registration is suppressed, how deletes are represented, and how retries avoid double writes.
5. Check syntax with unica.check (test runs are outside the v0.13 surface) and report runtime verification as unavailable; for live failures, rely on supplied ЖР/ТЖ and correlate message id, node, user/session, and object ids.

Review checklist

• Message processing is restartable and idempotent.
• Errors distinguish validation, duplicate, incompatible version, missing reference, and temporary transport failure.
• Conflict resolution is explicit and logged.
• Exchange does not bypass rights or tenant boundaries accidentally.
• File names, encoding, schema version, and partial-write behavior are validated before loading.

Contract gaps

If public MCP unica cannot expose exchange runtime state, message queue state, or registration details required for the task, report a Unica MCP contract gap.