Concepts are containers for data. The concept name is a label for the data it will contain (e.g. Person, Country, Language, Date of Birth etc.). The concept instance is the data that it holds.

If you had a spreadsheet of data, the column header would be the concept name, each item of data in that column would be an instance.

You add a concept like this:

Concepts names must be:

  • Unique

  • Not contain quotation marks "

Concept types

A concept has a data type. Four types are supported:

  1. String (default) - plain text that can be used to represent a wide range of data. (can be used as a subject or object of a relationship)

  2. Number - to represent numerical concepts such as Loan amount, Vehicle mileage etc. (can only be used as the object of a relationship)

  3. Date - to represent date data such as Claim date, Date of birth etc. (can only be used as the object of a relationship)

  4. True/False - to represent boolean data that con only be true or false, such as Fraud confirmed, Over 18 etc. (can only be used as the object of a relationship)

Much like a spreadsheet, the different data types allow you to perform different functions on the data when you start creating rules and want to compare or transform this data.

Details of the different functions available for each type are listed in the expressions (ADD LINK) section.

Changing a concept's data type after you have added data to it, or created rules using this concept, can introduce invalid logic that will create errors in your knowledge map. It is therefore best to consider what you will use this data for before in advance of

Mutually exclusive

This feature is only available on concepts with a String data type. Selecting mutually exclusive will restrict the concept to two instances where the selection of one will preclude the other. It is very similar in behaviour to a true/false concept, however it allows custom instances to be set. E.g. hot/cold, night/day, yes/no.

An error message of β€œThe concept [concept name] is mutually-exclusive and should define 2 instances but no instances have been defined.” may be received upon saving your knowledge map when using this feature.

If this error is received it is because no instances have been created. Create two instances on the mutually exclusive concept (e.g. yes and no) and save again.

Last updated