When a DCM device starts up, it needs to know which product slots it has, what their properties are, and any device-type-specific configuration values. This information is delivered to the device over MQTT - firmware does not call any HTTP endpoint directly.
The extensible fields system lets you attach typed custom attributes to any platform entity — without writing code or changing the schema. Tenant administrators define the fields they need, assign them to specific entity types, and start recording values immediately.
The PPM module provides two ways to classify projects and work items: labels and extensible fields. They serve different purposes and operate at different scopes. This page explains the distinction.
This guide walks through creating categories, defining attributes, assigning them to entity types, recording values, and querying extensible field data. It uses a DCM (Device Control Management) vending machine as the example entity.
GPM item attributes are powered by the generic Foundation Extensible Fields (FND EFF) system using entitytype = 'GPMITEM'. This lets any domain — insurance, radiology, beauty — define typed attribute sets on items without schema changes, while sharing a single consistent model across the platform.
PPM project and work item extensible fields are powered by the generic Foundation Extensible Fields (FND EFF) system. The same four-table model used across the platform — categories, attribute definitions, assignments, and values — handles custom fields for both PPMPROJECT and PPMWORK_ITEM entity types.