Rules
Most rules in TIBCO BusinessEvents are used for inferencing. However, regular business rules also have a role to play.
A TIBCO BusinessEvents rule has three components:
- Declaration
- They declare which concepts and events the rule will depend on, and the names by which instances of these entities can be referred to in the conditions and actions. Aliases must be valid identifiers. Declaring multiple terms of the same type allows the rule to consider multiple instances of the corresponding entity.
- Conditions
- Each statement in the condition must evaluate to a boolean value. All of these statements must be true for the rule’s action to be executed. Assignments and calls to certain functions are disallowed in the condition.
- Actions
- List of statements that will be executed, when the rule is fired, for each combination of terms that matches all the conditions.
You can organize rules depending on your project and project maintenance needs. Rules are organized in folders. At deploy time you can select folders of rules or individual rules (or both) for deployment.
Inferencing rules are at the heart of TIBCO BusinessEvents. Inferencing rules are declarative, and at runtime are executed based on the outcome of each conflict resolution cycle. Statements in a rule action might create or modify concept instances, create and send simple events, call functions and rule functions, and so on depending on need.
- Rule Priority and Rank
For each RTC, the rule agenda is sorted by priority and then within priority by rank, for those rules that use the same ranking mechanism. - Rule Functions
A rule function is a function written in the TIBCO BusinessEvents rule language. All rule functions created for a project are available project-wide.
Copyright © TIBCO Software Inc. All rights reserved.