Organizations stack different software systems together to reduce the need for hard-coding changes, to cut costs and to deliver modern application features. More than ever, the trend in these enterprise systems is focused on the principles of reusability, configuration, and cloud computing.
The combined architecture of
Configuration, Not Customization
In addition to built-in entity definitions such as Account, Contact, and Lead, Dynamics CRM allows new entities to be configured without changing code through an IT department. A system administrator, software developer, or technically inclined business user has the ability to define new data structures that can drive almost any conceivable business problem. Additionally, user interface, security, reporting and search in Dynamics CRM are driven by configuration rather than by changing code. The business problems that these applications address may extend beyond traditional Customer Relationship Management (CRM) business problems.
In addition to configurable features, Dynamics CRM also offers an application framework with strong support for extension and integration by software developers and system administrators.
Complex Business Logic and Reusability
Although Dynamics CRM offers a robust platform for managing enterprise data, it does not have built-in features for managing or applying complex business logic to that data. Many real-world software problems require that hundreds of data points are considered simultaneously. Some business verticals that typically require complex decisioning include:
- Insurance quoting, eligibility, underwriting, and claims
- Health care diagnosis, eligibility, and pricing
- Eligibility for government benefits
- Loan origination
- Product configuration and pricing
A Business Rule Management System (BRMS) such as InRule has features that help to address common requirements not provided in Microsoft Dynamics CRM 2013:
- Execute complex logic that drives real business decisions – Complex decisions often require consideration of hundreds of data points and rules. Data points may be aggregated across complex entity hierarchies comprised of many different data types and collections.
- Provide a detailed look into the logic that drives complex decisions – Business logic should be easily readable and reportable for subject matter experts and managers, not just software developers.
- Have the ability to re-use rules, easily change rules over time – Rules may be shared across applications. Additionally, rules often change over time. An application may need to be quickly updated to accommodate changes.
- Change the behavior of Dynamics CRM without having to change code – Business users and subject matter experts should be empowered to make rule changes just as easily as they can control other features of CRM. Have the option to deploy as a completely cloud-based solution – No on premise hardware or software should be required, including management and execution of business rules.
Dynamics CRM and InRule provide an architecture that promotes configuration over code customization, lowering maintenance costs to the business and improving turnaround time on rule changes. Dynamics CRM Online and InRule both deliver the benefits of a service-oriented architecture as well as configurability. A BRMS such as InRule provides configurability of decision logic, business rules, and calculations.
To learn more about how these technologies work together, download the
John Hauppa is the Director of Software Architecture Services for InRule Technology.