Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
The co-founder of Progress® Corticon® explains why you should care about business rules engines.
Business rules are statements that govern the decisions we make day in and day out in our business. These statements take uncertainty out of the equation so that decisions can be made quickly and accurately, with minimal disruption to customers.
Just as you make negotiations in your everyday life—I need to stock up on groceries, but I don’t have enough fuel in my vehicle, so I will have to stop at the station first—businesses must consider millions of calculations each day about their services to their customers. For example:
To serve high volumes of customers quickly and accurately, businesses put rules in place to guide decision making. For the above cases, a business rule could be something like the following:
These rules constitute the logic of decisions. Complex decisions require hundreds or thousands of rules to fully describe, and it may take people years of study to learn these rules. For example, physicians require years of education and training to learn the “rules” of medicine in order to make patient care decisions.
Business rules are sometimes documented. But, more often than not, rules are in the heads of subject matter experts, managers, analysts and executives. When automated, rules are typically embedded into application code by developers as part of IT systems. In this way billions of micro-decisions—such as negotiating payments at lightning speed when you swipe a credit card, or when approving an online application—can be made each day in hundreds of industries. The car rental representative’s terminal presents him with vehicle options per the customer’s plan; the claims agent’s workflow system immediately returns claims with invalid billing codes to the claimant.
Business rules come from sources both internal and external to the organization. Internally, the business sets policy and uses best practices learned from previous client engagements, industry organizations, partners and others. External rules come from local and governmental laws and regulations, such as the Affordable Care Act, as well as contracts between the business and its suppliers and partners.
When business rules change, the decision logic that represents those rules must also change. The problem is that the rules may be implemented across multiple different systems, and combine with other application logic in complex ways. As a result, once our systems grow in complexity, a simple rule change that business people can describe in minutes can take months of programming time to change. This is why modern enterprises are turning away from hard-coding business rules.
Progress Corticon is a best of class BRMS that empowers developers to manage decision logic as business rules, not programming code. This allows traditional developers to be far more productive. And, it enables a new class of developers—business subject matter experts—to directly manage decision logic.
How the Progress Corticon Business Rules Engine works (Click to enlarge)
Progress Corticon uniquely provides safeguards to ensure the integrity of the decision logic. For any given decision, Corticon automatically identifies rules that are incomplete, in conflict, or circular in logic. This “referential rule integrity” prevents garbage rules from entering the rulebase, and is as important to BRMS as the concept of referential data integrity is for the database.
Corticon compiles rules down into a high performance executable (.exe) that can be integrated using open standards into any number of enterprise systems. Rules can be integrated natively into Java and .NET apps, integrated into any application that can call Web or REST services, and tied directly to a database.
No matter the number of rules, complexity of rules, the amount of data the rules need to reference, or the numbers of transactions the rules have to execute on, Corticon is so high performance that you can be assured it will scale to meet your needs.
Last, Corticon enables fast and safe rule changes. When you want to make a change to a specific rule, Corticon highlights what other rules that change will impact, in ways business people can understand. Users can make changes in a matter of minutes rather than months.
To learn more, visit Progress Corticon on the web or try it free now.
Dr. Mark Allen is a Progress General Manager, dedicated to advancing business automation and passionate about applying technology to improve the world. In 2000, he founded Corticon, later acquired by Progress in 2011. Under his leadership, Corticon became a leading independent business rules platform with hundreds of customers in diverse industries such as financial services, government, healthcare and insurance. Prior to founding Corticon, Dr. Allen developed rules-based systems to help physicians make better patient care decisions. Dr. Allen has a B.S. in Applied Physics from Columbia University, and an M.D. from the University of California Los Angeles.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.