InstantChange™: the technology that lets you change a running process

Most workflow platforms are designed around a simple assumption: once a process is running, you leave it alone. You can improve it in the next version. You can migrate instances when you're ready. But while it's live, with hundreds of cases in progress, you don't touch it.

WEBCON was built around the opposite assumption.

What is InstantChange™

InstantChange™ is the technology that lets you modify a live workflow while it's running. Add an approval step, change a business rule, restructure how work moves between people and teams − and every active process instance absorbs the change immediately. No restart. No data loss. No manual migration. The modification applies to all active instances at their current position in the workflow, and a full audit trail is maintained throughout.

What you can change live with InstantChange™

Let's be specific, because "modify a live workflow" can mean a lot of things on different platforms. On WEBCON, a process champion (someone from your team trained to build and maintain workflows) can make any of the following changes to a workflow, right now, with active instances in progress:

• Add or remove an approval step. The 300 cases currently waiting for sign-off don't restart. They continue from wherever they are, now under the updated definition.
• Change a business rule – the conditions that determine routing, thresholds that trigger escalation, logic that decides who handles what. Every active case follows the new rules from the moment the change is saved.
• Add form fields or adjust existing ones. Cases in progress absorb the new fields at their current position. No data is lost.
• Restructure routing logic entirely – how work moves between people, teams, departments. Everything keeps running.

InstantChange™ keeps every instance on the same version

In every case, the change is applied at the current position of each active instance. Full audit trail continuity is maintained.There is one version of the process, not two running in parallel while you wait for old instances to drain. This is not an advanced feature you enable in settings. It's how the architecture works.

Why most workflow and low-code platforms can't do this

To understand what makes InstantChange™ unusual, it helps to understand why other platforms struggle with mid-flight changes.

On most workflow platforms, a process instance is essentially bound to the version of the process definition that was active when it was created. The instance carries a reference to that version. When you change the process, existing instances don't automatically know about it – they're still running on the old rules. To bring them across, you need some form of migration, and migration means risk.

Most platforms give you three options: let old instances finish under the old definition (months of parallel version chaos), migrate them manually (risky, labor-intensive, often incomplete), or terminate and restart them under the new definition (you lose progress, context, and audit history). Each option carries real operational cost. None of them is good.

WEBCON works differently

Workflow instances are database records, not runtime objects tied to a specific version. When a process definition changes, every active instance absorbs it at its current position. No migration. No parallel versions. No data loss. There is no architectural time limit on how long an instance can run − the platform treats a workflow running for three hours identically to one running for three years.

	✅ WEBCON InstantChange™	The standard approach
What happens to running instances	Absorb the change immediately at their current position	They keep running on the old version  until the case closes
Versions in production	Always one	Old and new run in parallel
Migration required	No the architecture handles it	Yes, or you wait migration risks data loss
Audit trail	Clean and continuous one version, one timeline	Split across versions  audit becomes guesswork
Result over time	Process stays current no deferred improvements	Backlog grows nobody touches live processes

What InstantChange™ changes in practice

Most process applications start with a backlog problem nobody sees coming. Teams accumulate improvements they'd like to make but don't, because touching a live process with hundreds of active instances creates too much operational risk. The change gets deferred. Then another. The gap between how the process works and how it should work widens, and nobody wants to trigger a migration.

InstantChange™ removes that cost entirely. In practice, that changes four things:

• You ship before your requirements are complete. Prototype in 60 minutes, deploy the next day, improve based on real usage. The first version doesn't need to be right.
• Your portfolio scales without growing the team. Three to five people can run a hundred applications, because the architecture doesn't make the job harder with every release.Your audit trail stays clean. One version of the process, always. No parallel versions, no governance ambiguity, no difficult questions when a regulator asks which rules applied to a specific case on a specific date.

Why InstantChange™ matters – and to whom

The same technology lands differently depending on where you sit in the organization.

If you're a process champion, the moment a change passes testing and goes live — no migration, no deployment window, no IT queue. Every active instance picks it up instantly.

If you're a CIO, the headline is architectural. Your portfolio scales without the governance risks that usually come with speed. No parallel versions, no shadow processes running on outdated logic. Your team stays small. Your control stays intact.

If you're in compliance or legal, the headline is audit trail. One version of the process, always. When a regulator asks which rules apply to which case on which date, the answer is unambiguous.

If you're a business owner or process manager, the headline is responsiveness. A policy changes today, your process reflects it today. No change request. No queue. No outdated process running while IT catches up.