InRule - The Premier Rule Engine for .NET

InRule is built entirely on the .NET platform, leveraging a component architecture that delivers unparalleled rule processing performance and flexibility. From the feature rich rule authoring environment to the optimized execution of the business rule engine, InRule unifies the domains of managed business logic and traditional systems processes.

What is a Business Rules Engine?

A business rules engine (BRE) is essentially a set of tools that allow analysts and developers to build calculations and decision logic that operate against a company's data. Its primary purpose is to separate the business logic from the system logic allowing substantial changes in system behavior without substantial changes to code.  The "externalized" business rules can be deployed into mission-critical enterprise systems to affect the logic by which the system executes.

Why is InRule the Premier Rule Engine for .NET?

InRule offers the best balance of ease-of-use rules management and flexibility coupled with an optimized evaluation engine. InRule additonally provides:

An Unparalleled Feature Set

• Advanced Decision Table support
• Dynamic interface design and rendering capabilities of irInteract
• Real-time rule evaluation analysis using irVerify
• Desktop and web-authoring modes of irAuthor
• WSE 2.0 and Smart Client support
• Variable service modes of irServer

Tailored to Business Users - Embraced by Developers

• InRule empowers knowledge workers to articulate even the most complex business logic in a rapid and intuitive manner.
• Once established in the application environment, InRule inherently facilitates team development and deployment of business rule applications throughout the enterprise.

Rule Architecture and Rule Oriented Application Development (ROAD) support for the:

• Business Analyst
  Responsible for overall business rule authoring.
• Process Engineer
  Provides authoring insight to workflow and endpoint management.
• Policy Manager
  Reviews industry compliance and governance of rule sets.
• Application Developer
  Maps the business entity schema to the enterprise object models and data stores.
• QA Manager/Tester
  Validates and releases new rule application and versioning changes to production.

InRule - Version 2.9 Features

InRule Version 2.9 delivers enhancements to make authoring and testing complex rules easier, while providing greater control and centralized rule management.

Centralized Rule Application Administration for the Enterprise

InRule's catalog services provide the ability to store, version, check-in/check-out, and set permissions on rules.

Administrators can now view all the objects stored across multiple catalog instances and can "promote" a rule application from one catalog to another.

irCatalogManager extends these capabilities across the enterprise.

Enhanced Testing

Testing rule logic has been made even easier with irVerify, InRule's integrated testing component. Rule execution is simpler to follow with an improved layout and Watch Lists.

The addition of a Watch List pane lets users create a list of fields to watch, so that only relevant or critical values are shown.

This helps users focus on fields that concern them and makes the verification process more efficient.

Relative Context-defined Rule Sets

Users can now define rules that are applied depending on the context in which a field is used. For example, ShipTo and BillTo are both fields with type Address. ShipTo may have a specific set of rules applied to it (e.g. "We can't ship alcoholic beverages to Utah") while the rules for BillTo are different (e.g. "Billing address must be in the United States.") This provides users with greater flexibility in reusing entities from multiple fields and collections, while ensuring that rules are applied appropriately and consistently based on an entity's context.

Enhanced Rule Authoring for Collections

InRule's support for handling collections has been enhanced with new functions for effectively iterating over a series of items in a collection. New functions for filtering, sorting, and working with nested collections significantly reduce complexity of authoring rules for sets of data. With these new capabilities, users can easily run rules for every member of a collection or apply rules only to items in a collection that meet a certain condition.

Greater Control over Rule Execution

InRule now allows users to specify rule sets to activate or deactivate based on category or metadata. For example, a user can choose to activate only online rules and deactivate batch rules depending on their needs. A new Halt Ruleset function gives rule authors the capability of halting the execution of a rule with or without invoking a runtime error. This is helpful for situations such as checking input data preconditions and improves users' ability to direct the outcome of rules.