Data Object

A Data Object represents information that is created, read, updated, or deleted during a process.

Key Fields

• Name: The data object name (displayed in diagrams)
• ID: Auto-generated unique identifier

How It Works

Data objects can be:

• Documents (invoices, contracts, reports)
• Records (customer data, orders, transactions)
• Messages (notifications, events, commands)
• Paper documents (Frachtbrief, Rechnung, physical forms)
• Physical signals (GPS positions, sensor readings)
• Any information artifact in the process

Physical Data Objects

Data objects can represent physical items:

• Paper Documents: Frachtbrief (waybill), Lieferschein (delivery note), printed invoices
• Sensor Data: GPS positions, temperature readings, weight measurements
• Physical Items: Packages, materials, products (when tracked as data in the process)

Example:

dataobject:
  - name: "Frachtbrief"
    description: "Physical waybill document for shipment tracking"
  - name: "GPS Position"
    description: "Real-time vehicle location data"

Learn more about Physical World Modeling →

Process Integration

Connected via process steps showing data flow:

• "creates" - Data object is created
• "reads" - Data object is accessed
• "updates" - Data object is modified
• "deletes" - Data object is removed

Cross-References

Data objects may include a refId pointing to canonical data entity definitions for traceability.

Integration

• Storage: Embedded in process elements[] or standalone in dataobject database
• Type: processes.dataobject (embedded) or dataobject (standalone)

Tips

• Use clear, business-focused names (e.g., "Purchase Order", not "PO_TABLE")
• Document data objects that cross system boundaries
• Reference canonical definitions when available