You’ll find a seemingly endless number of options out there if you did a search on low-code development.
Here’s the place where we explain why our approach to overall low-code development is better.
No one collects and maintains data without intending to use it for something. No one designs forms to be filled out and left alone. You do them for a reason. You do them to enhance, or improve, or manage, or optimize, or automate a process. Or all of that.
Too many low-code solutions have you start by modeling data – before you know what you’ll do with it. The forms will be more about editing data than performing tasks. There might be some reactive automation logic added to the application near the end.
If you build an application with WEBCON BPS, you can start by modeling the process from end to end. Then you can figure out what data the process needs and model that. Then you can take the UI we’ll auto-build for you and customize it.
You can still build an application the other way, but why would you want to?
There’s nothing wrong with this. Requirements might have been incomplete. Assumptions might have been incorrect. Or maybe you did everything right but a new need has come to light. Or business conditions changed. Or someone built a prototype and it’s up to you to make it production-ready.
Regardless of why, one thing is certain – you’re going to need to modify your applications. Possibly frequently. Not to worry.
WEBCON BPS lets you change applications without disruption – even while they’re running. It’s called InstantChange™ (we trademarked it and everything) and it really works. You can change the process logic, the data schema, the form design – anything – and the update becomes immediately available to everyone using the application. People don’t have to restart their work to benefit from an application you just improved.
And if making changes and evolving applications is not burdensome anymore, just think how much more agile you can get?
One reason people cringe at the thought of changing an application is because they think it’ll involve a lot of work and risk a lot of destabilization. It shouldn’t be that way.
If you change a step in a process, you shouldn’t have to edit your forms to change any buttons or menu options. If you alter a form field, the database and workflow logic and reports ought to just know about it, shouldn’t they? A change to one asset shouldn’t involve a lot of follow-on matching manual updates.
They certainly don’t with WEBCON BPS. It’s all one application. The forms, the reports, the schema, the process logic – they’re all aware of each other at all times.
Too many low-code platforms offer what they call a “suite”, which is a fancy way of saying “use this tool for laying out forms, this other one for creating reports, this additional tool for modeling data, and yet another tool for designing your automation logic.”
WEBCON BPS gives you a single designer studio where you build your entire solution, and every piece of the solution can be built, viewed, analyzed, and changed in one place.
Let’s say you built a nice solution and five different departments want to use it. Too many tools would make you deploy a copy to each of their collaboration portals, or team workspaces.
Not WEBCON BPS. We’ll let you deploy it once and surface it in each of those places. You can still keep them from seeing each other’s data, and you can still have settings that are unique to each place.
What you won’t have to do is maintain multiple copies, and write clever harvesting logic should you need to aggregate that data for company-wide analyses.
A WEBCON BPS application runs in a WEBCON BPS process portal, but it can also run in a SharePoint site, a Microsoft Teams workspace, inside of Microsoft Outlook, and on a mobile phone or tablet.
But you only have to build it once. It’ll dynamically adapt to wherever you want to surface it. It knows who you are and how you’re viewing it – and it dynamically adapts.
And that’s not just forms. It’s reports, dashboards, task lists – everything.
Too many applications go undocumented; there’s not enough time, or not enough discipline, or something else – you name it. You won’t have that problem with WEBCON BPS. Two clicks is all it takes to harvest an application’s metadata and produce IT-, admin-, and user-friendly application documentation.
The assets you create while building an application? Rules, application connections, data sources, forms, workflows, constants, field definitions, and more? They’re automatically catalogued. You can reuse them as much as you’d like (which we hope is a lot; who wants to redo work that’s already been done?), share them between applications, report on them, and more.
Building your first application with WEBCON BPS might take a little less time compared to many other platforms, but the second, third, fourth, and tenth applications? You’ll be done in significantly less time than most everyone else.
And analytics? They don’t require extra work. As you create your application, we automatically work out performance metrics to track and preserve (you can add more, too). You can get to those metrics from the user interface, the administration dashboard, or the designer studio. It comes in very handy when it comes time to make changes.
Some low-code solutions take on the role of “glue”, or “integration”. That’s fine – we do that, too. But more often than not, you need to create an application that maintains its own data, requires its own user interface, and so on.
WEBCON BPS applications can be connected to just about anything, but your application is self-contained, deployable as a single package, versionable as a set, and governable from a single place.
Best of all? The items you work on are much more than simple data rows. They’re full-blown cases, with master data, detail data, document attachments, email attachments, comment threads, and a lot more. You can secure them, version them, archive them, and report on them as a coherent set.
WEBCON BPS approaches low-code development from a process-first and change-friendly point of view – and we think it makes all the difference.
We think even seemingly static data has a lifecycle, and that it’s often more than create/update/delete. Processes are everywhere, and we make them painless.
HOW TO BUILD A BUSINESS APPLICATION IN 45 MINUTES