Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Defining the Account Concept

Procedure
1. Right-click the Concepts folder, and select New > Concept.
   You will see the New Concept Wizard
2. In the Concept name field, type `Account`. In the Description field, type `This concept maintains history for account transactions`.
3. Click Finish.
4. 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:
   Attributes
   Concepts, events, and scorecards have some built-in attributes, in addition to the properties you define here. The attribute `extId`, referenced as `@extId`, will hold the account ID.
   The `extId` must be unique across the cluster
   It’s important to note that the optional `extId` 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 the `extId`. However, that would not be possible if more than one table contains the same columns in its primary key.
   Concept Relationships
   Concepts 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.
   Inheritance
   Concepts 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.
5. 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.

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.