remarks
Header data of the text notes on folders, registers, documents and portfolios: one row per note, with the assignment to the object, the colour and audit fields.
The note text is not held in this table. Depending on the storage mode it is either a text file in the file system or a row in osremarktext.
Note links to other DMS objects are not held here either; they live in hyplnk.
1. Columns
| Name | Type | Length | Description |
|---|---|---|---|
|
|
— |
System-wide unique note ID. Corresponds to |
|
|
— |
ID of the DMS object the note is attached to. |
|
|
— |
Object-type ID of that object (object-type ID). |
|
|
— |
Medium ID of the |
|
|
— |
Colour of the note: |
|
|
— |
Creation timestamp (UNIX time). |
|
|
— |
User ID of the creator. |
|
|
— |
Timestamp of the last change (UNIX time). |
|
|
— |
User ID of the last modifier. |
|
|
32 |
Under database storage the key of the note text in osremarktext, under file-system storage |
The textid column is missing from the table description in the vendor manual. The mapping to
osremarktext.textid was measured against enaio® server 12.0.
Under file-system storage std.DeleteRemark removes only
the note file and leaves the row here in place. The note keeps being delivered afterwards, with an
empty <Text>, and can no longer be repaired through UPDATE_TEXT. Only
dms.XMLUpdate with <RemarkText action="DELETE"> removes it
completely.
|