Boxed Expression Editor for Business Knowledge

The boxed expression editor for business knowledge is the formal definition of business knowledge.

Purpose

It describes logic using nested table structures. These contain FEEL expressions ("Friendly Enough Expression Language") which are textual notations for formal specification of decision logics.

Call

You make the call by selecting a business knowledgeOpen from the context menu.

Structure

If you open a business knowledge's boxed expression, then the context sensitive Design and Page Layout tabs appear; these tabs contain functions for editing boxed expressions and making expression settings.

The document window tab indicates which business knowledge is displayed in the table.

A business knowledge can be reused by multiple decisions and business knowledges. It is used by a decision or another business knowledge via a knowledge requirement. The outmost boxed expression of a business knowledge is, therefore, a function definition;.

The workspace contains possible recursive nested boxed expressions. The following types of boxed expressions exist:

  •  Literal Expression

    A literal expression contains one single FEEL expression. A FEEL expression always has one value taken from the expression's evaluation.

  •  Context

    Variables can be defined in a context. These have a boxed expression as value respectively.

    A context might also have a result that is taken from a FEEL expression. The context's variables are often combined in this expression.

  •  Function Definition

    A function definition has formal parameters and a boxed expression which is used to evaluate a value from the parameters.

    Function definitions can be defined using FEEL, Java or PMML.

  •  Function Call

    For a function call, a value is specified from the function definition of a called business knowledge. Parameter values are set using boxed expressions.

  •  Decision Table

    A decision table contains rules that map combinations of input values to output values.

    A hit policy determines how the result is determined from applicable rules.

  •  List

    Entries in the list are FEEL expressions.

  •  Relation

    A relation is a table with homogeneous columns regarding type. Cell content is FEEL expressions.

Supported Procedures in the Boxed Expression Editor