📄️ Application Integration with InRule
Ways to integrate the InRule Rules Engine into an application, from a simple calculation engine to rules-driven dynamic UI.
🗃️ Configuration Files
5 items
📄️ InRule Decisioning Architecture
InRule's product architecture: end-user tools (Author Studio, irAuthor, irVerify, Catalog Manager), services, and irSDK.
🗃️ Performance Logging and Monitoring
4 items
🗃️ irServer - Rule Execution Service
3 items
📄️ Rule Execution Process Flow
A diagram of InRule's rule execution process flow.
🗃️ Calling InRule from BizTalk Server
4 items
📄️ irSDK Assembly Information
Reference for which irSDK assemblies are needed for common authoring and runtime scenarios, such as custom WPF or WinForms apps.
🗃️ Calling InRule from Windows Workflow Foundation
4 items
📄️ Using InRule NuGet Packages
Reference for the irSDK NuGet packages installed alongside irSDK, such as InRule.Activities and InRule.Authoring.Core.
📄️ InRule Culture Settings
InRule's culture settings translate date, datetime, and number formatting to the Windows session locale at runtime or authoring.
🗃️ .NET Assembly Object State
4 items
🗃️ Embedding Authoring Controls
3 items
📄️ Interacting with Non .NET Platforms
Call the InRule rule engine from COM applications using the COM-compliant typelib provided with the InRule installation.
🗃️ Customizing irAuthor with Extensions
4 items
📄️ License Activation Utility
The License Activation Utility activates or deactivates InRule licenses and registers the Event Log Source without the MSI installer.
📄️ InRule Temp Files
InRule reads and writes to the %TMP% temp directory, so the running app domain's account needs read/write permission there.
📄️ irSDK for .NET Core
InRule's .NET Core support, via InRule.Common, InRule.Repository, and InRule.Runtime NuGet packages targeting .NET Standard 2.0.