irCatalog is a database-backed service that provides a variety of rule management capabilities. Rules are stored in irCatalog®, and at run time the most up to date rules can be used without any need to recompile application code.
irCatalog delivers full Rule Lifecycle Management:
InRule simplifies administration by importing Active Directory users and groups into irCatalog, where the administrator can assign InRule roles and/or permissions to them. If a user or group is deleted from Active Directory, those deletions are noted in InRule, making initial and ongoing permission management easy and consistent.
irCatalog Manager can be used to manage one or more irCatalog instances, allowing enterprise-level access to all of an organization’s rule applications and InRule users.
InRule provides the ability for users to reuse rules and schemas. Users may select just the parts of a rule application they need, then manage and consume those to update or create new applications. This allows greater consistency in how critical decision logic is applied across an enterprise, because one set of rules and business schemas is authored and maintained, then reused wherever needed.
irCatalog® allows control over the ways in which rule applications and parts of rule applications are accessed and shared. Users have the ability to specify whether new schemas, rulesets, and data elements are shareable, allowing or disallowing their use within other rule applications.
When working with a rule application using shared elements, irCatalog® will alert users if any shared elements have been updated since the last time the rule application was checked in or saved. Revisions may then be pulled into the rule application.
To prevent unwanted revisions of shareable rule elements, an application may be designated as the “master rule application” for a rule element. The shared element may then be modified only within the context of the master rule application.
irCatalog® can be searched for shareable elements, making it easy to find reusable rules and application components.
Multiple team members work on different parts of a rule application, checking out only what they need and allowing other team members to continue working on additional parts of the application. If desired, an "exclusive checkout" can be used to prevent other users from updating all or part of an application.