The rule editor and rule function editor are similar. This section focuses on the form-based rule editor. You can adapt the information in the Area and Property section to apply to the different blocks of code in the source editor.
Name
(Wizard only) The name to appear as the label for the resource. Do not use any reserved words. Names must be unique within a folder. See Identifiers (Names). (Editor and Wizard) (Editor and Wizard) Specify a value between 1 and 10, where 1 is the highest priority and 10 is the lowest priority. Rules with a higher priority execute before rules with a lower priority.See also Rank. Only set priority or rank where there is a reason to control the order of rules. As a general practice, it is more efficient to let the engine determine the order of rule firing. Specifies a rule function that controls the order of execution of rules with the same priority. Validity must include Condition (that is, do not select Action Only as the validity.) Determines if the rule is used in forward chaining. If the checkbox is unchecked, changes made by this rule won’t trigger other rules. A concept or event type in the project that you will use in your rule. Types you add to the declaration define the scope of the rule.For example, a concept definition such as /Concepts/Accounts/CheckAccount. Alias A name used to refer to the scope element in the body of the rule. You can change the alias. Like resource names, aliases must be valid identifiers See Identifiers (Names). Each line in the Conditions area is a single expression that evaluates to true or false. Each line is joined to the others with an implicit and operator.For the OR operator, use a double pipe (||) on the same line.BusinessEvents evaluates single conditions from left to right. BusinessEvents optimizes the evaluation of multiple conditions (see Order of Evaluation of Rule Conditions in TIBCO BusinessEvents Architect’s Guide.)
Copyright © TIBCO Software Inc. All Rights Reserved.