Automate processes across the entire organization
Learn about key, powerful differentiators
Get a monthly dose of news, insights, and inspiration tailored for IT and business leaders.
Discover our complex training program
See what companies chose WEBCON to accelerate digital transformation
Get a monthly dose of news, insights, and inspiration tailored for IT and business leaders.
Puro Hotels reduces 2 FTE with workflow automation
Discover our complex training program
See what companies chose WEBCON to accelerate digital transformation
Get a monthly dose of news, insights, and inspiration tailored for IT and business leaders.
Puro Hotels reduces 2 FTE with workflow automation
Discover our complex training program
See what companies chose WEBCON to accelerate digital transformation
Modifying a live application |
Power Platform: |
WEBCON BPS: |
Integration |
Power Platform: |
WEBCON BPS: |
Duration |
Power Platform: |
WEBCON BPS: |
Application lifecycle management |
Power Platform: |
WEBCON BPS: |
On-premises & Cloud |
Power Platform: |
WEBCON BPS: |
Migration and upgrades |
Power Platform: |
WEBCON BPS: |
Process mapping |
Powerr Platform: |
WEBCON BPS: |
Analytics and audit trails |
Power Platform: |
WEBCON BPS: |
Records, auditing, case management |
Power Platform: |
WEBCON BPS: |
Application data |
Power Platform: |
WEBCON BPS: |
Power user options |
Power Platform: |
WEBCON BPS: |
Power Platform | 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 |
Integration | Making an application out of components is up to you; PowerApps are built separately from Flows which are separate from reports which are separate from Azure functions which are separate from data; links between them are fragile | The entire solution is built as a set of tightly-coupled components that work together automatically |
Duration | Flows must complete within 30 days; running over that is considered an exception; workarounds exist, but they delay the inevitable, and they’re fragile | Processes can run for one second or one century, and any length of time in between; they’ll survive migration, upgrades, changes to the model, and not end prematurely |
Application lifecycle management | Forms, workflows, and any dependent components must be manually packaged; non-destructive/non-disruptive updates is at best an art, not a science | 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 | Online and multitenant only; a gateway must be used to breach firewalls to access on-premises data | One platform that runs on-premises, cloud IaaS, and SaaS offering |
Migration and upgrades | Elements of projects can be exported as templates for building new projects somewhere else, which isn’t exactly migration | Everything migrates, in every direction, with current status and audit trail preserved and intact |
Process mapping | Create an abstract high-level diagram in Visio, then separately build the application using different tools — doing the work twice | The process model is the workflow diagram, and (together with the data dictionary) drives the form and report models |
Analytics and audit trails | Workflow designer must add extra measurement steps to a flow, and create a place to store those metrics and a way to view them | Built into each workflow step; reporting and analyzing is built into the platform |
Records, auditing, case management | Documents can be treated as records, but the process used to review them will be lost when completed. Data is disconnected and connections are ad-hoc | Every workflow instance is a case with status, roles, documents, data, and an audit trail; the case can be treated like a record from cradle to grave |
Application data | Must be modeled somewhere else (Lists, DataFlex, SQL) and managed independently of your application; data is not part of your application and changes to data will break it | Data is part of your application and is deployed/updated as your application evolves |
Power user options | Power users must use the same tools as professionals; while technically not “code,” a spelling error or misplaced parenthesis will break an application | Designer Desk provides non-professionals with an easy way to create prototypes professionals can extend and deploy to professionals |
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.
And everywhere WEBCON BPS is, it’s the same technology. The same feature set. Not just the same look and feel. The same everything.
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.
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.
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.
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 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.
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 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.