Custom Bitrix24 Approval Processes Development

Imagine: a contract for approval, but the amount changes the route, the lawyer is on vacation — the task flies to the deputy, and if rejected, the system automatically returns it to the initiator with a comment. Without custom logic, such scenarios are impossible: the standard Bitrix24 designer only handles linear routes with fixed participants. According to our statistics, 70% of projects require dynamic rules — multi-stage approvals, integration with 1C, SLA with thresholds. For example, one company with a turnover of 500 million rubles reduced contract approval time by 60% after implementing custom processes. We build custom approval processes end-to-end: from requirements analysis to implementation and training. We'll assess your project in 2 days — just reach out.

Why custom approval processes solve what the standard designer cannot?

The standard business process designer has severe limitations: more than 3–4 branches make the scheme unreadable, dynamic participants require PHP code, and process versioning is absent. Our experience shows that 70% of projects need custom logic: complex conditional routes, integration with REST API or external systems.

How we build custom processes?

The foundation is three approaches, chosen based on the task:

• Custom activity blocks — we add our own PHP classes to the designer. They are 3 times more flexible than standard ones because they are not limited by the form.
• CRM smart processes with robots — for simple branching in CRM.
• Fully custom application via REST API — for maximum flexibility.

How to create a custom activity block?

An activity is a PHP class implementing \Bitrix\Bizproc\Activity\Base. It appears in the designer as a standard block but contains arbitrary logic.

class SendToErpActivity extends \Bitrix\Bizproc\Activity\Base
{
    public function execute(\CBPActivity $activity): \CBPActivityExecutionStatus
    {
        $dealId = $activity->getDealId(); // get parameter from BP

        $erpClient = new ErpApiClient();
        $result = $erpClient->createApprovalRequest($dealId);

        if ($result->isSuccess()) {
            $activity->setVariable('ERP_REQUEST_ID', $result->getId());
            return \CBPActivityExecutionStatus::Closed;
        }

        // Error — we can return Faulting for handling in BP
        return \CBPActivityExecutionStatus::Faulting;
    }
}

The block is registered in bitrix/activities/ or /local/activities/. After registration, it appears in the designer as a standard element and supports parameter configuration via a form.

How to implement dynamic participants?

A list of approvers determined by document data is a frequent request. For example: deal amount up to 500,000 rubles — approved by the department head, from 500,000 to 2,000,000 — plus the financial director, above — plus the CEO. And for each department, a different matrix.

Implementation: an activity block "Determine Approvers" calculates the user list based on document data and an authority table. The authority table is stored in an HL-block or a separate DB table. The result is an array of user IDs, passed to the next "Approval" block as a parameter.

// HL-block "Approval Authorities"
// Fields: DEPARTMENT_ID, AMOUNT_FROM, AMOUNT_TO, APPROVER_USER_ID, APPROVER_ROLE
$approvers = ApprovalMatrixTable::getList([
    'filter' => [
        'DEPARTMENT_ID' => $departmentId,
        '<=AMOUNT_FROM' => $amount,
        '>=AMOUNT_TO' => $amount,
    ],
]);

How to organize substitutes and delegation?

Approver on vacation or business trip — the process should not hang. Two options:

• Automatic delegation: before sending the task, we check the user's status (via user.get or a custom profile field "substitute"). If the user is absent — the task goes to the deputy.
• Delegation after timeout: if the task is not completed in X hours — it also goes to the deputy. Implemented via a "Pause" block in BP + condition.

We maintain a substitution matrix in an HL-block: USER_ID, SUBSTITUTE_USER_ID, DATE_FROM, DATE_TO. The activity block checks the current substitute at the time of launch.

How to implement parallel approval with a threshold?

Three approvers simultaneously, two "approve" required:

[Parallel block]
  ├── Task: Approver 1
  ├── Task: Approver 2
  └── Task: Approver 3
[Wait block: 2 out of 3 completed with result "Approved"]
[Condition: result?]
  ├── Yes → Next stage
  └── No → Rejected

In the standard designer, this is implemented via a "Parallel activity" + a custom activity "Vote Aggregation". The activity monitors the accumulation of responses in a BP variable and returns Closed only when the threshold is reached.

How to maintain approval history and audit?

Each approver action is recorded:

• In the document comment via crm.timeline.comment.add
• In a separate HL-block "Approval History" with fields: date, user, action, comment, document version

The latter option is preferable — it allows building reports: how many times on average a document goes through approval rounds, which approver rejects most often, what is the average approval time by document type.

How to set up escalation and SLA?

For each stage, an SLA (completion time) is set. If the deadline is violated:

1. Notification to the approver themselves
2. Notification to their manager
3. After the second threshold — automatic default decision (auto-approval or escalation higher)

Implemented via Bitrix agents or through a scheduler in a custom application.

Comparison: standard vs custom approach

Types of custom processes

How to implement a dynamic approver list: step-by-step guide

1. Create an HL-block "Approval Authorities" with fields: department, amount from, amount to, role, user ID.
2. Develop an activity block that queries the HL-block based on document data and returns an array of approvers.
3. Register the activity in the BP designer via /.description.php.
4. In the process, after the "Determine Approvers" block, add a standard "Approval" block and specify the variable with participants.

What is included in the work and timelines

• Documentation: route map, authority matrix, SLA
• Development of custom activities and HL-blocks
• Setup of substitution and escalation
• Integration with external systems (1C, ERP, Telegram)
• Administrator training and 30 days of support

Timelines depend on complexity: from 2 weeks for a basic process to 6 weeks with ERP integration. Cost is calculated individually — we will assess your project in 2 days after a brief. Get a consultation — contact us.

A mature approval system is not a configured BP in the designer, but a set of custom blocks, routing rules, and an audit base. We guarantee stable operation: certified specialists with over 8 years of experience and 50+ projects. Such a system lasts for years and requires minimal intervention when business rules change — just update the authority table. Custom approval processes pay for themselves on average in 6 months by reducing manual labor by 80%. The solution is fine-tuned, and you can see it for yourself — request a demo.

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.