This page contains information about the rule alias feature.
Rule alias is a more comfortable and convenient alternative to rule ID. Unlike rule ID, the rule alias can be set by the user. Then it may be used to refer to the rule from other rules or when calling the Rule Solver API.
Rule alias can be set via rule settings, this applies to all rule types.
Rule alias can be any string containing letters, numbers and the - character.
Rules created in DecisionRules version 1.12 and smaller will have no rule alias but the user may provide one if they want. All newly created rules will have auto-generated rule aliases that can be freely edited.
setting up a custom rule alias
Rule alias does not have to be strictly unique within the space. However, it is greatly recommended to keep your rule alias unique, since requests with non-unique alias will typically fail.
If you assign two identical rule aliases to several rules in a single space, the conflicting rule aliases are displayed in red color.
rule alias conflict
Solving rules with rule alias works the same way as with rule id (rule flow id). All you need to do is to replace the rule id (rule flow id) in the request with the respective rule alias.
call on solver endpoint made with rule alias via postman
Rule aliases can be used in the
SOLVEfunction in decision tables and decision trees, as well as the
DR.solvefunction available in scripting rules.
solving rule with calling SOLVE() function via rule alias as parameter
There is a possibility to use rule aliases with Management API as well. Just replace the rule ID (rule flow ID) with the respective rule alias and all the requests to the Management API should work as before.