Skip to main content



Decisioning Glossary

A​

Actions​

Operations that run when a rule’s conditions are met. Actions can assign values, run rule sets, update collections, create notifications, or call external services.

Author Studio​

Our browser-based editor for creating and maintaining rule applications. It supports entities, fields, rule sets, vocabularies, decisions, and testing.

B​

Business Language​

The readable rule authoring language supported by vocabulary templates.

C​

Calculated Field​

A field whose value is produced by an expression at runtime instead of being stored.
Variants: Calculation, Inline calculated field

CI/CD for irCatalog​

CI/CD for irCatalog refers to using automated tools to move rule applications through development, test, and production. These tools interact with irCatalog to check in and check out rule applications, retrieve versions, and promote updates without manual steps. This allows rule applications to be included as part of a standard build and release pipeline.

Collection​

A list of child entities inside an entity. Collections support: add, remove, clear, and sort operations.

Conditions​

Logical statements that must be true to trigger rule actions.

D​

Data Set​

A data set is a collection of files grouped together for a specific purpose. In irAuthor, a data set is used to store files that a rule application may need during execution. These files can include JSON, XML, text files, or other structured content. Data sets help keep these resources organized inside the rule application so rules can easily access them when needed. They can also include optional file headers that describe the format of the files they contain.

Data Types​

Data types help define the type of information that can be stored in a field or passed into a rule. They ensure that rules work with the right kind of values during execution.

  • Boolean
    Represents a true or false value.
  • Integer
    Represents a whole number.
  • Decimal
    Represents a number with decimal precision.
  • String
    Represents a text value.
  • Date
    Represents a calendar date.
  • DateTime
    Represents a date and time.
  • Key-value pairs
    A named key and its associated value

Decision​

A named entry point for running logic. A decision has inputs, executes rules, and returns outputs.

Decision API​

A REST API that executes decisions and rule sets using a simplified request structure.

Decision Flow​

A visual model for describing the sequence of logic in a decision.

Decision Platform​

This refers to the tools and services we offer to author, manage, store, and execute automated decisions. It includes irAuthor and Author Studio for building rule applications, irCatalog for storing and versioning them, and irVerify for testing. At runtime, the platform uses Decision Services and the Rule Execution API to execute decisions and rule sets. Together, these components support the full lifecycle of decision logic from authoring through deployment and execution.

Decision Services​

The runtime service that hosts the Decision API and Rule Execution API.

Decision Table​

A grid-based rule structure that maps combinations of conditions to actions.

E​

Endpoint​

Endpoints allow InRule to connect to external systems. They provide a consistent way for InRule to communicate with systems such as databases, email services, message queues, enterprise applications, and web services. Endpoints also support syncing with external schema definitions.

Entity​

A data structure representing a business concept. Entities contain fields and collections that rules act on.

H​

Hard Code​

To hard-code means to embed business logic, decisions, or rules directly into application source code rather than modeling them in a rule engine or decision platform. Hard-coded logic is less flexible and harder to change than logic defined in a decision platform or rule application.

I​

Input Parameters​

Values provided when executing a decision or method rule.

InRule for JavaScript​

A runtime for executing rule applications in JavaScript environments.

InRule Metrics​

InRule Metrics is the component of the platform that provides analytics or measurement capabilities for decision logic, for example, tracking executions, outcomes, and performance of rule applications over time. They can be thought of as the Key Performance Indicators (KPI's) that can be tracked during rule execution.

irAuthor​

The desktop-based editor for building rule applications.

irCatalog​

The repository for storing, versioning, and managing rule applications.
Variants: catalog, catalog database, catalog manager, catalog service

irScript​

The scripting language used for expressions and calculations.

irSDK​

The runtime SDK for executing decisions and rule sets.

irVerify​

The testing tool for running sample data through rules and decisions.

O​

Object Model​

The data structure used by irSDK to represent rule applications and entities.

P​

Placeholder​

A placeholder is an input parameter used in a business language template. Placeholders, in rule templates, allow the user to create business language templates which take different input parameters and use them while executing the associated expression. In a rule template editor, any word enclosed in $ symbols is treated as a placeholder.

Parameters​

Values passed into a decision or method rule that control execution.

R​

Rule​

A unit of logic with conditions and actions.

Rule Actions​

Rule actions define the operations that run when a rule’s condition is met. These actions perform updates, call other logic, interact with external systems, or change how rule sets execute. The actions listed here match the names used in our product and documentation.

  • Activate Rule Set Actions
    Enables rule set actions that were previously deactivated.
  • Add Collection Member
    Adds a new item to a collection.
  • Clear Collection
    Removes all items from a collection.
  • Copy Collection
    Creates a duplicate of a collection and its items.
  • Copy Entity
    Creates a duplicate of an entity and its field values.
  • Deactivate Rule Set Actions
    Temporarily disables rule set actions during execution.
  • Declare Variable
    Creates a local variable that can be used within the rule set during execution.
  • Execute Member Rule Set
    Runs the rule set associated with each member of a collection.
  • Execute Method
    Calls a method rule and uses its return value.
  • Execute REST Service
    Calls an external REST service and uses the response in rule execution.
  • Execute Rule Set
    Runs another rule set from within the current rule.
  • Execute SQL Query
    Runs a SQL command or query and makes the results available to rules.
  • Execute Web Service
    Calls an external SOAP web service and uses the response in rule execution.
  • Execute Workflow
    The Execute Workflow action allows for executing a workflow configured from a Workflow Endpoint.
  • Execute XPath Query
    Runs an XPath query against an XML document and returns the result.
  • Fire Notification
    Creates an informational, warning, or error message.
  • Halt Rule Set
    Stops execution of the current rule set immediately.
  • Map Data
    Maps fields or structures from one source to another using defined mappings.
  • Remove Collection Member
    Removes an item from a collection.
  • Send Mail
    Sends an email message using a configured mail server.
  • Set Field Invalid
    Marks a field as invalid and identifies a validation issue.
  • Set Value
    Assigns a new value to a field, variable, or expression target.
  • Sort Collection
    Orders the items in a collection based on a selected field or expression.

Rule Applications​

A rule application is a package that contains the logic, data structures, and configuration needed to evaluate business decisions. It includes entities, fields, rule sets, rules, notifications, actions, and other components used to model decision logic. Rule applications are stored as a single file or in irCatalog.

Rule Constructs​

Rule constructs define the structure of rule logic in a rule application. They describe the different forms a rule can take and how that rule controls the flow of logic. Rule constructs include common patterns such as If/Then rules, loops, decision tables, and other structures used to evaluate conditions and run actions.

Rule Engine​

The runtime component that evaluates rules and decisions.

Rule Execution API​

The upgraded version of the classic irServer Rule Execution Service for running rule sets and decisions.

Rule Execution Log​

A log of rule firings, field changes, and notifications.

Rule Execution Service​

The legacy runtime service that has been replaced by the Rule Execution API.

Rule Set​

A rule set is a container for a group of related rules and actions. Rule sets control when their rules run and how they behave during execution. This includes settings such as fire mode and run mode, which determine how rules are evaluated. Rule sets can also be activated or deactivated individually or by category to manage the flow of rule execution.

Rule Set Execution Types​

Rule set execution types describe how a rule set is scoped within the rule application. Each type defines the data context in which the rule set operates and how rules in the rule set access entities and fields during execution.

  • Entity Rule Set
    A rule set defined in the context of an entity. It runs for all instances of that entity and has access to the entity’s fields and related entities in the hierarchy. This is the most common rule set type and is recommended for most rule authoring.
  • Context-specific Rule Set
    A rule set defined for an entity when it appears in a specific location in the schema, such as a child entity referenced by a field or a collection. It applies only to that specific instance rather than every instance of the entity type. This allows rules to run in a dual context: the referenced entity and its parent.
  • Independent Rule Set
    A rule set with no associated entity context. All values and entities used in the rule set must be provided as parameters. Independent rule sets always run in explicit fire mode and are executed only when called directly.

Rule Set Execution Modes (Fire Modes)​

Rule set execution modes specify how and when a rule set runs during rule processing. Each mode defines how the engine evaluates rule conditions and whether the rule set can run more than once.

  • Auto Optimized Mode
    The engine evaluates conditions whenever their dependent values change and determines the order in which rules run. The rule set continues to fire until all conditions are satisfied. Only a limited set of actions can be used in this mode.
  • Auto Sequential Mode
    The rule set runs in the order it is authored. It can fire multiple times during rule processing if dependent values change.
  • Auto Single Pass
    The rule set runs once in the order it is authored. It does not run again even if dependent values change during execution.
  • Explicit
    The rule set runs only when it is called directly by an action or a calling application. It does not run automatically and will not re-fire based on dependency changes.

Rule Template​

Rule templates provide the core decision-making constructs in language rules.
Example: If... Then...

S​

Schema​

The data structure that defines entities, fields, and relationships.

SOC 2 Type II​

InRule is SOC 2 Type II Compliant.
SOC 2 Type II refers to the version of SOC 2 audit that assesses not just the design of internal controls, but also their operational effectiveness over a sustained period (typically 6–12 months). It provides strong assurance that a service provider’s systems handle data securely over time.

T​

Template​

A reusable pattern for writing rules using business language.
Variants: rule template, vocabulary template

U​

User-Defined Function​

A user-defined function (UDF) is a reusable helper function created inside a rule application. UDFs let authors encapsulate custom logic in a function using irScript, and then call that function from rules. They reduce complexity, extend built-in capabilities, and can be stored and versioned with the rule application.

V​

Value List​

In the context of decisioning and rule authoring, a Value List is a predefined list of discrete values (e.g., codes or options) that a rule or decision can reference. Value lists help standardize inputs and make rule logic more robust by limiting choices to known valid values.

Vocabulary​

Vocabulary lets users define custom business language templates that make rules easier to read and write. It enhances the business language editor by allowing authors to create their own phrases and templates that appear when writing rules. Vocabulary items can be scoped to the rule application or to specific contexts such as entities or fields.