Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Rule Editor Reference

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.

Property | Description
--- | ---
Configuration Section
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 Identifier Naming Requirements.
Description (Editor and Wizard) | Short description of the resource.
Priority (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.
Rank | 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.) See Using Priority and Rank to Control Order of Rule Execution for details. Default is 0.0.
Forward Chain | Determines if the rule is used in forward chaining. If the checkbox is not selected, changes made by this rule won’t trigger other rules. By default the checkbox is selected
Declaration Section
Term | 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`. Note: Do not use the generic "Event" as event type, instead use "SimpleEvent", "TimeEvent", or any other event type defined in the project. It is not necessary to add scorecards in the declaration in order to use them in the rule.
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 Identifier Naming Requirements.
Conditions Section
| 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. TIBCO BusinessEvents evaluates single conditions from left to right. TIBCO BusinessEvents optimizes the evaluation of multiple conditions (refer to the "Order of Evaluation of Rule Conditions" section in TIBCO BusinessEvents Architect Guide).
Actions Section
| List of statements that will be executed when the rule is fired.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.