By default a business process in Bitrix24 runs on one entity: manually from the card or automatically when a record is created or changed. Running a template across a thousand existing deals — after rolling out a new process, an import or a base cleanup — can't be done that way. The "Roboteka" app has a "Mass launch" section for this: you pick the entity, a filter by dates, an ID list or all records, and a business process template — the app runs it on every record found.
How does a business process run by default?
Three stock ways. Manually: an employee opens a deal or lead card and starts the process with a button — fine for approvals and one-off operations. Automatically on an event: the template settings turn on auto-start on creation or on change of a record — the process starts when the event happens to a specific entity. Through robots: actions fire when a deal lands on a pipeline stage. What all three share — the entry point is always a single card. That's why a template added today won't touch deals created yesterday: for them the creation event has already passed, and nobody will move each one through the stages just to fire robots. How the templates themselves are built is in the breakdown of Bitrix24 business processes.
When do I need a mass launch?
Four typical situations. You rolled out a new template — not only new deals but the whole accumulated base should pass through it. You imported clients from an old CRM — phones and fields need normalizing across all records at once. You rebuilt the pipeline — old deals need new field values set. You're launching a mailing or a promotion — a notification process should run across a segment of contacts. The manual option — opening cards one by one and pressing the start button — is tolerable up to a couple of dozen records. Beyond that you need a tool that assembles the list of entities by a filter itself, runs the template on each, and doesn't tie up a manager all day.
How does the mass launch work in Roboteka?
The "Roboteka" app has a built-in "Mass launch" section. Setup is three steps. First — the entity type: lead, deal, contact, company or smart process. Second — the filter: by a creation-date range, by an explicit ID list, or by all records at once. Third — what to run: a business process template or an individual robot from the catalog with set parameters. The app collects the IDs of the matching records and runs the chosen template on each of them. The launches go through a queue with a rate limit, so the stream of starts doesn't disrupt the portal's current work: managers keep working while the process walks the base.
How do I prepare a template for a run across the base?
Two rules. First — a test run: the "by ID list" mode accepts a few specific records, so test the template on three to five trial entities first and only then run it across all. Second — resilience to a repeat run: if the run has to be repeated, the template must not double up tasks and notifications. Add a condition at the start of the process that checks whether the record was already handled — for example, by whether a service field is filled — and end the process if the work is already done. The more precisely the date filter cuts off already-processed records, the fewer idle launches hit the portal.
Example: update the deals of contacts from a selection
The task: across a segment of contacts, set a new field value in their open deals. The mass launch is configured for the "Contact" entity with a filter by ID list or creation dates. Inside the template are two robots. Find deal by condition looks up a contact's deals by a filter — the contact ID plus an arbitrary JSON filter, for example {"CLOSED":"N"} for open ones — and returns the ID of the first deal found, the list of all IDs, the count and a "Found" flag (Y/N). On Y the Update deal by ID robot writes the new field values, passed as JSON, into the found deal. This way a run across contacts updates the deals linked to them with no manual work.
Bottom line
The stock launch of a business process is tied to a single card and its events. The mass launch in Roboteka covers the rest: the entity type, a filter by dates, a list or all records, a process or robot template — and the run goes across the whole selection through a queue. Before a big launch, test the template on a list of a few IDs and protect it against repeat processing. The robots for such templates are collected in the CRM robot catalog. If the robot you need isn't in the catalog — describe the task, we build it for free and add it to the shared library.