Prev Next

Item Definition

An important characteristic of data items in Decision Models is their structure.

The ItemDefinition element is used to model the structure and the range of values of the input and the outcome of decisions.

Access

Ribbon

Simulate > Decision Analysis > DMN > DMN Expression, then select or create an ItemDefinition

Other

Double-click on a DMN ItemDefinition

Toolbar Options

Option

Description

See also

Click on this button to save the configuration to the current ItemDefinition.

Click on this button to add a child component to the selected ItemDefinition.

Click on this button to add a sibling component to the selected ItemDefinition.

Click on this button to delete the selected component.

Click on this button to validate the ItemDefinition; Enterprise Architect will perform a series of validations to help you identify errors in the ItemDefinition.

DMN Decision Table Validation

Allowed Value Enumerations

Each 'Leaf' component of the ItemDefinition can define a string of Allowed Value Enumerations.

For example:

A DMN Item Definition example of a complex set of data type using Sparx Systems Enterprise Architect.

A DMN Item Definition example of a simple data type using Sparx Systems Enterprise Architect.

The Allowed Value Enumerations play an important role in Auto Completion. The idea is that you type these values once, and choose from a list later on.

Taking the 'Strategy' ItemDefinition as an example, we can fast fill the 'Allowed Values' field for a Decision table by selection:

Auto-filling value fields in a DMN Decision Table in the context of an Item Definition using Sparx Systems Enterprise Architect.

Then fast fill the Decision table rules by selection:

Auto-filling value fields in a DMN Decision Table in the context of an Item Definition using Sparx Systems Enterprise Architect.

Types of Component

An ItemDefinition element SHALL be defined using only one of these alternative methods:

  • Set to a built-in type
  • Composition of ItemDefinition elements

In other words, if an ItemDefinition is 'leaf' (no child components), it must be set to a built-in type; if an ItemDefinition has child components, it can not be set a built-in type.

The FEEL language has these built-in types:

  • number
  • string
  • boolean
  • days and time duration
  • years and months duration
  • time
  • date and time

Note: 'number', 'string' and 'boolean' are supported by Enterprise Architect for simulation.

In order to set a type for a 'leaf' ItemDefinition, you can use one of these three methods:

  • Use the context menu (Recommended)
  • Type in the cell after the name by appending ': string', ': boolean' or ': number'
  • Input 'string', 'boolean' or 'number' in the tag 'type' for the ItemDefinition

Setting the type of DMN Item Definition in a DMN Model using Sparx Systems Enterprise Architect.

Learn more