These tables extend the OpenACS object system and implement a full SQL metadata model for ]po[, allowing to extend object types at run-time. Please see the DynField documentation for more details.
Table |
Cols |
Rows |
Description |
---|---|---|---|
[im_dynfield_attr_multi_value] |
4 |
0 |
Provides storage for DynField multi-values fields (multi-select boxes). The table can define more then one value for each attribute. |
[im_dynfield_attributes] |
7 |
55 |
DynField attribute represents an extension field of one of the ]po[ objects. The im_dynfield_attributes table is an extension of the [acs_attributes table] defined as part of the OpenACS Object Tables for compatibility with the standard OpenACS system. |
[im_dynfield_layout] |
9 |
55 |
Defines the position of DynFields in a [layout page]. Currently (]po[ V3.4) only the Y-position is used), but future versions of ]po[ will feature a grid layout for DynField forms. |
[im_dynfield_layout_pages] |
9 |
7 |
[Layout pages] represent a specific page/location with a specific combination of enabled DynField attributes. For example, a dynamic workflow may want to present the user only a subset of object fields to fill in in a specific workflow transition. |
[im_dynfield_type_attribute_map] |
7 |
1063 |
This map allows us to specify whether a DynField attribute should appear in a Edit/NewPage of an object, and whether it should appear in edit or display mode. The table maps the objects type_id (such as project_type_id, company_type_id etc.) to the "display_mode" for the DynField attribute. The display mode is "edit" if there is no entry in this map table.
|
[im_dynfield_widgets] |
10 |
38 |
[DynField widgets] represent the "semantics" of a DynField attribute by defining the value rage, and the way a DynField is displayed. |
Calle Aprestadora 19, 12o-2a
08902 Hospitalet de Llobregat (Barcelona)
Spain
Tel Europe: +34 609 953 751
Tel US: +1 415 200 2465
Mail: info@project-open.com