A hypothetical company opens the updated editor and decides to improve its working process at the same time. By evening, nobody remembers which change altered the outcome.
Test interface updates and business-rule changes as separate tasks.
What is known about the update
In the official description, updated on 15 September 2026, Bitrix24 describes the builder’s new workspace. Updates roll out gradually.
An article’s existence does not mean your portal already has every capability. Check the actual version and available tools first. Do not turn someone else’s screen into a compulsory team instruction.
Map the existing behaviour
Before changing settings, record:
- what starts the process;
- which data it receives;
- its branches and participants;
- actions in external systems;
- what constitutes a correct outcome.
Preserve the agreed working version using a method available for your situation. Understand recovery before the first edit, rather than after “something went wrong.”
Identify active process instances separately and clarify their behaviour before changing the template. Do not assume a new version applies automatically and identically to everything.
Compare outcomes rather than diagrams
Using approved examples, check the normal route, a negative decision, an empty field and a repeat run. If the process sends messages or changes real data, organise testing to prevent unwanted actions.
Record expected and actual outcomes for each check. Only then add new rules as a separate change and test again.
Discuss the transition with QQDev through a Bitrix24 audit. Bring the diagram and examples of unusual outcomes. Attractive blocks please the eye; predictable behaviour pleases accounting, sales and everyone who would otherwise have to solve the diagram like an escape room.