Custom Bitrix24 Smart Process Development

Custom Bitrix24 Smart Process Development

With over 10 years of Bitrix24 experience and 50+ successful projects since 2015, our company delivers robust smart processes that automate your unique business workflows.

What Are Smart Processes in Bitrix24?

Smart processes are dynamic CRM entities that you create for your business needs: complaints, purchase requests, contracts. They are stored in separate tables with their own pipeline, fields, robots, and access permissions.

When Do You Need Custom Smart Processes?

Leads and deals don't always capture your business specifics. Custom dynamic entities — like "Complaint", "Purchase Request", or "Contract" — solve this. For example, managing complaints requires a number, status, assignee, linked deal, and a task for quality. Without custom development, this becomes chaotic. We create a full-fledged pipeline with automation using Bitrix24 dynamic CRM entities (\Bitrix\Crm\Service\Factory), stored in tables b_crm_dynamic_items_{entityTypeId}.

Limits of the Standard Constructor

In CRM settings → "Smart Processes", you can create a new type and add fields, stages, blocks. This works for simple cases, but fails when you need automation like automatic number generation (pattern RC-YEAR-XXXX with auto-increment), integration with 1C, or a custom card interface. Code is unavoidable.

Common scenarios requiring custom development:

• Automatic field calculation upon element creation.
• Chain of related actions: create a task, send notification, write to 1C.
• Non-standard card with custom UI (e.g., embedding charts via placement).
• Complex access rights (everyone can read, only assignee and manager can edit).

How to Create a Custom Smart Process via REST API?

Programmatic creation simplifies deployment between environments:

$result = $b24->callMethod('crm.type.add', [
    'fields' => [
        'title'                  => 'Complaint',
        'isUseInUserfieldEnabled' => true,
        'isLinkWithProductsEnabled' => true,
        'isStagesEnabled'        => true,
        'isRobotsEnabled'        => true,
        'isBizProcEnabled'       => true,
    ],
]);
$entityTypeId = $result['result']['type']['entityTypeId']; // e.g., 1052

// Add user fields
$b24->callMethod('crm.type.fields.add', [
    'entityTypeId' => $entityTypeId,
    'fields'       => [
        'fieldName'  => 'CLAIM_NUMBER',
        'userTypeId' => 'string',
        'listLabel'  => 'Complaint Number',
        'isRequired' => true,
    ],
]);

After that, the type is available in CRM; you can assign stages, robots, and permissions. The REST API gives full control, including migrations (see REST).

Implementing Automatic Element Numbering

A typical task: "Complaint No. RC-YEAR-0042". Implemented via the event handler onCrmDynamicItemBeforeAdd:

AddEventHandler('crm', 'onCrmDynamic' . $entityTypeId . 'ItemBeforeAdd', function(\Bitrix\Main\Event $event) {
    $item = $event->getParameter('item');
    $year = date('Y');

    // Atomic counter in Redis or a table
    $seq = incrementSequence("claim_{$year}");
    $item->set('UF_CRM_CLAIM_NUMBER', sprintf('RC-%d-%04d', $year, $seq));
});

Atomicity guarantees a unique number even with parallel requests. Use Redis or MySQL locks (SELECT ... FOR UPDATE).

Automation with Handlers and Custom Robots

When a complaint is created, automatically:

1. A task is created for the quality department.
2. The related deal is attached (if the complaint is for an order).
3. The responsible manager is notified.

AddEventHandler('crm', 'onCrmDynamic' . $entityTypeId . 'ItemAdd', function(\Bitrix\Main\Event $event) use ($b24) {
    $item    = $event->getParameter('item');
    $dealId  = $item->get('OPPORTUNITY'); // custom field for linked deal

    // Create task
    $b24->callMethod('tasks.task.add', [
        'fields' => [
            'TITLE'       => 'Handle complaint ' . $item->get('UF_CRM_CLAIM_NUMBER'),
            'RESPONSIBLE_ID' => getQualityDeptHead(),
            'DEADLINE'    => date('Y-m-d\TH:i:s', strtotime('+2 business days')),
            'UF_CRM_TASK' => ["D_{$dealId}"],
        ],
    ]);

    // Notification via bot
    notifyManager($item->get('ASSIGNED_BY_ID'), "New complaint: " . $item->get('UF_CRM_CLAIM_NUMBER'));
});

Handlers are written once and work stably. Log errors to avoid lost actions.

Custom automation handlers are created via REST for stage changes:

$b24->callMethod('bizproc.robot.add', [
    'CODE'     => 'send_to_1c',
    'HANDLER'  => 'https://your-server.com/robot/send-to-1c',
    'AUTH_USER_ID' => 1,
    'NAME'     => ['en' => 'Send to 1C'],
    'PROPERTIES' => [
        'document_type' => ['Name' => 'Document type', 'Type' => 'select', 'Options' => ['claim' => 'Complaint', 'refund' => 'Return']],
    ],
    'RETURN_PROPERTIES' => [
        'external_id' => ['Name' => 'ID in 1C', 'Type' => 'string'],
    ],
]);

Custom Card via Placement

For a complex UI, embed your own interface through placement.bind with type CRM_DYNAMIC_DETAIL_TOOLBAR:

$b24->callMethod('placement.bind', [
    'PLACEMENT' => 'CRM_DYNAMIC_' . $entityTypeId . '_DETAIL_TOOLBAR',
    'HANDLER'   => 'https://your-server.com/app/claim-detail',
    'TITLE'     => 'Additional data',
]);

It opens as a side panel (slider) in the smart process card—your SPA with a custom interface.

Access Rights

Permissions are configured through CRM roles (crm.type.userfield.access.set) or the application. For a complex matrix: read—all managers, edit—only assignee and manager, delete—only administrator. Verify via user.current and department.get on each request.

Integration with External Systems

A custom dynamic entity processes data 2 times faster than a standard deal due to optimized storage structure. Typical scenarios:

Integration with 1C often uses the CommerceML protocol for exchanging directories and documents.

Deliverables and Timeline

What is included

• Detailed documentation of the entity structure and API endpoints.
• Custom robot code (up to 3 robots included).
• Integration scripts for 1C, email, webhooks.
• Access to the development sandbox and test environment.
• Administrator training (2 hours online).
• 30-day warranty support.

Timeline

Total: 2–4 weeks depending on the number of robots and presence of custom UI. Typical budget ranges from $1500 to $8000, with clients reporting 30–50% reduction in processing time. For instance, a logistics company reduced complaint handling time by 40%, saving over $10,000 annually. To evaluate your project, contact us—we will calculate the timeline and budget within one day.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.