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.

Entity type

Decision Insight stores information about entities in one of two ways: configuration and transaction. The documented difference between the two is that instances of transaction entities are stored in a dedicated storage area optimized for numerous short-living instances.

The important distinction between configuration and transaction types is that when you create a backup of your application, Decision Insight will include instances of configuration entities in the backup (if they have been linked to an exported space). Instances of transaction entities will never be included in the backup.

From a pragmatic view, you will store items that are static – like the names of process steps – in configuration storage. This means that restoring from a backup will initialize those entities along with the rest of your application.

Information that is transient – like the transactions in process at any given moment – are stored in transaction storage and will not be included in any backup / restore operation.



Related Links