action
An operation that is defined in the right-hand side of a rule. An action is carried out only if all the conditions of the rule are satisfied. See condition.
action task
A task in a ruleflow that contains actions that are defined using fragments of business rules. See ruleflow.
administrator
A BRMS user profile proficient in system configuration and administration. The administrator is responsible for administrating the BRMS.
agenda
A component of the rule engine that tracks the prioritized rules selected by the rule engine during the pattern-matching logic cycle. The eligibility of a rule instance can change after another rule instance is fired. If this happens, the content of the agenda is adjusted accordingly. See firing a rule; eligible rule; rule instance.
agenda filter
A filter on rule instances in the agenda.
annotation
A natural language-like string assigned to an element of the business object model. See DisplayText property.
assertion
The action of adding a new object into the working memory.
BLX file
The file extension for a file containing an XML representation of one or more business rules. See BMX file.
BMX file
The file extension for a file containing an XML representation of a business object model. See business object model; BLX file.
BRMS
Business Rule Management System. A system designed to modify and manage business logic independently from the enterprise application. ILOG Rules for .NET is a fully-featured BRMS.
BRX file
The file extension for a file containing an XML representation of the output of the rule project (a ruleset). It is essentially a merge of the .blx, and the .rfx added to the rule project when it is built. See BLX file; RFX file; rule project; ruleset.
business analyst
A BRMS user profile responsible for modeling business rule application projects.
business method
A method added to a type in business object model. Business methods extend the original type without altering its source.
business object model
A representation of a business domain. Using a business object model, users can describe their business logic in a business rule language. The elements of a business object model map to those of a corresponding execution model.
Business Object Model View
A view in Visual Studio .NET with which you view and edit the elements of a business object model.
business policy
The statements that define how an organization conducts its business. A business policy can define internal operations, a marketing strategy, a competitive strategy, and internal and external regulations.
business property
A property added to a type in business object model. Business properties extend the original type without altering its source.
business subtype
A subtype of a type in a business object model. Business subtypes are used to extend an object model using business methods and business properties.
business rule
A statement that models a business policy, is specified unambiguously, and can be implemented in a computer system. A business rule is written in a business rule language, in the form of a statement made of conditions and actions that execute only if the objects treated match the conditions. Business rules are packaged into a ruleset before they can be executed by the rule engine. See business object model; action; condition.
business rule application
An application that enables the execution of a ruleset that has been developed using ILOG Rule Studio.
business rule file
A file that contains one or several rules written in a business rule language.
business rule language
A language for expressing business rules using natural language terms and syntax. With a business rule language you express rules using terminology and constructs defined in a business object model rather than the underlying implementation.
business rule management
The practices that control and manage business rules through their lifecycle. Every company manages policies, and they implement policies in application code. Business rule management is a way of improving this process. Business rule management is not necessarily automated and does not imply technology. Usually an organization has informal business rule management practices.
category
A property of business rules and the elements of business object models. This property allows you to specify whether a business element is visible in a rule. A business element is visible in a rule when at least one of the categories of this business element has been specified on the rule.
condition
Element of a rule that expresses tests on objects.
decision table
A set of business rules with similar conditions and actions represented as a table. Columns represent generalized forms of the conditions and actions. Rows contain specific values for each generalized condition and action. Each row represents a rule.
developer
A BRMS user profile responsible for implementing the business rule application.
DisplayText property
A property of a business element that allows defining natural language-like strings assignments.
DTX file
The file extension for a file containing an XML representation of one or more decision tables.
dynamic domain
A way of defining the set of possible values for a type. The set of values is stored and managed outside the business object model, and changes to the set of values are automatically reflected in the business object model. When rule authors write business rules using the type, they choose from a list of values that is created dynamically and always up-to-date.
dynamic rule selection
A way to filter rule artifacts at runtime. The filter is expressed in rule statements and associated with a rule task. In ILOG Rule Studio for .NET you use the Dynamic Select property of a rule task to specify the filter.
eligible rule
A rule instance whose conditions evaluate to true, and can therefore be fired. Eligible rule instances are stored in the agenda. See firing a rule; agenda; rule instance.
end point
The final node in a ruleflow. A ruleflow can have several end points. See ruleflow.
Execution Services
Public WCF services that provide local and remote ruleset execution for ILOG Rule Execution Server for .NET.
Fastpath
A rule execution mode that uses an optimized sequential algorithm. See ILOG Rule Engine for .NET; Sequential; RetePlus.
firing a rule
The action of removing a rule instance from the agenda once the actions of that rule are carried out as a consequence of a successful match. See action; agenda.
flow task
A task in a ruleflow that references another ruleflow. Executing a flow task is equivalent to executing the ruleflow to which it points. See ruleflow.
ILOG Rule Engine for .NET
Implemented as a class, the ILOG Rule Engine takes a ruleset and executes it against objects in working memory. The rule engine contains the ruleset, the working memory, and the agenda.
ILOG Rule Execution Server for .NET
A set of components with which you can manage and monitor the execution of your rules in either a local or distributed environment.
ILOG Rule Manager for SharePoint
A Rule Team Server Web interface for policy managers to manage and edit rule artifacts.
ILOG Rule Solutions for Office
Microsoft Office rule editing tools for policy managers.
ILOG Rule Studio for .NET
A business rule application development tool integrated into the Visual Studio development environment.
ILOG Rule Team Server for SharePoint
A SharePoint Web server dedicated to business rule management and editing.
Management Service
A Windows service that provides private API support to manage executable resources and monitor ruleset execution for ILOG Rule Execution Server for .NET.
package
See rule package.
Persistence Service
A Windows service that provides private API support to store and access the executable resources for ILOG Rule Execution Server for .NET.
policy manager
A BRMS user profile. The policy manager is a nontechnical user who uses Microsoft Office or Web tools. The policy manager defines and enforces business policy, and is responsible for creating and editing business rules.
precondition
A group of rule statements in which you define global variables for a decision table and conditions that must be met before any rows in the decision table can be executed.
publishing
The process of sending the rules in ILOG Rule Studio to a RuleDoc in a repository for storage and management. Once rules are published, they need to be synchronized between ILOG Rule Studio and the repository. See repository; RuleDoc; synchronization.
repository
A place that provides storage and collaborative access to RuleDocs. See publishing; RuleDoc; synchronization.
RetePlus
A rule execution mode for matching many patterns with many objects. The RetePlus execution mode is used by the rule engine to minimize the number of rules and conditions that need to be evaluated, compute which rules should be executed, and identify in which order these rules should be fired. See ILOG Rule Engine for .NET; Sequential; Fastpath.
retraction
The action of removing an object bound to a rule variable from the working memory. See assertion; working memory.
RFX file
The file extension for a file containing an XML representation of one or more ruleflows.
RQX file
The file extension for a file containing an XML representation of a rule query. You create and rule query files in the Find Rules window. See rule query.
rule artifact
An item used to express a business policy in a business rule application. Business rules and decision tables are examples of rule artifacts.
Rule Document Library
A document library used to store RuleDocs.
Rule Editor
A point and click editor that enables you to build rules through phrases in drop-down menus. Rule Editors are available in ILOG Rule Solutions for Office, ILOG Rule Team Server for SharePoint, and ILOG Rule Studio for .NET.
rule engine
See ILOG Rule Engine for .NET.
Rule Execution Server Console
A snap-in into the Microsoft Management Console (MMC) to enable management and monitoring facilities for ILOG Rule Execution Server for .NET.
rule instance
A rule instance is an occurrence of a rule that includes the combination of objects in the working memory that match the patterns specified in the rule. More than one instance of the same rule may exist in the agenda at any one time because the rule patterns are satisfied by more than one object or set of objects. See agenda.
rule package
A logical container for organizing rule artifacts and other rule packages. A rule package does not serve a function in the execution of its rule artifacts. When you publish a rule project, rule artifacts belonging to the same rule package are stored in the same RuleDoc.
rule project
A type of project in which a business policy is expressed as rules.
rule query
A user-defined search on the rules in a solution. You can use rule queries to filter rules when you publish them, and when you create a ruleset. See RQX file.
rule session
A runtime connection between a client and a rule engine. A rule session may consume initialized rule engine resources. The Rule Execution Server uses rule sessions as an execution component. See ILOG Rule Execution Server for .NET.
rule task
A task in a ruleflow that refers to and orders rule artifacts. See ruleflow.
Rule View
A view in ILOG Rule Studio that allows viewing and editing business rules.
RuleApp
A deployment and management unit for the Rule Execution Server that may contain one ore more rulesets. See ILOG Rule Execution Server for .NET.
RuleDoc
A Microsoft Office file that contains rules and can be edited using ILOG Rule Solutions for Office. RuleDocs contain rule artifacts, such as business rules, decision tables, and ruleflows.
ruleflow
A way to control an order the execution of rule artifacts. You define a ruleflow in terms of tasks and transitions between them. See action task; rule task; flow task; end point; start point; transition
ruleset
An executable bundle of rule artifacts.
ruleset parameters
Parameters that can be defined for a ruleset. These parameters are accessible from outside of the ruleset.
Sequential
A rule execution mode for stateless pattern-matching. With this mode, rules can be processed sequentially, which can improve the speed of rule processing in specific cases. The sequential mode can be selected for individual tasks in a ruleflow. See ILOG Rule Engine for .NET; RetePlus; Fastpath.
SharePoint Products and Technologies
SharePoint Products and Technologies facilitate collaboration within an organization and with partners and customers. Using the combined collaboration features of Windows SharePoint Services and SharePoint Portal Server, users in your organization can easily create, manage, and build their own collaborative Web sites and make them available throughout the organization.
start point
The first node in a ruleflow. A ruleflow can only have one start point. See ruleflow.
synchronization
The process of making sure rule artifacts in a rule project are consistent with their corresponding RuleDoc published to a repository from ILOG Rule Studio. See publishing; repository; RuleDoc.
transition
A connection between two tasks. Transitions are unidirectional, and they can have conditions attached to them. See ruleflow; transition condition.
transition condition
A condition on a transition that specifies when the following task can be executed. See ruleflow; transition.
working memory
A part of the rule engine that stores objects against which a ruleset is executed. It contains the current state of objects that led to the current rules in the agenda. See agenda; ruleset.