news & events

We at WEBCON actually like Microsoft Flow. It’s a nice tool for automating tasks, triggering events, and connecting data/APIs. It complements WEBCON BPS very nicely. But we get asked – a lot – how we compare to it?

We decided to list top 10 differences between Microsoft Flow and WEBCON BPS to answer that question!


WEBCON whitepaper cover - Why MS Flow Builder Should Look at WEBCON BPS


We don’t make comparisons like this to say one tool is better than another. Really. We make comparisons like this to explain when to use one vs. when to use the other. Sometimes you need a wrench (a.k.a. a spanner) and sometimes pliers are the right tool to use. Many jobs will require both.

Let’s take a look at the first 3 reasons why a Microsoft Flow builder should look at WEBCON BPS:

  1. In WEBCON BPS change is easy, immediate, nondestructive, and even nondisruptive

Do stakeholders know exactly what they want in advance? Are business conditions stable enough that new needs won’t emerge? Does scope creep never happen in your environment?

We didn’t think so. Which is why WEBCON developed InstantChange™ technology. You can modify a workflow model, data schema, form layouts, connections, data sources – pretty much anything – and have the change take effect immediately upon deployment. Even on instances that are already in progress.

Try doing that with Flow. Some settings cannot be changed after they’ve been made. Other changes could disrupt the forms you’re using (likely PowerApps) and possibly the data/apps you’re connecting to. And if those things change, you won’t know about it until something breaks.

  1. Your applications run exactly the same in our multitenant SaaS offering, in a dedicated Azure solution, or in your on-premises data center.

WEBCON BPS runs as a multitenant SaaS offering, on an on-premises server, or in an Azure (or other IaaS vendor) environment dedicated to you. But wherever you use us, it’s the same stuff. Same models. Same user experience. No gateways, relays, or half-ways.

You can migrate work done in one place to another place and lose nothing. Current running state? We preserve it. All history? It’ll still be there.

  1. You can understand our models.

Flow diagrams (actually, most tools’ diagrams) look like program flowcharts. They’re very busy with one icon/box/artifact for each step along the way. It makes it very hard to use a diagram for automation work for communication. Designers have to jump over to Visio to draw out simplified diagrams for illustration purposes – and keep them manually in sync when things inevitably need to change.

With WEBCON BPS, you create one diagram. It’s easy to read. And it’s smart enough that it can still tell the workflow engine what to do. This isn’t just a matter of convenience. You build better applications when you can refine the requirements via conversation and negotiation. You can’t do that without common reference points. Ours are easy to produce.

Learn other 7 reasons and one bonus point explaining why a Microsoft Flow builder should look at WEBCON BPS from our brand new whitepaper!