Defining the Account Concept
- Procedure
- Right-click the
Concepts folder, and select
.
You will see the New Concept Wizard
- In the
Concept name field, type
Account
. In the Description field, typeThis concept maintains history for account transactions
. - Click Finish.
- In the Account Concept Editor Properties section, add the following properties:
Name Type Policy History Balance
double Changes Only 1 Debits
double All Values 5 Status
String Changes Only 1 AvgMonthlyBalance
double Changes Only 0 The Multiple field is used to define an array property. In this release, domains are used only with the TIBCO BusinessEvents Decision Manager component.
You may wonder where the account ID from the incoming event will be stored. It will go into the concept’s
extId
attribute.Note: Concept Attributes and Concept Relationships:AttributesConcepts, events, and scorecards have some built-in attributes, in addition to the properties you define here. The attributeextId
, referenced as@extId
, will hold the account ID.TheextId
must be unique across the clusterIt’s important to note that the optionalextId
attribute, if used, must be unique across all objects in the cluster. This attribute is used for events as well as for concepts. For example If you use database concepts you might expect to use the primary key from the database as theextId
. However, that would not be possible if more than one table contains the same columns in its primary key.Concept RelationshipsConcepts can have containment and reference relationships with other concepts. You set these up as concept properties, and define the kind of relationship by selecting an appropriate data type for the property. For example, a car concept can contain Wheel concepts, and can have a reference relationship to a Dealership concept.InheritanceConcepts can also inherit from other concepts (and events can inherit from other events). Inheritance is a programming relationship and not an ontology relationship. It enables you to extend a base type for more efficient project management. . - Save and close the resource.
Result
You have defined a concept type to hold information about bank accounts. The last step in building the ontology of your project is to set up a scorecard to hold fraud detection criteria that are used in rules.