Pictures can be stored locally on the workstations (or network drives) or within a content server. With setting Log. Path in the navigation definition (please see Navigation Definition). the path can be defined, where local pictures will be stored or temporary pictures will be checked in, when they are stored in a content server.
...
[KLASSENART]_[KLASSE].[ext], whereas [ext] stands for the file extension, which has been set under the navigation definition, parameter Type (see Navigation Definition).
Example: 001_KLASSE019.gif.
...
The picture to be shown must be checked-in and parameter Type must match the navigation settings (see Navigation Definition).
Furthermore the following name convention is required:
[KLASSENART][BELIEBIGERTEXT][KLASSE].[ext], whereas [ext] stands for the file extension, which has been set under the navigation definition (see Navigation Definition), parameter Type.
Before displaying the picture, a local copy is created. With [BELIEBIGERTEXT] it is possible to ensure, that only the current picture will be shown. It is recommended to use an increment or date value for [BELIEBIGERTEXT].
Example: After picture 001_20090101_KLASSE019.gif has been up-dated, it should be stored with a new name, e.g. 001_20090113_KLASSE019.gif.
...
A data sheet can be assigned to each class, regardless the data format. Special name conventions are required. They are analog to the name conventions for pictures (see chapter https://pronovia.atlassian.net/wiki/pages/resumedraft.action?draftId=554631331 Pictures ), only text „datasheet_" must be put in front.
...