Streamline Approvals in Bitrix24 with Bizproc Workflow Templates

Streamline Approvals in Bitrix24 with Bizproc Workflow Templates

On a portal, eight similar approval processes accumulated with minor differences in amounts and approvers. Each was configured separately; changing rules meant editing eight copies. We solve this with workflow templates — one template, parameters at launch. For example, in a project for a trading company, we reduced the number of templates from 12 to 1, saving 3 hours per week on maintenance. With 5+ years of experience and over 100 successful projects, we ensure your workflow automations are efficient. In 2–3 business days, we design, develop, and test a turnkey template that works on real data. Automating business processes with templates reduces maintenance costs by up to 70%. Development of a custom template costs from $500, while maintenance savings average $1,000 per month. Our experience — over 5 years in corporate portal automation, dozens of successful projects. We guarantee correct operation and provide documentation. Order template development — and forget about process duplication. Contact us for a consultation on your processes.

What is a Workflow Template

A template is a saved BP configuration that can be launched for any matching document. Templates are stored in b_bizproc_workflow_template, linked to a document type (MODULE_ID, ENTITY, DOCUMENT_TYPE). The key difference from a one-time BP is launch parameters. When a template starts, the system shows a form with fields — the user enters data (e.g., amount or reason), and they are available inside the process as variables. The template structure is serialized as an activity graph with nested conditions and sequence flows.

Parameters vs. Variables vs. Constants

Three data types in a BP template. Typically a template contains 5–10 parameters, 3–5 constants.

• Parameters — requested from the user at launch. Type, required, default value are set in the editor. Used where data changes per launch.
• Variables — internal variables, exist within one BP instance. Initialized at the start, modified by actions. For example, the ApprovalResult variable accumulates voting results.
• Constants — fixed values, same for all template launches: threshold amounts, notification addresses, approver user IDs. When rules change, only the constant is updated — not the entire graph.

Templates Cut Approval Time by 3x

Compare: manual setup of one process takes up to 4 hours. For 10 processes — 40 hours. A parameterized template replaces 10 copies, making setup 10 times faster than individual process creation. One-time template development (2–3 days) saves up to 70% of time with each regulation change. Instead of editing each process, you change one constant. This is 5x more efficient than copying processes and reduces support costs. Bitrix24 approval templates allow any logic — from simple requests to multi-stage approvals.

Export and Import of Templates

Templates are exported to an XML file via the editor interface. The XML contains the full BP structure: all actions, conditions, settings, field bindings. This allows:

• Transfer templates between portals (test → production). When transferring between 5 portals, up to 3 hours are saved.
• Store templates in version control
• Create a library of standard processes

When importing to a new portal, field bindings (user IDs, list IDs) need to be remapped manually — they will differ. There is no automatic remapping. Export/import path: [List] → Business Processes → [Template] → Edit → Export/Import.

Programmatic Template Creation (How-to)

For mass creation of similar templates (e.g., for 30 lists), use the Bizproc API — CBPWorkflowTemplateLoader. Below is a step-by-step guide for developers:

1. Prepare an $arTemplate array with required keys: MODULE_ID, ENTITY, DOCUMENT_TYPE, NAME, TEMPLATE, PARAMETERS, VARIABLES, CONSTANTS.
2. Form $arProcessTemplate — an array of actions translated from the template's XML representation. The template structure is serialized as an activity graph with nested conditions and sequence flows.
3. Call the method CBPWorkflowTemplateLoader::Add($arTemplate, $errors).
4. Check the $errors array for any errors.
5. After successful addition, get $templateId.

$template = new \CBPWorkflowTemplateLoader();
$arTemplate = [
    'MODULE_ID'     => 'lists',
    'ENTITY'        => 'BizprocDocument',
    'DOCUMENT_TYPE' => 'iblock_' . $iblockId,
    'NAME'          => 'Approval request',
    'DESCRIPTION'   => '',
    'AUTO_EXECUTE'  => \CBPDocumentEventType::Create,
    'TEMPLATE'      => $arProcessTemplate,
    'PARAMETERS'    => $arParameters,
    'VARIABLES'     => $arVariables,
    'CONSTANTS'     => $arConstants,
];

$templateId = \CBPWorkflowTemplateLoader::Add($arTemplate, $errors);

AUTO_EXECUTE — flag for automatic execution: on document creation, modification, or manually. Values: 0 (manual), 1 (creation), 2 (modification), 4 (deletion).

What's Included in Template Development

• Logic and condition design
• Configuration of parameters, variables, constants
• Creation of launch forms
• Integration with CRM fields, lists, documents
• Testing on real data
• Export template to XML for backup
• Administrator instructions
• Post-launch support

Benefits of Templates Over Process Copying

Copying processes leads to duplication: if a rule needs changing, each copy must be edited. A template with parameters is a single source of truth. Change a constant — all launches update. This cuts maintenance time by 5x and saves budget. Configuring business processes via templates takes 80% less time when changes occur.

Development Timeline

A standard approval template takes 2–3 business days; a complex one with integrations up to 5 days. If you want to automate your processes, contact us — we will propose an optimal solution. Development cost is calculated individually based on complexity. Our Bizproc templates for Bitrix24 are built for efficiency, and we offer expert workflow template development services.

How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project

You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.

1C-Bitrix Editions: Site Management

Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.

Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.

Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.

Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.

Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.

How Does Composite Cache Reduce Server Load?

Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.

1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."

Avoiding Common Mistakes in Edition Selection

Typical Mistakes

• Buying Start for an online store — no sale module, you either need to upgrade immediately or hack a custom ordering system.
• Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
• Using Business for a landing page — overpaying for features that will never be used.

Choosing an Edition for an Online Store

Hard Criteria for Edition Selection

By modules:

• 1C exchange (catalog) → at least Small Business
• Composite cache (main.composite) → only Business
• Web cluster (cluster) → only Business
• Multisite → only Business
• REST API → only Business

By load:

• Up to 1,000 unique visitors/day — any edition can handle
• 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
• 10,000+ unique visitors/day — only Business with composite and cluster

By budget:

• The price difference between editions is 2-5x
• Upgrade at any time — pay the difference in license cost
• Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.

What Happens If You Ignore License Renewal?

An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.

Cost Benefits of Planned Edition Upgrades

1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:

1. Pay the difference in license cost
2. Activate new key: Settings → Updates → Registration
3. Install newly available modules via admin panel
4. Configure new functionality
5. Test compatibility

What we do during an upgrade:

• Check custom code for conflicts with new modules — especially custom event handlers like OnBeforeOrderAdd, OnSaleBasketSaved
• Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
• Configure multi-warehouse if needed — b_catalog_store, warehouse selection rules
• Run full functional testing on staging
• Document changes

As a result, you get:

• A working site on the new edition with no data loss
• Configured composite cache (if upgraded to Business)
• Testing report and recommendations for further optimization
• Access to staging and documentation of changes

Integrating Site Management with Bitrix24

A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.

Practical Recommendations

• Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
• Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
• Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
• Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.

What We Offer: Turnkey Selection and Configuration

We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:

• An edition selection report with justification
• Migration plan (if upgrading)
• Fully set up staging with the new edition
• Composite cache and cluster configuration (if necessary)
• Documentation of the new configuration
• Guarantee of site functionality after the transition

Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.