Master files (stammX)
| This page was automatically generated from the database schema dump and may be incomplete or incorrect. |
Master files are the top hierarchy level of the enaio® DMS: a container for related business objects (customer file, project file, case file, …). A master file itself carries no document data; it structures subordinate registers and document objects.
Per configured master-file object type, a table stammX exists holding all master files of that type. Analogously to the object convention, X = main type + 1. The variants are:
-
stammX— main table. -
stammXr— rights table. -
stammXs— shadow table (index-data history). -
stammXlistY/stammXlistYs— table-field data and its shadow variant.
1. Common System Fields
The following 16 system fields are present in stammX tables (positions 1–16, here exemplified by stamm1). Starting at position 17, type-specific index fields (feld*, zahl*, datum*, real*) follow — these differ per X.
So far only stamm1 has been examined as a reference. If other stammX tables turn out to have diverging system fields, this list will be adjusted accordingly.
|
| Name | Type | Length | Description |
|---|---|---|---|
|
— |
Internal master-file ID (primary key). Corresponds to DMS system field |
|
|
— |
Timestamp of the last index-data change (UNIX time). Corresponds to |
|
|
— |
Number of links of the master file. Corresponds to |
|
|
248 |
Foreign ID — assignment to an external system. |
|
|
— |
System ID of the master file. |
|
|
255 |
User name of the creator. |
|
|
— |
Creation date of the master file. |
|
|
255 |
User name of the last modifier. |
|
|
— |
Timestamp of the last modification (UNIX time). |
|
|
— |
Marker for master files moved to the recycle bin. |
|
|
32 |
GUID of the owner. References benutzer.osguid. |
|
|
32 |
ID of the security descriptor. Used by dms.SetSD, dms.ReadSD and dms.CreateSD. |
|
|
— |
Flags controlling index-data history. Controls whether shadow rows are written to the |
|
|
— |
Number of text notices on the master file. |
|
|
— |
Number of PDF annotations on the master file. |
|
|
— |
Collaboration flag (status marker for collaboration objects, see dms.GetAllCollaborationDocuments). |
Compared to objectX, stammX lacks:
-
haupttyp,untertyp,anzahl— master files have no document file. -
archiviert,archivar— master files are not archived in the document sense. -
flags,version,lockuser— no versioning/locking at master-file level. -
medium_doc,name_doc,medium_dia,name_dia,filesize,mimetypeid,docpagecount,dochistflags,signstate,props,retention_planned,retention— all document-file related.
Additional in stammX (compared to objectX):
-
colab— collaboration flag.
2. Type-specific index fields
From position 17 onward, the index fields configured in the object definition (osobjdef / osobjfields) for the respective master type X follow. The suffix convention (feld*, zahl*, datum*, real*) and the XML access via dbname are identical to Object — type-specific index fields.
3. Rights table (stammXr)
Analogous to the object rights table: 4-column structure (id, type, value, field), identical across all master-file object types.
4. Shadow table (stammXs)
Analogous to the object shadow table: holds the index-data history of the master file. First column osguid, followed by the type-specific index fields of the corresponding stammX table.
5. Table fields (stammXlistY, stammXlistYs)
Analogous to object table fields: per table field Y defined on master type X, a stammXlistY table with id (FK to stammX.id) and line. Shadow variant stammXlistYs with osguid and line.
6. Related Server-API jobs
-
dms.XMLInsert — create a master file.
-
dms.XMLUpdate — modify master-file index data.
-
dms.XMLImport — insert/update via search match (combines search + insert/update on the same tables).
-
dms.XMLDelete — delete a master file (cascades to registers and documents depending on options).
-
dms.GetObjectDetails — master-file system fields.
-
Object-type ID — structure of the master-file type ID X.