null

Skip to end of banner
Go to start of banner

Folder Types

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Current »

Folder types control the behavior and appearance. Apart from general specifications such as folder type, description, document type, versioning behavior and the icon to be used, the following properties are defined:

Allowed subfolders

An entry must be created for each allowed subfolder type. The wildcard character * is supported (e.g. PROJECT*).

If no allowed subfolders are entered, the allowed subfolders are inherited from the parent folder at runtime. Inheritance of this setting may extend over several hierarchy levels and ends at the root node at the latest. If no subfolders are restricted there either, all folder types are allowed.

If no subfolders are to be allowed in a folder, a "dummy" entry can be created. You can enter any value (e.g. "NO FOLDER") that does not correspond to a folder type. In the application, the folder attachment is not available because no valid folder types are set as allowed subfolders.

Allowed document ID

In this setting, you can restrict the document identifications permitted in a folder and thus the possible types of documents in the folder.The document identification of a document info record is also provided using a characteristic. The corresponding characteristic is defined in the Document Control .

If no permitted Document ID are maintained, the settings are inherited from the superior folder at runtime. If no settings are maintained up to the root node, all documents are allowed.

If no documents are to be allowed in a folder, a "dummy" entry can be created. You can enter any value (e.g. "NO DOCUMENTS") that does not correspond to an identification. In the application, the document attachment is not offered if no valid document identifications are set.

Inheritance of characteristics

Determination of characteristics for inheritance

If the class name is'*' or empty, the characteristic is inherited if a standard class type and the class is defined in DMS Customizing for the document type to which the inheritance is to take place, and the characteristic to be inherited is a characteristic of this standard class in this class type.

If an explicit class name is specified, characteristic inheritance only takes place if this class is assigned to the superordinate folder. In this case, this class is also assigned to the subordinate document or document folder.

Inheritance of characteristic values

Single-value characteristics: Single-value characteristics are inherited only from the main usage of a document. If the characteristic to be passed on does not have a value in the characteristic value assignment of the higher-level document folder, the characteristic is passed on empty, otherwise the characteristic value of the higher-level folder is copied. Inheritance always takes place within the same class type.
Multiple-value characteristics: Multiple-value characteristics are inherited both from the main usage and from all other uses (links). The characteristic values of the superior document are merged into the characteristic value assignment of the subordinate document or document folder. Inheritance always takes place within the same class type.

  • No labels