Skip to main content

Definitions

Introduction​

The Definitions module serves as a flexible mapping table within the 3D-Customizing environment.
It allows the creation of custom definitions and mappings that can be accessed by backend scripts (Unity) or by the RuleEngine.

Important:
Definitions have no fixed logic and are not automatically passed to Unity scripts or ObjectInformationInteractions.
They act as a data source that can be accessed by any script or process, allowing business logic to be moved from code to customizing.

Example Use Case​

Example: ELineProductLengthMapping

  • Definition: ELineProductLengthMapping, Type: Number
  • Properties (Key/Value):
    • 4500 → 4425

Usage in script:

  • A Unity script (ELineAddressablesCreatePrefabs) extracts the value 4500 from the GameObject name (e.g. "TX_EL_785_TP_4500").
  • The script looks up this key in the ELineProductLengthMapping definition and retrieves the real length 4425.
  • The value 4425 is used as the actual ELine length.

Planned Future Enhancements​

  • Extended Properties → Support for multi-column tables (e.g. variant tables)
  • Integration with RuleEngine → Rules could evaluate definitions automatically

Usage in System

Creating a Definition​

A new Definition can be created by clicking “Create” in the CRUD component.
Existing Definitions can be edited or viewed via the inline icons.

Fields​

  • Code (mandatory)
    → Technical name of the Definition, freely selectable, must be unique and follow naming conventions.
    → Note: This Code is referenced in the backend (Unity) → must match exactly!

  • Type (mandatory)
    → Data type of the Definition:

    • String
    • Number
      (Extension to Float/Int possible)

  • Descriptions (optional)
    → Multilingual description of the Definition

    • de_de = Basis Szene
    • en_en = Base Scene
    • …

Actions​

  • Save → Create new Definition
  • Save → Save changes

Definition-Information Tab (Edit-/View-Mode)​

In Edit-/View-Mode:

  • Basic information of the Definition can be viewed or modified.
  • Save

DefinitionProperties Tab

Purpose​

The DefinitionProperties Tab allows adding Properties (records) to a Definition.

→ Currently: Key/Value pairs
→ Future: multi-column Properties with "Extended Properties"

Example:

Code (Key)Value (Value)
45004425

Creating a DefinitionProperty​

A new DefinitionProperty can be added by clicking “Create”.
Existing Properties can be edited or viewed via the inline icons.

Fields​

  • Code (mandatory)
    → Technical base value for the Property
    Example: "1500" (mm)

  • Value (optional)
    → Technical reference value
    Example: "1475" (mm)

  • Descriptions (optional)
    → Multilingual description of the Property

    • de_de = Basis Szene
    • en_en = Base Scene
    • …

Actions​

  • Save → Create new DefinitionProperty
  • Save → Save changes

DefinitionProperties Tab (Edit-/View-Mode)​

In Edit-/View-Mode:

  • Basic information of the DefinitionProperty can be viewed or modified.
  • Save