integration-implement

name	integration-implement
description	Реализация интеграций 1С. Используй когда нужно создать HTTP-сервис, REST-клиент, webhook, web service, file exchange, очереди, контракты, обработку ошибок и безопасное хранение секретов.

Integration Implement

MCP routing

• Preferred path: use MCP unica tools unica.project.map, unica.meta.info, unica.meta.compile, unica.meta.edit, unica.code.search, unica.standards.search, unica.standards.explain, and unica.runtime.execute.
• Use unica.form.*, unica.role.*, or unica.cfe.* tools when the integration requires UI, rights, or extension changes.
• Do not call internal metadata, analyzer, standards, runtime, or package adapters directly. They are hidden behind MCP unica.

Workflow

1. Define the contract first: endpoint, method, auth, payload schema, idempotency key, retries, timeout, and error response shape.
2. Inspect existing integration modules and HTTP/web service metadata with unica.code.search and unica.meta.info.
3. Create or edit metadata through unica.meta.compile / unica.meta.edit; keep source-set and format selected by unica.project.map.
4. Put reusable logic in common modules; keep HTTP service handlers thin and explicit about request parsing, validation, and response codes.
5. Handle secrets outside versioned modules and configs. Do not log tokens, passwords, full request bodies with personal data, or raw auth headers.
6. Verify syntax/tests with unica.runtime.execute; for live HTTP behavior use the autonomous-server skill or a user-provided debug URL.

Contract detail

• Read references/platform/integration-contracts.md before changing HTTP/SOAP/OData/JSON/XML/file-exchange behavior.
• Decide state model explicitly: stateless call, authenticated session, queue, exchange message, cursor, or file batch.
• For OData, JSON, and XML, preserve field names, types, date/number semantics, encoding, null handling, and backward compatibility.
• Define auth and secret handling before code: token refresh, certificate or OpenID context, storage location, masking, and retry behavior.
• Make retries idempotent through external ids, message ids, or duplicate checks. Do not rely on remote retries being harmless.
• Stabilize error semantics: validation, auth, duplicate, temporary remote failure, permanent remote failure, and internal failure must be distinguishable.

Review checklist

• Contract and versioning are explicit.
• Input validation rejects malformed data before business writes.
• Retries are idempotent or guarded by external ids.
• Error responses are stable and do not leak internals.
• Logs use structured logging fields and contain correlation ids but not secrets.
• Tests cover success, validation failure, duplicate/retry, and remote failure.

MCP example

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.meta.info",
    "arguments": {
      "cwd": "<workspace>",
      "ObjectPath": "HTTPServices/ExternalAPI/ExternalAPI.xml",
      "Mode": "full"
    }
  }
}