Bsp Patterns

BSP Patterns

MCP routing

• Preferred path: use MCP unica tools unica.search, unica.view on the object node, unica.view on the form and role nodes, unica.docs, and unica.run.
• Runtime идёт через unica.run: вызов без op отдаёт словарь операций и контракт каждой — argsSchema, execution, previewRequired, ifRevRequiredOnApply. Контракт вызова бери оттуда, а не из этого текста; выбирай только операцию с implemented: true и не выдумывай аргументов записи с argsSchema: null; превью исполнением не является. Не обходи контракт прямым runner-ом.
• Use epf-bsp-init and epf-bsp-add-command only for BSP external processing registration helpers.
• Do not call internal analyzer, standards, runtime, or package adapters directly. They are hidden behind MCP unica.

Workflow

1. Identify the BSP subsystem or library pattern by intent, not by guessed module name.
2. Search existing project usage with unica.search before writing new code. Prefer local project conventions over generic snippets.
3. Inspect affected metadata, forms, roles, and external processing registration with unica.view at each object's logical address.
4. Use unica.docs with source: "development-standard" only for a development-standard that constrains the pattern. Do not treat it as platform or BSP documentation. Exact platform mechanics require unica.docs with source: "platform-help". Treat local BSP code as corroborating implementation evidence, not as the platform contract.
5. Implement the smallest integration point; check syntax with unica.check (test runs are outside the v0.13 surface), and do not claim runtime verification from a static check.

References

• Read ../../references/platform/compatibility-modes.md when BSP code gates behavior by a platform version or compatibility mode. Platform guidance remains the contract source; BSP code is corroborating implementation evidence that must be reconciled with that contract.

Pattern hints

• Long operations: background job, progress feedback, cancellation, and idempotent restart.
• Access: role/profile interaction, privileged mode boundaries, and safe reads.
• External processing: СведенияОВнешнейОбработке, command descriptions, form opening, server command execution.
• Secure data: avoid plaintext secrets in modules, constants, logs, and versioned configs.
• Notifications/files: check cleanup and user-visible error path, not only happy path.

MCP example

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.search",
    "arguments": {
      "query": "СведенияОВнешнейОбработке",
      "scope": "<source-set-from-unica-view>:Configuration",
      "limit": 20
    }
  }
}