Application Integration with InRule

  • Updated

The InRule Rules Engine can be integrated into end applications in many different ways.  Typical implementations range from calling the rules engine as a simple calculation engine to driving dynamic surveys incorporating rules and metadata to influence UI display, validation, and navigation.

Application Integration Topics

Core Runtime Objects used to call the Rules Engine

Refer to the source code example: Basic Example of Calling the Rule Engine to see how to use these objects in code.


  • Session object that manages all of the rules engine request directives and execution results


  • Instance of a runtime rule application
  • Derived Classes: FileSystemRuleApplicationReference, CatalogRuleApplicationReference, InMemoryRuleApplicationReference


  • Holds data for the rules engine
  • State may be saved and loaded as needed


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.