Click or drag to resize

NRules Namespace

Contains types that implement runtime components of the rules engine.
Classes
  ClassDescription
Public classActivation
Represents a match of all rule's conditions.
Public classAgendaExpressionEvaluationException
Represents errors that occur while evaluating agenda expression.
Public classRuleCompilationException
Represents errors that occur while compiling a rule.
Public classRuleCompiler
Compiles rules in a canonical rule model form into an executable representation.
Public classRuleExecutionException
Represents errors that occur during rules execution.
Public classRuleExpressionEvaluationException
Represents errors that occur while evaluating expressions as part of rules execution.
Public classRuleLhsExpressionEvaluationException
Represents errors that occur while evaluating rule left-hand side expression.
Public classRuleRepositoryExtensions
Public classRuleRhsExpressionEvaluationException
Represents errors that occur while evaluating rule right-hand side expresson.
Public classSession
See ISession.
Interfaces
  InterfaceDescription
Public interfaceIAgenda
Agenda stores matches between rules and facts. These matches are called activations. Multiple activations are ordered according to the conflict resolution strategy.
Public interfaceIFactResult
Result of an operation on a set of facts.
Public interfaceILinkedFactSet
Collection of linked facts propagated as a set.
Public interfaceILinkedFactSource
Fact source for linked facts.
Public interfaceISession
Represents a rules engine session. Created by ISessionFactory. Each session has its own working memory, and exposes operations that manipulate facts in it, as well as fire matching rules.
Public interfaceISessionFactory
Represents compiled production rules that can be used to create rules sessions. Created by RuleCompiler by compiling rule model into an executable form.
Enumerations
  EnumerationDescription
Public enumerationBatchOptions
Defines how batch insert/update/retract of facts behaves. Any fact that already exists in the session during insert is considered failed. Similarly, a fact that does not exist in the session during update or retract is also considered failed. By default, any failed fact in a batch operation fails the whole operation, and no facts are propagated. This behavior can be changed using BatchOptions.
Public enumerationLinkedFactAction
Action taken on the linked fact.