|
||
 |
||
|
|
||
|
||
Inhalt
|
|||||||||||||||||||||||||||||||||
 |
|||||||||||||||||||||||||||||||||
|
During its procedures and functions, Main//Pyrus focuses on his central elements: the documents. It supports the user during every step of the life cycle of a document. These steps are usually parted in creating, altering, storing and deleting the document. Because of the requirements which occur thereby, it is comprehensible that documents are more than just files for the system, they offer information of the content, the structure and the administration.
These are the information, which are generally known as “the document”. In Main//Pyrus they are parted into the following:
- title
- description
- content
- author
In addition to this, Main//Pyrus has additional information, which are just informative:
- creation date
- date of last altering
- altered last by
- date of release
- released by
Main//Pyrus offers a high flexibility in the definition of a documents’ structure. The structure of a document depends on the specified class. To find out more about classes and structural information, please click here.
The administrative information, which will be saved for every document in Main//Pyrus are listed below. The important different to the content information is, that administrative information have influence on the behaviour of the document. The administrative information are the reason that certain actions are not responsible for some documents.
| Description | Description |
|---|---|
| Owner | The owner of a document is the user who added the document to the system. It is possible to alter the user afterwards, but every document must have an owner. The owner could be a user or a group. The specific character of the owner is, that he has every permission for the document. This is why it is not possible, that any document exists without somebody who has the permission to read this document. |
| Native file | In Main//Pyrus there will be created many different document formats for every document. The most of them are graphic files which have just visible information and which are not alterable therefore. Usual office applications save additional information like the history of the document. These information are particularly worthy of protection. Furthermore, the system has to know which file should be offered for altering. This alterable file is the native file. |
| Document is template | This attribute makes it possible to use a document as template. The usual syntactic correctness of the document does not apply for the templates. |
| Class of the template is alterable | It makes it possible to alter the class of a document which is used as template. The resulting document could belong to another class afterwards. |
| Retention period | Some documents have to be stored for a certain time for different reasons. Main//Pyrus supports you to observe these respites. These respites usually depend on the kind of the document, so the retention period can be specified in the respective classes. |
| Automatically deletion after retention period expired | If a retention period has been specified, the document can be deleted automatically after the expiration of it. You can select this option if you want the system to do this. |
| Not version-controlled | If a altered document will be released after it was checked out, Main//Pyrus would create usually an additional version of it. By selection this option, you can avoid that additional versions will be created. |