Looking for an alternative
to Nintex?

When you trade Nintex for WEBCON you will enjoy better application creation, evolution, and management.

Nintex

WEBCON BPS

Modifying a live application

 

Cancel/restart your live workflows or let them finish the old way

InstantChange™ – your in-flight workflows adapt immediately

Application lifecycle management

Workflow/forms are versioned but not moved between environments; data is not part of your application and changes to data will break it

The entire application – workflow, forms, reports, dashboards, data schema, connections to external data – can be packaged and deployed (and updated) from development to test to production

On-premises & Cloud

 

Three separate and incompatible offerings

One platform that runs on-premises, cloud IaaS, and SaaS offering

Migration and upgrades

 

Manual with some automated guidance. Not all features migrate. Audit trail and current running status must be discarded

Everything migrates, in every direction, with current status and audit trail preserved and intact

Process mapping

 

Separate product

Integrated with workflow and forms and report and dashboard designer

Workflow designer

 

Separate product

Integrated with process mapping and forms and report and dashboard designer

Analytics

 

Workflow designer must add extra measurement steps to workflow

Built into each workflow step

Application data

 

Must be modeled somewhere else (SharePoint, SQL) and managed independently of your application

Data is part of your application and is deployed/updated as your application evolves

Power user options

 

Power users use the same tools as professionals, which are definitely not “workflow for everyone”

Designer Desk provides non-professionals with an easy way to create prototypes professionals can extend and deploy to product

Nintex vs. WEBCON BPS​

Modifying a live application

Nintex:
Cancel/restart your live workflows or let them finish the old way

WEBCON BPS:
InstantChange™ – your in-flight workflows adapt immediately

Application lifecycle management

Nintex:
Workflow/forms are versioned but not moved between environments; data is not part of your application and changes to data will break it

WEBCON BPS:
The entire application – workflow, forms, reports, dashboards, data schema, connections to external data – can be packaged and deployed (and updated) from development to test to production

On-premises & Cloud

Nintex:
Three separate and incompatible offerings

WEBCON BPS:
One platform that runs on-premises, cloud IaaS, and SaaS offering

Migration and upgrades

Nintex:
Manual with some automated guidance. Not all features migrate. Audit trail and current running status must be discarded

WEBCON BPS:
Everything migrates, in every direction, with current status and audit trail preserved and intact

Process mapping

Nintex:

Separate product

WEBCON BPS:
Integrated with workflow and forms and report and dashboard designer

Workflow designer

Nintex:

Separate product

WEBCON BPS:
Integrated with process mapping and forms and report and dashboard designer

Analytics

Nintex:
Workflow designer must add extra measurement steps to workflow

WEBCON BPS:
Built into each workflow step

Application data

Nintex:
Must be modeled somewhere else (SharePoint, SQL) and managed independently of your application

WEBCON BPS:
Data is part of your application and is deployed/updated as your application evolves

Power user options

Nintex:
Power users use the same tools as professionals, which are definitely not “workflow for everyone”

WEBCON BPS:
Designer Desk provides non-professionals with an easy way to create prototypes professionals can extend and deploy to product

Release. Review. Revise. Repeat. Evolve.

An application isn’t really a one-time deliverable – it’ll need to be regularly adapted and improved in collaboration with users and stakeholders. That can’t happen unless the cost of change is low, and that applies to both creating changes and gracefully deploying them.

Say goodbye to fragile dependencies.

When you map a process, the workflow is already finished. So are the forms. When you change a field, the forms, the reports, the data – they’ve already adapted. When you define a connection, you can reuse it over and over again. When you consider that many platforms expect your application to be a series of strings of dependencies upon dependencies, rock-solid solutions are a welcome change.

“Citizen development” is a nice idea – but it’s citizen-assisted development that actually works.

Business users have day jobs. The work it takes to go beyond a quick tactical app and an enterprise-grade solution isn’t trivial. Applications that work by gluing together assets spread all over the company are harder to assemble than one might think. Perhaps it’s better to cooperate with professionals than bypass them. Have everyone participate in a solution, with different tools for different roles – that work together: users can create prototype examples that professionals quickly evolve into true solutions.

Change management revolution withInstantChange™

Learn how our unique technology future-proofs your critical applications, makes remarkable time-to-business the norm, and why you’re missing out if you don’t have it!

One consistent platform that works everywhere

It’s in your data center. It’s a hosted solution. It’s a part of your cloud infrastructure. It’s everywhere.

And everywhere WEBCON BPS is, it’s the same technology. The same feature set. Not just the same look and feel. The same everything.

You can even migrate from one location to another and keep working – without missing a beat in a running instance, and without losing any history or current running status.

The end of fragile applications

Applications wind up involving forms, workflows, reports, connections to data, and perhaps a unified web application that brings them all together. With most platforms, those different elements are build separately, integrated manually, and deployed carefully.

Here’s the fun part: in WEBCON BPS, they’re all different faces of a single thing. The forms are a window into the current state of the workflow. The data schema tells the forms what they need to do. Lookup fields can reference a catalog of already-configured data sources. There are business rules governing, well, everything. Reports know about current status and form content. Change audit trails keep track of everything, not just documents.

No process left behind when you need to make a change

Virtually every process management and workflow automation platform treats a single running instance as a set of queued instructions. Once it starts, it can’t change, and you have to accept it. Maybe you can cancel and restart it, but that’s it.

WEBCON BPS is better than that. At every step in a process, a running instance checks the model to see what should happen next. Change the model, the running instances change their path. The forms change their behavior. The data changes its schema. The reports change their appearance.

The model implemented by WEBCON’s InstantChange™ technology is rare – and incredibly useful when you have processes that won’t stand still.

Processes that run as long as you need

WEBCON BPS apps can happily run for months, if not years, without consuming resources or slowing anything down. You can migrate them, and even modify them, and they’ll continue to run.

Professionals and stakeholders working together

In a world of citizen-assisted development, professionals stay in regular contact with stakeholders. That means stakeholders/users need to be able to understand what’s going on and be able to give feedback that’ll be acted on.

With WEBCON’s Designer Desk, stakeholders create the initial specifications in the form of a functioning prototype. When professionals pick that up and carry it forward, the ongoing work is familiar. With InstantChange™, the effort and time needed to react to feedback is microscopic.

Deployment lifecycle support

Deployment isn’t an afterthought. It’s wired into WEBCON BPS’ DNA. Every application element is aware that it can be moved from place to place, and fundamental design decisions were made to ensure that things keep working when they do.

You can even define dependencies into your applications when you want them to behave differently between development, testing, and production, too.

Process mapping and workflow diagramming aren’t two separate things

Most platforms out there model automations like program flowcharts. Every little activity is a shape on the diagram.

Good luck explaining that to your business stakeholders. They’d need training and reference guides just to be able to follow along.

That’s why some companies pivot to process mapping. In other words, a higher-level, business-friendly diagram that’ll be used to (sometimes automatically) generate that program flowchart-style automation diagram that does the actual work.

The dirty secret is that the relationship between abstract map and real flowchart is one-way. If you modify the flowchart, the relationship is broken. And you have to modify the flowchart, because the map can’t describe everything.

WEBCON BPS is different. There’s one model that does double duty. At face value, it’s an easy map of the steps (or stages) in a process and the paths that can be followed to move between them. One level deeper, and everything that happens when you enter/exit/move between steps is there to be configured – and reconfigured when needed

Auditing and analytics without extra effort

Plenty of platforms offer analytics. Some charge extra for it. Almost all of them require you to do extra work to make use of it. So your hyper-detailed, flowchart-style workflow diagrams will need to become extra detailed to accommodate extra steps to emit metrics to be collected for analysis.

Wouldn’t it be nice if the workflow model assumed it would be reported on? That it provided metrics automatically? And that it had room for you to easily add extra metrics to measure without making the project more complicated? We thought so – and we made it so.

The end of analysis paralysis

The reason why so many projects never get started is because stakeholders aren’t quite sure what they want. Not in detail, at least. Designers conduct a seemingly endless series of requirements-gathering meetings, specification reviews, and so on. They do this because they can’t afford not to get it right the first time.

WEBCON BPS changes that. By making the cost of change low and effort to evolve easy, you can start with an imperfect first try and immediately follow it up with a series of improvements based on feedback. Improvement cycles can be measured in hours, sometimes even minutes.

And since most people have an easier time critiquing than imagining, you not only get faster results – you get better results, too.

One simple subscription (or purchase)

You can subscribe to it. You can buy it. It’s your choice.

See WEBCON BPS in action:

Contact us

Let us answer your detailed questions and take you for a deep dive demo of WEBCON BPS.

* Reguired fields are marked
top