A rule set is a container for a group of logically related rules and actions. Rule sets are functionally significant because they establish when and how the underlying rules are executed. This is accomplished by setting the Fire and Run Modes for the rule set. Rule sets may also be activated and deactivated individually or by category to further control the flow and behavior of rule execution.
Rule sets can be created in both irAuthor® and Author Studio™. Read more about creating rules in Author Studio in the article, Creating a New Rule Set
Three Types of Rule Sets in Author Studio
Entity Rule Sets
Entity Rule Sets are based on an entity context and apply for all instances of the entity. They are the most commonly used of the three rule set types. The associated entity establishes the authoring and execution context for the rule set to operate against, essentially defining which fields are available to the rule set.
One goal when authoring rules is to keep the logic in a rule set as atomic as possible without having to reach across contexts; an Entity Rule Set lends itself to this approach as it defines a limited and relevant logical context for the rules. Entity Rule Sets are typically the recommended authoring model for new users.
Decision Rule Sets
A decision always begins with a DecisionStart rule set and contains a set of inputs that can be different from its outputs. The rules within a Decision execute against the inputs and then the outputs reflect the results. Decisions allow authors to only pass in the data that is needed to make a decision. Decision Rule Sets always use explicit fire mode.
Independent Rule Sets
Independent Rule Sets do not have an inherent associated entity context like Entity Rule Sets or Decision Rule Sets. They are currently disabled and will be available in future releases of Author Studio.
Rule Set Workspace
![]() |
Name |
Rule set name. Click the rule set name to load the rules page. The rules page will show all the rules within the selected rule set.
![]() |
Context |
Identifies the context for the rule set.
![]() |
Fire Mode |
Identifies the selected Fire Mode for the rule set. Make modifications to the Fire Mode by selecting the rule set to load the properties panel.
![]() |
Description |
Identifies the description for the rule set. Make modifications to the description by selecting the rule set to load the properties panel.
![]() |
Modified By |
The user that last made a modification to the rule set.
![]() |
Date Modified |
The time the rule set was last modified.
![]() |
New Rule Set |
Create a new Decision Rule Set or Entity Rule Set.
![]() |
Delete Rule Set |
Delete a Decision Rule Set or Entity Rule Set by hovering over the rule set to see the Delete icon on the far right of the row. The items under the rule set will also be deleted.
Properties Panel
Within the workspace, when a rule set is selected, the properties panel will appear.
![]() |
Name |
The title of the rule set is saved here.
![]() |
Description |
The description of the rule set is saved here.
![]() |
Enabled |
The user can enable or disable the selected rule set. The disabled rule set will not run when the rule application is executed. Enabled slider is available for both decision rule set and entity rule set
Fire Mode Settings
Rule sets are functionally significant because they establish when and how the underlying rules are executed. The Fire Mode allows the user to select when the rule set will fire.
Decision Rule Sets always use explicit fire mode. Therefore, the Decision Rule Set properties panel will not show the fire mode settings.
![]() |
Auto Sequential |
Auto Sequential specifies that the rule set and its associated rules are always "on.” Unlike Auto Optimized rule sets, Auto Sequential rule sets execute in the order they appear in the list. These rule sets will fire any time a dependency for a top-level rule condition changes as the result of running a subsequent rule set.
![]() |
Auto Optimized |
The engine will automatically recalculate a condition within the rule set any time any of its dependent values change. These rule sets do not fire in the order they are authored—the engine decides the sequence based on a proprietary optimization algorithm. These rule sets will continue to fire until all of its conditions are satisfied. Only a limited set of actions are available in an optimized rule set.
![]() |
Auto Single Pass |
Auto Single Pass rule sets execute in the order they appear in the list, and execute only once, even if a dependency for a top-level rule condition changes during the execution of a subsequent rule set.
![]() |
Explicit |
An Explicit Rule Set will be executed only when explicitly instructed to do so by action or calling application. An Explicit Rule Set is appropriate for procedural operations and will not get re-fired automatically by the engine.
The user can enable or disable the selected rule set. The disabled rule set will not run when the rule application is executed. Enabled slider is available for both decision rule set and entity rule set
Comments
0 comments
Please sign in to leave a comment.