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.