Attributes in Ventoo Case Management

The attribute system allows arbitrary user-defined fields without changing the data structure (EAV model). Attributes can be bound to cases, engagements, scopes, scope schemas, and activities. Open Case Management Setup → Attributes or Attribute Groups.

Attribute groups

An attribute group bundles related attributes for display.

Field

Description

Code

Unique group code (e.g. GENERAL, PROCESS, BILLING).

Description

Display name.

Sort Order

Order in the UI.

Attributes

Field

Description

Code

Unique attribute code.

Description

Display name.

Group Code

Owning attribute group.

Data Type

Data type (see below).

Required

Required status: No, Optional, Mandatory.

Default Value

Prefill for new records.

Sort Order

Order.

For the Table Relation data type, additional fields apply: target table, display/store field, optional filter, and the filter field.

Data types

Data type

Meaning

Text

Free text.

Decimal / Integer

Number.

Boolean

Yes/no.

Date / DateTime

Date or date-time (also accepts BC DateFormula expressions such as CM, +1M).

Dropdown

Selection from predefined values.

Table Relation

Reference to a BC table record (filtered lookup possible).

URL

Web link.

For attributes of type Dropdown, define the allowed options via the Dropdown Values part (code + description, with order). Example for an attribute PRIORITY: LOW, MEDIUM, HIGH, CRITICAL.

Attribute assignment

Via Assign Attributes (on scope schema, scope, and engagement cards) or All Attributes (on the case card), you define which attributes appear on which records. The values actually displayed are determined by a resolution chain:

Direct → Schema → Global → Fallback (all attributes if no assignment exists)

The default value follows the priority: assignment default → attribute default → empty. Values are copied once at creation and are independent afterwards.

Attribute permissions per process step

Via Attribute Permissions or the two matrix views, you control per attribute, process step, and role whether an attribute is visible, editable, or required:

  • Attribute Permission Matrix – Attributes × Roles view, filtered by process step.

  • Attribute Permission Matrix (by Step) – Attributes × Steps view, filtered by role.

Permission resolution runs in this order: exact step → process level → global → default (full access). The permission states are: O – Optional, H – Hidden, V – Read-only, R – Required.

When advancing a process step, empty required attributes block the change.