It's very easy to move Entities, Fields, Calculations, and Rules up or down in the
Rule App navigation tree: Simply right-mouse click on the item you wish to move
in the tree and select Move Up or Move Down. Alternatively you can use the hot key
combination CTRL-U or CTRL-D to move the item up or down respectively.
Leverage a rich function library including a wide variety of more than 100 functions
and methods out-of-the-box such as adding collection members, wildcard and regular
expression searches, string replacements, and sending emails. To view the full list
of functions, open the InRule Help file and navigate to Developing Rule Applications
Function Reference.
Condense related business rules into a Decision Table. Add any number of input Conditions
and output Actions in an easy to read table structure where combinations of Conditions
result in one or more Actions.
Use versioning to change Calculations, Rules, Decision Tables, Inline Tables, SQL
Queries, and Database Lookups over time with effective dates. Click on the Rule
App node, click Use Versions, and click on the element you wish to version. The
Version tab allows you to add a new version and assign the appropriate effective
date for the change.
Conditionally specify when a Ruleset should fire. The "Auto" Fire Mode
specifies that the rule is always "On" and the rules in the Ruleset will
fire as values are modified. The "Explicit" Fire Mode specifies that rules
will only fire when the user or application instructs the rules engine to execute
the Ruleset.
Explicitly specify the order in which rules are run. Setting the Run Mode of a Ruleset
to Sequential or Single-Pass Sequential. Now, instead of setting a priority on a
rule, the order in which the rules appear in the Ruleset is the order in which they
are run.
Leverage existing business object methods and/or custom functions. By adding a .NET
Assembly Endpoint, you can call your object methods as part of an expression or
as an Execute Method Action.
Label a Rule Application to facilitate the staging of rules through the development
lifecycle. Use InRule's central Repository to label a Rule Application. From irAuthor,
go to Tools -> Maintain Repository. Select the Rule Application you wish to label
click the "Assign Label" button.
Test your rules interactively without having to build an application around them:
irVerify, InRule's rule verification tool, provides the capability to test rules
on-the-fly as the are developed and save your tests for execution later.
Bind your Rule Application Schema to one or more database tables, a complex XSD
structure, or .NET Assembly class hierarchy. Right-mouse click on Endpoints, select
.NET Assembly, Database Connection, or XML Schema Definition, and choose the relevant
schema elements that you need to write rules against.
Use a SQL Query to conditionally populate one or more Entity Fields or a Collection.
Once your SQL Query is established, insert a SQL Query action under a rule condition
and choose your SQL Query to run. Using the Settings button, you can specify the
mapping of columns in your query to Fields in your Entity(s).
