Any field or entity may have one or more classifications associated to it, which can be used in rule authoring to provide a more business oriented vocabulary. For example, a Fico Score field may be defined with classifications such as “Excellent”, “Good” “Fair”, or “Poor”. Additional rationale for Classifications include:
- Labels a business condition with a meaningful name for authoring
- Allows fields and entities to be grouped and aliased
- Promotes rule centralization and re-use
Classifications may be used in business language rules using the “is” operator, for example, “Borrower Fico Score is Excellent”. Classifications may also be referenced from Syntax Language using the “IsClassification()” function.
The Classification list shows all the Classifications for a given entity. The Classifications are grouped by the fields to which they apply.
Display Name: in the midwest
Condition: State/Province has a value of "ILLINOIS","INDIANA","IOWA","KANSAS","MICHIGAN","MINNESOTA","MISSOURI","NEBRASKA","NOR TH DAKOTA","OHIO","SOUTH DAKOTA","WISCONSIN","ONTARIO","MANITOBA","SASKATCHEWAN","NUNAVUT"
Here is how this Classification would be defined:
Here are the possible settings on this screen:
The name of the Classification.
The name that will be displayed and used to reference the Classification from a business language rule.
Denotes whether the classification will apply to the entity or the field. If field is selected, a field must be selected from the drop-down list.
For example, if a Classification on a "Transaction Code" field was applied to its "Transaction" entity, the rule could be authored as "If Transaction is Buy", instead of "If Transaction Transaction Code is Buy".
The business language condition of the Classification.
Please sign in to leave a comment.