While the model makes up the heart of the Decision Insight deployment, models themselves contain entities. You build entity definitions within the model to describe what the solution will monitor, evaluate and display. The model also defines the relationships between entities.

You can define the following characteristics for an entity:

  • Name 
  • Space 
  • Description 
  • Type (configuration or transaction)
  • Key                                                                                                                                                

Every entity is comprised of attributes. Attributes contain information about an entity. One (or more) attributes are the Key value used to locate an instance of the entity. 

As you define your Decision Insight model, the first step is to define the entities and attributes for the model.


You could have a bank note entity. A bank note has attributes such as its facial value, its currency, and its serial number. An instance of a bank note entity is, for example, the $100 bill with serial number HG 65595879 B. A $1 bill with serial number F 82969936 H would be another instance of this entity.

Create an entity

To create an entity, on the main menu, click the Configuration icon. On the left menu click Entities, then the New Entity button. 

Properties of an entity

The following lists the properties an entity can have.


When you create an entity, you must define it in a space.  Only entities defined in spaces that are part of the current application are displayed in editors.

  • Configuration – Use configuration type for a globally stable entity, typically configuration related (for example: step, channel, stage, category, process). The instances of this type of entities are exported in application files if they are linked to a space of the application.
  • Transaction – Such entities are created and deleted over time. Select this type for entities representing transactions, payments, shipments, etc.
Inherit from

Entities can inherit the attributes, relations, and keys from other entities. This concept is usually known as Inheritance. It is a way to establish an IS A relation between instances.

An example of inheritance is to consider Animal, Dog and Cat entities. Dogs are animals, as are cats. As a consequence, it is possible to declare the Dog entity as inheriting from Animal. The same holds for the Cat entity.

Inheritance leads to complex applications. It should be used with caution.


Once you've defined attributes for an entity, you can specify that one or more of these attributes will be entity keys. Keys are used to identify, retrieve, and solve instances of data during the data integration process.


For more information, see Collect.

Related Links