mcpField
B
bitrix-bizproc

bitrix-bizproc

github.com/bxmaximumProductivity47266 installsUpdated 2w ago
Repository

About bitrix-bizproc

A Bitrix skill for implementing and operating business processes across documents and activities. It emphasizes lifecycle rules, access checks, runtime operations, and safe custom activity development.

Key features

  1. 01Starting and stopping processes
  2. 02Document IDs and type invariants
  3. 03Access checks for operations
  4. 04Custom activities and triggers
  5. 05Runtime troubleshooting guidance

Use cases

  1. 01Implementing document approval flows
  2. 02Adding custom business-process activities
  3. 03Diagnosing stalled process runs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bxmaximum/bitrix-framework-skills --skill bitrix-bizproc

After installing, type/bitrix-bizprocin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
custom-activities.md
runtime-ops.md
start-stop.md
templates-access.md
triggers.md

Details

From the project README

Business processes (bizproc)

Baseline: main 23.0+ · Verified: bizproc 26.1400.0, bizprocdesigner 26.800.0, main 26.800.0

Runtime, documents and activities are in bizproc; the template designer UI is bizprocdesigner (needs feature BizProc). Load bizproc and the document owner module (crm, lists, …).

TaskRead
Start, terminate, kill, external events, document ids, Starterrules/start-stop.md
Custom activity: folder, .description.php, class, reserved names, waiting for eventsrules/custom-activities.md
Custom triggers for the Nodes designerrules/triggers.md
Template rights, designer controllers, import, template servicerules/templates-access.md
Stuck pauses, fault limit, tracking, storage cleanup, agents vs Messengerrules/runtime-ops.md

Invariants

  • A document id is [moduleId, entity, documentId], a type [moduleId, entity, documentType]. Copy triples from the owner module or an existing template; never invent them.
  • CBPDocument methods report through $errors (by reference), not exceptions: check it after every call.
  • Check rights before a manual start and in every custom controller (CBPDocument::canUserOperateDocument() / canUserOperateDocumentType()).
  • Approvals and document state machines → bizproc. Periodic sync and heavy I/O → agents or Messenger (bitrix-background-jobs), never inside execute().
  • Custom activity classes and helpers are vendor-prefixed and never reuse CBPActivity member names.

Comments

Markdown supported