Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Rule Template Editor Reference

The rule template, rule, and rule function editors are similar. This section focuses on the form-based editor. You can adapt the information to apply to the different blocks of code in the source editor.

Property | Description
--- | ---
Configuration Section Same as the Rule Editor Configuration section. See Rule Editor Reference for details.
Declarations and Variables Section
Type | Types you add define the scope. As in the Term section of a rule, you can specify concept or event types in the project that you will use in your rule. In addition you can specify variables using primitive types. For example (in the source view):
    Concepts.Accounts.CheckAccount checkacc;
    int i = 123;
It is not necessary to add scorecards in the declaration in order to use them in the rule or rule template.
Alias | A name used to refer to the scope element or variable in the Pre-conditions (`when`) and Action Context (`actionContext`) sections of the rule. Aliases must be valid identifiers See Identifier Naming Requirements.
Expression | If you specify a primitive you can also specify an expression.
Pre-conditions Section
| Each line in the Pre-conditions area is a single expression. Expressions can be local variable declarations, method calls and so on, as well as expressions that evaluates to `true` or `false` such as are found in regular rules. Each line is joined to the others with an implicit `and` an 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.)
Action Context Section
| Defines the list of all possible actions that can be executed when a rule instance based on this template is fired. Only the subset of these action context statements that are defined as commands in the business rules are actually considered. When you add an action context statement, first select one of the action types, then select an entity (create or modify action types) or rule function (call action type).

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.