mappe
| This page was automatically generated from the database schema dump and may be incomplete or incorrect. |
Portfolio master data. A portfolio is a logical, cross-user collection of DMS objects — comparable to a favourites list or a working folder.
1. Columns
| Name | Type | Length | Description |
|---|---|---|---|
|
|
— |
Portfolio ID (primary key). |
|
|
— |
Delete marker (for staged deletion). |
|
|
— |
Timestamp of the last change (UNIX time). |
|
|
— |
Creation date. |
|
|
255 |
User name of the creator. |
|
|
255 |
Recipient/addressee of the portfolio (for handover portfolios). |
|
|
32 |
Subject/title of the portfolio. |
|
|
— |
Portfolio type. |
|
|
— |
Link count. |
|
|
— |
ID of the creator. References benutzer.id. |
|
|
— |
ID of the recipient. References benutzer.id. |
|
|
— |
Final delete marker. |
|
|
32 |
GUID of the portfolio object type. |
|
|
255 |
User-defined column for free data. |
2. Related tables
-
mdrel — assignment of documents to the portfolio.
3. Usage by Server-API jobs
-
dms.AddPortfolio, dms.DelPortfolio, dms.ModPortfolio — portfolio CRUD.